Usually this works but sometimes a reboot of pfSense is needed. After 15 to 60 minutes, I am back with the same problem, often even WAN connection drops. Often this can be solved by using SSH and select option 16. ![]() The latest year I started to get 502 Bad Gateway, nginx. Nov 18 17:06:30 pfSense nginx: 8 17:06:30 83498#100152: *2302 connect() to unix:/var/run/php-fpm.socket failed (61: Connection refused) while connecting to upstream, client: ClientIP, server:, request: "GET /widgets/widgets/snort_?getNewAlerts=1637251590358 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "pfSenseIP", referrer: " Nov 18 17:06:30 pfSense nginx: ClientIP - "GET /widgets/widgets/snort_?getNewAlerts=1637251590358 HTTP/1.1" 502 552 " "Mozilla/5.0 (Windows NT 10.0 Win64 圆4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/.45 Safari/537.36" Running latest pfSense on an Intel NUC and this issue has been escalating. Replaced the actual IPs with ClientIP and pfSenseIP. Everything seemed to work until today when I logged on pfSense.Īfter some minutes I got a freeze, 502 Bad Gateway, this is what the logs say:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |