2.5.0 how to transfer config to another machine
I want to migrate a pfsense config to a new (recent) machine. The new one has a different architecture (cpu, interfaces names)
I exported (backup) the actual .xml config file, then modified :
- the interfaces names,
- reverted webgui protocol to http
and imported it in the new machine with a fresh 2.5.0 install (in a testbed separated network)
It boots, but the GUI is stuck on logon page. If admin password is incorrect, I clearly get a "Username or Password incorrect" message, but using the correct credentials, the logon screen clears the fields and does nothing. SSH is OK.
I even get " /index.php: Successful login for user 'admin' " messages in the ssh console.
I suspect a certs issue, but I don't know how to "reset" or switch to standard (webconfigurator) certs without using "reset to factory default".
I tried " pfSsh.php playback generateguicert" but still no success.
I switched to another browser (from firefox to edge) -> I managed to get in !
I changed the password
I changed the wan interface IP to connect to the outside ("Packages Reinstallation" occurred)
I switch back to https
reset WebGUI cert with "pfSsh.php playback generateguicert"
-> now I can connect to GUI witch HTTPS
Cert Authorities (CA) are correct. I have one internal CA and one "Acmecert Let's Encrypt"
When I check the certs in "System / Certificate Manager / Certificates" there is an error in webConfigurator default
seems that pfsense had a crash recovered : "[01-Mar-2021 15:56:02 Europe/Paris] PHP Fatal error: Uncaught Exception: DateTime::__construct(): Failed to parse time string (@) at position 0 (@): Unexpected character in /etc/inc/certs.inc:712"
... and I can't generate additionnal Certs : no button available
JKnott last edited by
I copied the config from my old HP computer to my new Qotom a few weeks ago. It was very easy and only required a couple of minor tweeks. I copied the file directly from the old hard drive to a USB stick to the new drive. However, you can use the backup & restore functions too.
That is what I was expecting on my side, but it did not behave as planned.
Did you transfer from v2.4.5 or 2.5.0 ?
JKnott last edited by JKnott
2.4.5 > 2.4.5
I agree, it works for 2.4.5, but not for 2.5.0
I can confirm transferring leads to a certificate corruption problem, and I'm wondering how I can "reset" or "clear" the certs, to start over cleanly.
JKnott last edited by
Why not install to 2.4.5 and then update to 2.5.0?
I already migrated the "source" machine to v2.5.0 and found a cert corruption issue + dns issue.
I had to redo the whole config on the new machine. However, it offered me the opportunity to "clean up" the whole config ;-)
I want to keep the old machine as a spare one eventually (even if not kept up to date) , so I'm looking for a 2.5.0 -> 2.5.0 transfer procedure.