Web configurator times out
-
@Jamie22 looks like noone will
-
Full reset, option 4 factory reset. Hooked in serial port too 115200, still no web configurator. Had cox reset modem twice to be sure my static ip is recognized, but without a configurator, the router doesn't work. Possibly there are some Linux commands, I'm a Windows person, that need to run?
-
How are you connected to the firewall?
After a config default the firewall LAN IP is at 192.168.1.1. What does it show at the console above the menu? Is it conflicting with the WAN?
-
@stephenw10 I had some help from the TAc. Their suggestion was to have a separate connection via wireless and a serial connection using a single laptop. The suggestion and help had a new gateway on the LAN which turned out to be not blocked
I was in the mess to start with by breaking the rebind rule (?firewall?) where a published website to an SSL certified site was "rebind" bound to two up addresses. This was a simulated attack and somehow closed down the second "bound" site which was the gateway.
The issue has now persisted - there's an error about vhd_getprocess and the webConfigurator.pid in the past not being there to kill and the rc.web.conf. I may be able to give more information when it comes up again.
But after fix the issue returned.
-
Hmm, what exactly was the fix there?
-
@stephenw10 one item was to change the gateway so I could log into the web configurator. It worked for a while but only when companioned with an old WPA2 router being replaced. Removing the old router caused a recurrence.
-
So setting a different upstream gateway in pfSense? Or in a local client?
From that error it seems more likely you had a local IP conflict that prevented access to pfSense. Presumably the 'router' device you replaced with the old one?
-
Exactly that. The router called it a "rebind". The SSL was tied to the gateway after it was designated to another server.
Looks like I may be able to recover- I see the configurator lists as pfsense.home.arpa. I did a full reset to factory. I'm guessing that's where the configurator default lives. Only issue now is because I converted all the machines to a new gateway, resorting the configuration will likely flip it back to the blocked gateway post rebind.
Otherwise looks good. I'm going to sit in it and think about the process prior to restore.
Thanks for your reply!
-
@Jamie22 - For what it's worth - I had the same issue today (Firefox) and it wasn't until I closed the browser and opened the address in another tab that it went away. It happened to me twice.
-
Yes if you had some other router that resolved to the same IP and then use that same URL after swapping in pfSense it will show a rebind error.
