New 502 Bad Gateway
-
Is 2.4.1 supposed to fix this without the updated files here?
I saw the redmine ticket was closed due to a new version of pfbng fixing this. Is that automatically installed in 2.4.1? I'm not seeing a package update on my 2.4.1 RELEASE box.
-
If you ran the 2.4.1 update after the new package was uploaded (2.1.2_1) then it would pick up the new files automatically.
-
I still have 502 issue when use pfSense 2.4.1 and pfblockerng 2.1.2_1. :(
-
Still having the issue after 2.4.1, had to disable DNSBL again.
-
Hey all,
Try disabling the Dashboard auto-update check. It seems unrelated, but I made this change last weekend and my system has been stable ever since.
-
I am also experiencing this issue. Error 502 Bad Gateway roughly every 15 hours. Latest version of pfSense and pfBlocker as of the date of this post. I'd post the actual versions but I need to reboot the router to get into the GUI and I can't afford to take down the internet here at this very moment.
As a side note, I've used pfSense for years now and this '502 Bad Gateway' seems to be a reoccurring theme..
-
Running 2.4.1 and 2.1.2_1 and still getting 502 but also getting a few crash reports to send in each day as well.
PHP ERROR: Type: 1, File: /usr/local/pkg/pfblockerng/pfblockerng.inc, Line: 2496, Message: Allowed memory size of 536870912 bytes exhausted (tried to allocate 8192 bytes) @ 2017-10-28 07:02:39 -
Hi,
same here - updates onto last version of pfsene & pfblocker - after about a day it becomes unresponsive.
-
Disabling Snort and it's updates has kept me up and running for 2 days now. I'm going to wait another day and then re-enable snort and see what happens. Perhaps Snort needs the same changes that pfblocker has gotten.
-
I made some additional mods to the code. Run the following command to download the patched version from my Github Gist:
fetch -o /usr/local/pkg/pfblockerng/pfblockerng.inc "https://gist.githubusercontent.com/BBcan177/7ff15715be0f02afdbe0a00c676aedce/raw"Recommend a reboot after downloading the patch.
Please let me know your feedback!
-
For me after 2.4.1-RELEASE (amd64) and pfBlockerNG 2.1.2_1 Finally no more err 502 or 504. Open VPN keep connections.
Sistem running for 2 Days 09 Hours 02 Minutes 23 Seconds. Before i had issues after 6-9 hrs.
Many thnx fo all.
-
Hey all,
Try disabling the Dashboard auto-update check. It seems unrelated, but I made this change last weekend and my system has been stable ever since.
Well it finally failed after a week of being stable…
-
I made some additional mods to the code. Run the following command to download the patched version from my Github Gist:
fetch -o /usr/local/pkg/pfblockerng/pfblockerng.inc "https://gist.githubusercontent.com/BBcan177/7ff15715be0f02afdbe0a00c676aedce/raw"Recommend a reboot after downloading the patch.
Please let me know your feedback!
I installed this today and after 6 hours of running my pFsense VM increased disk usage of over 20gb and crashed the VM and needed to be rebuilt.
-
I installed this today and after 6 hours of running my pFsense VM increased disk usage of over 20gb and crashed the VM and needed to be rebuilt.
I don't think the patch would have done that… Confirmed with a few other users. Check your PM for details and we can go from there... Thanks!
-
I made some additional mods to the code. Run the following command to download the patched version from my Github Gist:
fetch -o /usr/local/pkg/pfblockerng/pfblockerng.inc "https://gist.githubusercontent.com/BBcan177/7ff15715be0f02afdbe0a00c676aedce/raw"Recommend a reboot after downloading the patch.
Please let me know your feedback!
I installed this today and after 6 hours of running my pFsense VM increased disk usage of over 20gb and crashed the VM and needed to be rebuilt.
Works on my machines since 4 days without a hassle and without filling up the disks.
What was filled up, did you have had a look on the files? -
I made some additional mods to the code. Run the following command to download the patched version from my Github Gist:
fetch -o /usr/local/pkg/pfblockerng/pfblockerng.inc "https://gist.githubusercontent.com/BBcan177/7ff15715be0f02afdbe0a00c676aedce/raw"Recommend a reboot after downloading the patch.
Please let me know your feedback!
I installed this today and after 6 hours of running my pFsense VM increased disk usage of over 20gb and crashed the VM and needed to be rebuilt.
Works on my machines since 4 days without a hassle and without filling up the disks.
What was filled up, did you have had a look on the files?I checked BBcan's pm and started the process again and keeping check on a few things this time. I couldn't check when it happened though as it had reached 109% storage and the VM crashed and when I rebooted it, it took everything with it. Configs for all services where 95% lost (like 3 DHCP mappings remained of a list of 200+, lost all NAT/Rules). So I ended up just factory resetting and am now attempting to replicate the findings. I will keep everyone updated as the day progresses.
-
2.4.1-RELEASE (amd64) and pfBlockerNG 2.1.2_1 which has been just fine until this morning. I now get the 502 bad gateway again. I installed the two patch files as well prior to the update to 2.1.2_1. I don't know when I lost access since the system will continue to run but I think I looked at the GUI yesterday.
I just installed the most recent change from the previous page so ignore this until I have more time to keep an eye on it. I read past the 3rd file thinking it was one of the previous files.
-
I've been struggling with this same issue on two devices (SG-2240 and SG-4860) since this thread was created as well. I'm currently on the 2.4.1 release with the latest pfblockerng, snort and squid/squidguard packages. In all cases, it seems like this issue is encountered at the stroke of midnight. I've been ready to capture the console text but like other users have reported, the console stops responding completely so I can't capture the data requested.
Last night, I looked at all the cron jobs that were kicking off around midnight and there were several that were happening at exactly midnight. I modified them to have at least 5 minutes separation to see if that might help. I've also tried pausing pfblockerng and snort and still get the 502.
Just thought I would also report this is still an on going issue.
-
I've already posted it once, but a ZFS install cured all my issues. Even on 2.4.0 and pbng 2.1.2
-
Hi, All
Is it just the pfBlockerNG DNSBL issue? Can I turn on the IPv4 blocks only? I have upgraded to 2.4.1 (ufs) already, pfBlockerNG is disabled due to the issue, but I really want to turn it on. Thanks.
