504 or 502 Gateway Timeout Error NGINX when accessing the webgui
-
I just installed and setup snort and things seemed well, until about an hour late I started having issues trying to access my WebGUI page to look at the alerts and started getting the 504 Gateway Timeout Error NGINX page when trying to access the GUI for pfsense. I then rollback my installation of snort thinking that was the issue, and now i get this error every time i try to access the WEBGUI. I restarted the PHP-FPM and it works for about 5 minutes then the error happens again. I have to keep restarting the PHP-FPM and it keeps happening. Any suggestions on how to resolve?
Version: 2.3.3-RELEASE-p1 (amd64)
My log show the error below:
<171>1 2017-05-01T10:21:34-05:00 caesarsnetwork.localdomain nginx - - - nginx: 2017/05/01 10:21:34 [error] 22340#100111: send() failed (54: Connection reset by peer)
<174>1 2017-05-01T10:21:34-05:00 caesarsnetwork.localdomain nginx - - - nginx: 192.168.1.55 - - [01/May/2017:10:21:34 -0500] "GET /vendor/font-awesome/css/font-awesome.min.css HTTP/1.1" 200 7038 -
Sounds like you have something consuming php processes.
You can increase the number of processes available in System > Advanced > Admin Access. Try setting 'Max Processes' to 4 or 6. Or higher if you have RAM available.
Steve
-
That looks normal yes. Except Snort is still there so it wasn't removed. How did you remove it?
Steve
-
I used the remove package feature in the packages? was this not correct?
-
Ok so this is what i Did just to see if it was snort.
I did a fresh install and used a config from two weeks ago and all is well.
So all i did was go to the available packages and installed Squid proxy, did not set it up at all. I walked away for ten seconds to check on something come back and the browser just spins and 504 gateway timeout error. Literally, nothing was done except the squid package install. Any suggestions as to why just installing a package would cause this to happen? -
So you restored a config from when you had packages installed?
Squid can behave oddly when installed and not configured on occasion. Check the system log to see if it's continually restarting.
Steve