Web interface unresponsive

StitchTech · Aug 31, 2012, 2:56 PM

I have the same issue and I can't make changes using the GUI because it's so unresponsive. I generally get a login prompt after a long wait when trying to connect but when I put in my username and password it usually comes back with a 503 - Service Not Available error. I'm a Linux newbie (but a CCNA so I know my way around a network) so I don't have a clue how to make the changes recommended in this thread by editing the config files. Any help would be greatly appreciated. I'm running a Dell T110 server with 500GB disk drive. I have three LANs along with the WAN all using the Dell bce ports on the two installed NIC cards.

Bittone66 · Mar 28, 2013, 7:32 AM

Hello people,
same problem here: 2.0.2, AMD 64 on a Della 2950 server 1 Opteron dual core CPU, 8 GB ram, 2 broadcom + 4 intel Eth Adapter.
I'm running Squid a revrse proxy, multiple OPENVPN tunnels, FreeRADIUS 2, IPSEC VPN as server.
Bye

A.T.

CDuv · Sep 12, 2013, 2:42 PM

@computermad:

see if u hv incorrect settings on the ldap auth.
I got mine fixed after removing the inactive ldap server entries from the user auth. setting.

Also happens when there is DNS resolving issues with the LDAP(s) server(s) FQDN :

Sep 12 14:27:39 pfsense php: /status_services.php: ERROR! ldap_get_groups() could not bind to server MyCompany. : Can't contact LDAP server

One advice is to set an IP address in "Authentication Servers" config page (or to have complete faith into it's DNS server to respond).

jimp · Sep 12, 2013, 3:00 PM

@CDuv:

One advice is to set an IP address in "Authentication Servers" config page (or to have complete faith into it's DNS server to respond).

That would work with plain LDAP, but with LDAP+SSL, a hostname is required (and it must match the hostname of the LDAP server's certificate CN also)

turbo · Feb 6, 2016, 6:04 PM

Thought I bring this old post up as it happens still with 2.2.5 i386. After initial start the system runs just fine for weeks/a few month. Traffic is still going as supposed. Happened a lot lately and I fixed every time with a "cold start". Now I know a smoother way.

I was used to have the system running without a keyboard. Wanted to edit some rules and no response. Searched and found this thread. Attached a keyboard, and entered from jimp mentioned commands into the shell.

killall -9 php
killall -9 lighttpd
/etc/rc.restart_webgui

or just enter Option 11 (Restart webconfigurator)

Problem solved. :D
Guess have to keep the keyboard attached now. :(

hollister · Sep 13, 2016, 6:52 PM

Still seems an issue with 2.3.2-RELEASE (amd64)
built on Tue Jul 19 12:44:43 CDT 2016
FreeBSD 10.3-RELEASE-p3
Webgui not really responsive, I can wait up to 1min just to get the login screen and then things work.
Hardware APU or AMD G-T40E Processor

alexjensen · Sep 14, 2016, 1:14 PM

I'm not sure if this is related to your issue but I was having trouble with php-fpm / web console crashes a few weeks back while running on 2.3.2, I also read somewhere that people on 2.3.1 were having similar problems.

If you're using them, try removing the IPSec and/or OpenVPN widgets from the web console home page.

I don't know which widget was causing the problem for me but I haven't had any issues for almost 3 weeks now, previously was having an incident (web console crashing and dial in OpenVPN connections breaking and 1 incident of IPSec VPN becoming unresponsive) weekly.

hollister · Sep 17, 2016, 3:39 AM

I only have the following widgets:
System Information, Interfaces, Services Status, NTP Status, Installed packages, Thermal Sensors
For now I removed Installed packages
will see if there is any improvment on the next logon

tonymorella · Sep 20, 2016, 5:46 AM

@hollister:

I only have the following widgets:
System Information, Interfaces, Services Status, NTP Status, Installed packages, Thermal Sensors
For now I removed Installed packages
will see if there is any improvment on the next logon

If you are using a PC engines board disable hardware TCP Seg and large receive offloading and see if this helps. I noticed a huge difference.

MatthewH · Sep 22, 2016, 2:13 PM

This morning the web GUI wouldn't load. I'm running 2.3.2. Tried it in IE & Chrome on 2 computers in different subnets with same result. Tried using IP address & FQDN, same result. I got a warning about an invalid https certificate, which I shouldn't & don't usually get, and when I told the browser to proceed anyway it just sat trying to load. There were no messages on the console since when I successfully logged in yesterday.

Console options 16, then 11 fixed it.