PfSense Lost All settings, unable to restore configuration



  • I have about 20 IPSEC tunnels configured on a pfSense. I was modifying one of the tunnels and hit the apply changes button. When I did so the pfSense crashed and rebooted.

    I checked the console and both interfaces appeared to be unconfigured with no IPs.

    At the top of the screen was a messages that said: Warning: Illegal string offset 'protocol' in /etc/inc/xmlparse.inc on line 77

    Fatal error: Cannot create reference to/from string offsets nor overloaded objects in /etc/inc/xmlparse.inc on line 77

    I was unable to get the router reconfigured so in order to get things back online I stood up a new router in it's place.

    Anyone have any pointers on what could have caused this? And more importantly how to prevent it from happening in the future?



  • You could check the general System log and IPSec log to see if anything relevant is there.  Did you have a config.xml backup that you couldn't restore?  If not, you might want to consider creating at least one backup (Diagnostics - Backup/Restore) for future recovery.



  • @KOM:

    You could check the general System log and IPSec log to see if anything relevant is there.  Did you have a config.xml backup that you couldn't restore?  If not, you might want to consider creating at least one backup (Diagnostics - Backup/Restore) for future recovery.

    I am unable to access the web gui since it doesn't have an IP. Can I access the system log and ipsec logs from the console?

    I did have a backup, but I was concerned that something in the config had caused it to crash and didn't want to have this problem again. Recreating the settings took a couple hours, but if it saves me another unfortunately timed crash it will be worth it. (And it was a good audit of rules, settings, etc.)



  • /var/log contains all of the available logs, including system and ipsec.  I'm just guessing with the ipsec log, since it may only have connection-related details and not anything about the plumbing.


Log in to reply