<![CDATA[New Install and Reinstate Config Bug]]>Had a hard lock on the machine and on restarting the HDD didn't recover. Luckily had a backup config.xml so decided to reinstall and let pfSense do its thing.

Fresh install, enabled the LAN and gave it a network so I can log on from another machine, access the web gui, and upload back up config.xml. pfSense loads it and restarts. As its a fresh installation, no packages are loaded up so it tries to do this in the background. However, it seems to fail as Unbound has not started.

Investigating this, I see the Unbound has an Advance Setting and is trying to include the pfBlocker inc file which is not there yet. Removing this and restarting Unbound lets Unbound start successfully.

Just notifying this as a bug on 2.3.1.

]]>https://forum.netgate.com/topic/103469/new-install-and-reinstate-config-bugRSS for NodeSat, 09 May 2026 19:45:55 GMTFri, 29 Jul 2016 09:23:40 GMT60<![CDATA[Reply to New Install and Reinstate Config Bug on Fri, 29 Jul 2016 23:53:10 GMT]]>As a precaution before upgrade I disabled all packages that could block access to internet, pfBlockerNG AND DNSBL, Suricata, Snort etc.

]]>https://forum.netgate.com/post/640858https://forum.netgate.com/post/640858Fri, 29 Jul 2016 23:53:10 GMT<![CDATA[Reply to New Install and Reinstate Config Bug on Fri, 29 Jul 2016 22:31:17 GMT]]>As a note if it helps:

remove or comment out the <custom_options>tag in the config xml under unbound works and unbound starts successfully.

I also had a problem with dnssec with my ISP I believe so removed this as well.</custom_options>

]]>https://forum.netgate.com/post/640846https://forum.netgate.com/post/640846Fri, 29 Jul 2016 22:31:17 GMT