I can't open the GUI
-
Hi,I can't open the GUI; suddenly this message appeared: "The web server encountered an error processing this request" What's the right way to solve that issue ?
Thanks. !
-
@Alamoodi I guess the first step is, do not disclose any information ;)
What pfSense version, what URL did you try to access? Did you make any configuration changes before? Can you access pfSense by SSH or on the console? Is pfSense running on hardware or in a virtual machine?
-
@patient0 Thnks for advice.
I don't know what's the version, I can't access by SSH, and I didn't try with console; if I can access it over console what should I do to solve it. -
@Alamoodi did you try to access the x.x.x.x/ URL or a subpage. Have you been logged in at the time?
To restart the GUI, there is the console menu point 11) Restart GUI.
Netgate got an excellent troubleshooting guide: pfSense: Troubleshooting GUI Connectivity
The
sockstat | grep nginxwould be the start to check that the GUI still runs and on the correct ports.Then the nginx logs,
/var/log/nginx/error.log,/var/log/nginx.log* -
@patient0 I'll try it and get back.
-
@patient0 I can't access by console, how I can make manually reboot by hand.
8300MAX -
@Alamoodi what problem are you having with console access
https://docs.netgate.com/pfsense/en/latest/solutions/netgate-8300/connect-to-console.html
As to your ssh trouble - was it enabled, trying to remember but I don't believe ssh is enabled out of the box? Pretty sure it has to be enabled??
-
-
I chang speed to 115200 and shwoing like this
-
After I prompt command "reboot" and GUI in "the connection has timed out"
And SSH by console dosen't open again!
-
@Alamoodi said in I can't open the GUI:
I chang speed to 115200 and shwoing like this
The speed setting for serial is crucial, now it seems your are already in a shell but the prompt is strange.
echo $SHELLwill show in what shell your areidwill show the current usersudois not installed since only the root user is used
But you show see a console menu when connecting to the console. Or get back to it be typing
exit
Let's see how the reboot goes.
-
@patient0 Not seen menu at all, only #, and nothing appear now!
-
@Alamoodi said in I can't open the GUI:
Not seen menu at all, only #, and nothing appear now!
What is
echo $SHELLshowing andls /boot? -
If I do manually off with press one time power button it will work?
-
-
@Alamoodi said in I can't open the GUI:
If I do manually off with press one time power button it will work?
I would assume so but I don't have an 8300.
Btw: I see the 8300 got an out-of-band management interface, Netgate 8300: Intelligent Platform Management Interface (IPMI)
-
@patient0 yeah the 8300 is different animal with the IPMI - so there might be some differences in how that is setup for your typical console and what/how you access it.
I don't have one to play with either :(
Your typical console should show you normal prompt, but you might have to type exit to get it
Here I just consoled into my 4860, see just # prompt, type exit and it brings up the normal menu
-
@johnpoz Thank you for all,
I did manually turn off with power switch at back and turn on again after a minute.
It's working good now. -
@Alamoodi Great, I would take a bit of time and validate you have console/ssh access - in case of future need. Always good to plan ahead for such a need.
I would validate console works, and how to access it. Would also leverage the IPMI and make sure it works and setup how you want.
And make sure you can ssh to it.
edit:
Personally other than first time setup scenarios have had really no actual need of console access. But I do like to connect to it when I run an upgrade to watch progress, etc.I leave my console cable connected to the 4860, just coiled up in the rack under my desk. Simple open rack door and grab the cable and connect to my pc and instant console access ;)
-
Also : now you've your system back up, and ssh works, and the console works, and you know how to use the IPMI works (wow, didn't even know the 8300 had that access : just great !), go to the /var/log/ folder ans save all the logs files.
It's very possible that you find in the system.log (or older, rotated versions of that file) what the reason was things went wrong in the first place.Get, for example WinSCP, you can use the SSH credentials and SSH port 22, to access the pfSense file system like Windows explorer.
If you can't find anything, start by adding a UPS.
