504_Gateway_Time-Out/Nginx problem
-
I tried going to the 2.3.1 build and can confirm this issue transfers over as of the latest version of 2.3.1. I have how ever; removed all of my widgets (except system info since one widget is needed to still be up), rebooted my box, and then re added my widgets back. I didn't see any problems in the system logs about nginx before rebooting and re adding my widgets back. Will continue to test this method further and return if resolved or not.
-
If this is related to the below linked bug, it has been logged and assigned as high priority for 2.3.1, however, no work has been done on it yet(hence the problem being in the snaps). Has anybody had any luck figuring out what command can be used to restart php-fpm? It's starting to get really annoying as OpenVPN also breaks(now I've had to open up SSH externally so I can restart php-fpm remotely, I'm not a fan of that), this is an issue in our production environment.
https://redmine.pfsense.org/issues/6177
-
If this is related to the below linked bug, it has been logged and assigned as high priority for 2.3.1, however, no work has been done on it yet(hence the problem being in the snaps). Has anybody had any luck figuring out what command can be used to restart php-fpm? It's starting to get really annoying as OpenVPN also breaks(now I've had to open up SSH externally so I can restart php-fpm remotely, I'm not a fan of that), this is an issue in our production environment.
https://redmine.pfsense.org/issues/6177
Not sure if its exactly the same but I haven't ran into this nginx issue (so far). It usually throws so many log errors by midnight and thru the day till it breaks. I noticed after the procedure I did that my ipsec widget was still throwing up the nginx error. I removed the widget and haven't ran into an issue. If you can reproduce my workaround (2.3.1 might not be necessary) but try to remove all the widgets if possible (reboot if possible), and if any widgets are throwing up the error remove them for awhile. Periodically re add them to see if waiting it out will get them to work well with each other. I have OpenVPN and IPSec and have just recently been using IPSec more often. I can't say if I can't access either VPN while my issue persist as I can even ssh locally from my main computer to my pfsense box to issue the php restart. Lastly Im not sure if there is a command (at least currently known) that can automatically issue a php restart.
-
I just found another topic discussing this very same issue, apparently it is caused by the IPSec widget.
https://forum.pfsense.org/index.php?topic=110116.0
-
I'm having this exact same problem on 3 SG appliances, and one VM.
It happens almost every day on mu home VM, and the appliances has happened once each since upgrading to 2.3
Does anybody know what command is issued by using option 16? I'd like to just add a cron until this issue is verified and hopeully makes it into 2.3.1
Option 16 runs /etc/rc.php-fpm_restart
Option 11 runs /etc/rc.restart_webgui
I added both of them to an hourly cron job a minute apart, and I have not been locked out by a 50? error since. Not really a fix, but it does seem to be a workaround of the problem.
For completeness, if anyone doesn't want to change the crontab using shell access, there is a cron package that will do the same thing from the web_gui.
-
Hi All,
There are some notes back in this thread also regarding widgets and also auto update: https://forum.pfsense.org/index.php?topic=109812.msg616466#msg616466
Just Fyi.
-
Here maybe a possible fix? https://forum.pfsense.org/index.php?topic=111475.msg621734#msg621734
-
This was more than likely fixed with 2.3.1_1.
-
@cmb:
This was more than likely fixed with 2.3.1_1.
I installed two new pfSense 2.3.1_1 VMware machines. I left out my cron job to restart PHP and the wweb gui, and was locked out of both within a day. I don't think it's fixed. At least not the community edition. Not sure about the hardware version.
-
I installed two new pfSense 2.3.1_1 VMware machines. I left out my cron job to restart PHP and the wweb gui, and was locked out of both within a day. I don't think it's fixed. At least not the community edition. Not sure about the hardware version.
There are many possible causes of this symptom. Most of those possibilities were fixed in 2.3.1, 2.3.1_1 and/or 2.3.1_5.
The original issue here was the update checking issue, which then was hijacked to the nanobsd read-write mount issue. Both of those are fixed. Locking this thread so it won't keep getting hijacked.
If you're having the same symptom, please start a new thread describing when it happens, what you're running on the system, etc.
