Errors After "Factory Default" Reset
-
After doing a Factory Default reset, then reconfiguring the interfaces on the box itself, after logging in and going through the first time setup wizard (which is technically the second time), any page other then the dashboard gets the following error:
An HTTP_REFERER was detected other than what is defined in System -> Advanced (https://192.168.0.1/). You can disable this check if needed in System -> Advanced -> Admin.Problem is you can't get to the said page because of this error too. Only the dashboard works.
Cheers.
edit: As of the time of this posting the box is running the latest 2.0 snapshot (via firmware update). And I even get the error in some items on the dashboard.
2.0-RC3 (i386)
built on Wed Jun 29 20:49:28 EDT 2011
Error: 501 Description: An HTTP_REFERER was detected other than what is defined in System -> Advanced (https://192.168.0.1/). You can disable this check if needed in System -> Advanced -> Admin. -
Does the behavior change if you reboot?
-
after the 2nd (or 3rd) reboot it seems to be working fine.
after configuring it (through the web wizard interface) i rebooted.
then errors
rebooted again (from your suggestion)
still errors
rebooted again
no errorsOnly error in syslog right now is apinger: error while loading rrdtool: broken pipe.
However, the RRD graphs are still showing data from the past week even after the "Factory Default" from this morning.
-
Yeah the RRD graphs do not get removed from a factory reset.
Kind of odd that it took three reboots to work, usually if it were something cached in the config just one reboot would have done it.
-
eh, maybe a glitch. I'll let it go over this holiday weekend and do it again on Tues/Wed next week.
(are the rrd graphs suppose to reset after a factory default? thats what I would expect as that is the norm for a factory reset on virtually any device…)
-
I see where the problem is now. After the first time web configuration wizard, the system does NOT reboot on its own. This is where my problem came in.
If you change the LAN IP during this configuration, the system never reboots. Even after the wizard says "done" the web pages are not accessible on the new IP, but you can still access the original 192.168.1.1 IP. PFSense never says to reboot, and it never rebooted. The dashboard says the IP is still 192.168.1.1, but if you go to the LAN interface, it list the NEW IP.
So, basically the problem is after a factory default, going through the first time wizard again, the system does not reboot when done [when it should reboot]. This automatic reboot would fix the issue.
Also, I think there should be an option on the factory default page to clear all RRD Graphs as well. Factory default is starting from the beginning, and old graphs may skew the results of the "new" system.
-
Actually it should not reboot when done, as there should be no need to do so. If the new IP isn't fully applied, that is the problem.
-
Either way, at the end of the wizard it doesn't work properly with a custom IP for the LAN interface.
Now I am curious if it does this on a fresh, "new" install, and not a factory default. I honestly do not remember. I'll get the snapshot from today and do a fresh install to see if it mimics this behavior.
-
You are all lucky guys, since a long time now (tested with alix and full install on "real" hardware) resetting to factory defaults resulted every time in a completely broken machine, which doesn't boot till end but stalls somewhere and has to be reinstalled completely. :-(
That happens now since last summer.
Looking at the disk/cf-card with another freebsd showd that there was a completely broken config.xml which did that failing. Replacing the config.xml with a new "empty", say original config.xml, i could start the pfsense again. Maybe that helps out. -
I reset to factory defaults a lot, and I haven't had any problems in quite some time. I reset the config in VMs fairly often when testing, and there is zero difference in the factory reset on a VM from a full install. Unless you can provide more detail with specific errors and behaviors, it doesn't help.
-
I reset to factory defaults a lot, and I haven't had any problems in quite some time. I reset the config in VMs fairly often when testing, and there is zero difference in the factory reset on a VM from a full install. Unless you can provide more detail with specific errors and behaviors, it doesn't help.
was that at me or igor?
-
I didn't save a broken config, but mostly the config.xml is empty. Its a 0byte-file or the only xml-tag is the first one, followed by an opening tag. Nothing more. Sorry that i cannot help out more.
-
It was for igor
If you can't replicate it, and nobody else has noticed it, it may be something corrupt in your install or something else that was done. Seems fine to me.
-
I'll add one last thing since I think we are on the same page now.
A fresh install, clicking on the "Setup Wizard", specifying a custom IP (ex. 192.168.0.1/16) will do the same thing as the "Factory Default"; the difference is the wizard starts automatically after a factory default. (and by wizard I mean the webConfigurator, not the local console interface/vlan assignments)
Dashboard shows 192.168.1.1, Interfaces->LAN shows 192.168.0.1. Web Interface is accessible on 192.168.1.1, but not 192.168.0.1.
-
and one last thing…i hope (lol)
the last page of the wizard, the "Finished Reloading" page, there is a link that says something like
"Click here to continue on with the webConfigurator" or something like that. the link points to the default IP instead of the new IP given in the wizard.cheers.
-
Some notes to add as I was testing out our production settings on the latest snapshot today.
It seems this bug is only related to the Setup Wizard. Entering everything outside of the wizard things work as expected (without reboots)
-
https://github.com/bsdperimeter/pfsense/commit/44a4d54dd367ff80de93eb63ddebd2aa88c7554b
-
I did a test with a completely new install, restored my config, installed packages and then resetted to factory defaults: pfsense booted and hangs (last message was that em0 and em1 changed state to up). Rebooted twice but it hangs at the same point. Maybe because of the installed packages? I think i'll test that without packages to get that clear. Thats just for your info. Thanks
-
Thanks jimp :)
A nice, easy fix.
