Netgate SG-1000 microFirewall

Author Topic: 502 Bad Gateway (nginx) after Update to 2.3  (Read 24363 times)

0 Members and 1 Guest are viewing this topic.

Offline BeerCan

  • Jr. Member
  • **
  • Posts: 92
  • Karma: +9/-0
    • View Profile
Re: 502 Bad Gateway (nginx) after Update to 2.3
« Reply #90 on: December 07, 2017, 08:42:30 pm »
Are you sure the "Enable DNSBL" box is also disabled? (not only the "Enable pfBlockerNG")

OK I went through all of the feeds and it is dansguardian that is blocking the patch system (I xx out my uid) 
https://lists.malwarepatrol.net/cgi/getfile?receipt=xxxxxxxxxxx&product=8&list=dansguardian

found this blocks it as well  https://malc0de.com/bl/BOOT


Do others have this enabled and are able to attach to the patch system?
« Last Edit: December 07, 2017, 09:30:48 pm by BeerCan »

Offline Olman

  • Newbie
  • *
  • Posts: 15
  • Karma: +0/-0
    • View Profile
Re: 502 Bad Gateway (nginx) after Update to 2.3
« Reply #91 on: December 15, 2017, 12:33:42 pm »
2.4.2; haproxy ; cluster

main - patch installed from this thread ; backup -not installed ;
bot are behave, with patch seems a bit better (but I'm not sure), but actively using web management,  cause a problem, an early evidence, it cant sync HA config, starting throwing sync errors , then everything collapsed ....

so far my understanding since my use of pfsense version 1 ( 2009 i think) , any add-on installed , caused a potential instability ... you may get lucky it works well, or it may hang after a couple month of usage ....

so far are great product , but adding some add-on .... think twice ....  that sad ...