• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

502 Bad Gateway (nginx) after Update to 2.3

Problems Installing or Upgrading pfSense Software
44
93
57.9k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B
    billyjp
    last edited by Apr 21, 2016, 8:28 AM

    Hello!

    First at all the new Design since Ver. 2.3 looks great!

    But since i update to this Version i have the Error "502 Bad Gateway (nginx) in the Browser if i try to connect to the Firewalls GUI. This error comes about after 3-5 days. A restart solve the problem. But this is not the best way!

    Can anybody help me how to fix this problem.

    THX

    1 Reply Last reply Reply Quote 0
    • V
      v4rp1ng
      last edited by Apr 21, 2016, 12:22 PM

      Same here.

      And now after the upgrade I get some strange errors on the webinterface (see attachment).
      Already tried to reinstall the systempackages with Diagnostics > Backup & Restore > Reinstall Packages but it seems it's not functioning too.

      pfsense.png
      pfsense.png_thumb

      1 Reply Last reply Reply Quote 0
      • J
        jwilling
        last edited by Apr 21, 2016, 7:59 PM

        Also experiencing the 'Bad Gateway' issue since the update.

        Occurring here almost daily and having to repeatedly reboot the system to clear it is not an acceptable option.

        1 Reply Last reply Reply Quote 0
        • D
          dusan
          last edited by Apr 21, 2016, 8:28 PM

          There are several threads about error 502/504 . For example, https://forum.pfsense.org/index.php?topic=110116.0

          1 Reply Last reply Reply Quote 0
          • C
            cmb
            last edited by Apr 21, 2016, 8:29 PM

            You don't have to reboot, option 16 at the console will bring it back.

            Not that that's acceptable, we're working on fixing any issues there. The one most people seem to be encountering is:
            https://redmine.pfsense.org/issues/6177

            1 Reply Last reply Reply Quote 1
            • B
              billyjp
              last edited by May 6, 2016, 10:19 AM

              Thank you for this info.

              Is it possible to force the option 16 ofer ssh?

              When i log in my pfsense over SSH i just see the consol input window without any options to choose (1,2,3,…)

              Screenshot_3.png
              Screenshot_3.png_thumb

              1 Reply Last reply Reply Quote 0
              • J
                Jailer
                last edited by May 6, 2016, 2:19 PM

                @billyjp:

                Thank you for this info.

                Is it possible to force the option 16 ofer ssh?

                When i log in my pfsense over SSH i just see the consol input window without any options to choose (1,2,3,…)

                service nginx restart
                
                1 Reply Last reply Reply Quote 0
                • D
                  Den
                  last edited by May 6, 2016, 4:02 PM

                  I had the same problem on clean install of 2.3. Restarting PHP-FPM and webConfigurator didn't help, had to reboot.

                  1 Reply Last reply Reply Quote 0
                  • J
                    jahonix
                    last edited by May 6, 2016, 6:12 PM May 6, 2016, 6:08 PM

                    @billyjp:

                    Is it possible to force the option 16 ofer ssh?

                    /etc/rc.php-fpm_restart

                    @Jailer:

                    service nginx restart

                    might give you: "Cannot 'restart' nginx. Set nginx_enable to YES in /etc/rc.conf or use 'onerestart' instead of 'restart'."

                    And "rc.restart_webgui" gives you option 11 "Restart webConfigurator" from console.

                    1 Reply Last reply Reply Quote 0
                    • C
                      cmb
                      last edited by May 7, 2016, 7:24 AM

                      service commands don't do anything, don't run them. If you don't get the console menu, you're not logging in as root. You'll need the sudo package, then run sudo /etc/rc.initial

                      1 Reply Last reply Reply Quote 0
                      • J
                        jahonix
                        last edited by May 7, 2016, 11:44 PM

                        You learn something new every day.
                        Thanks!

                        1 Reply Last reply Reply Quote 0
                        • ?
                          Guest
                          last edited by May 10, 2016, 11:44 PM May 10, 2016, 8:48 PM

                          Disabling the automatic dashboard auto-update check at /system_update_settings.php seems to mitigate the issue for now.

                          edit: i'm getting more and more the feeling that the issue is somehow ipv6 related..  still investigating.

                          1 Reply Last reply Reply Quote 0
                          • B
                            billyjp
                            last edited by May 11, 2016, 8:19 AM

                            Thanks for this tipp.

                            Can anyone approve this? I dont want to change to much important on my Main Firewall. But the nginx error comes no every 3 days  :-[

                            1 Reply Last reply Reply Quote 0
                            • L
                              luckman212 LAYER 8
                              last edited by May 18, 2016, 12:05 PM

                              Just want to chime in since I feel the 2.3.1 release is imminent

                              I got this 502 Bad Gateway nginx error for the first time today.  Had never seen it before.  I am actually running a 2.3.2 snapshot according to the dash, based on 2.3.1.a.20160516.0651.  I have been tracking the dev branch - Not sure how I landed on 2.3.2 but I assume that whatever fix was in for this should have been in there.  So I don't believe that this is fixed. yet.

                              I do have the auto-update check enabled on my dashboard.

                              I did leave the dashboard page "up" in a browser window overnight so I guess it was sitting there for a long time refreshing every so often.

                              I do have the IPSEC dashboard widget turned on, with 2 tunnels that are both "UP"

                              This is on an SG2440

                              My logs were filled to the brim with the error below:

                              nginx: 2016/05/18 07:54:28 [error] 50536#0: *6944 connect() to unix:/var/run/php-fpm.socket failed (61: Connection refused) while connecting to upstream, client: 2604:2000:xxxx:xx::116e, server: , request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "r1.xxx.xxx:8888"
                              
                              

                              I run my webconfigurator on HTTP port 8888

                              Not sure if that gives any clues

                              Screenshot below

                              1 Reply Last reply Reply Quote 0
                              • A
                                Ambivalent
                                last edited by May 18, 2016, 4:39 PM

                                So after having this issue multiple times a day I dug and dug and dug and found the thing that fixed it for me. This will apply to you if, like me you had been leaving the main firewal page open with the widgets. This error appears to be caused by a widget. In my case I had to close my OpenVPN status widget and it stopped killing PHP and apparently that kills the whole thing until you reboot. This may or may not apply to you but it's easy to test and not a terrible workaround for now.

                                1 Reply Last reply Reply Quote 0
                                • L
                                  luckman212 LAYER 8
                                  last edited by May 18, 2016, 5:12 PM

                                  I think the IPSec widget also causes this.  Not sure why that is.  Interesting info- not really a fix but it's a workaround.  Sadly, at least for me those 2 widgets are among the most useful ones to see at a glance.

                                  1 Reply Last reply Reply Quote 0
                                  • P
                                    phil.davis
                                    last edited by May 19, 2016, 2:38 AM

                                    Make sure to retry all the widgets after upgrading to 2.3.1-RELEASE.
                                    Then this can move forward if there are more issues reported.
                                    The problems are related to the widgets doing updates every 10 seconds or so, asking the nginx server to do stuff. nginx gives the PHP to back-end PHP processes to do the work. If those things get delayed (or hung) too much then all the PHP processes get busy and nginx will have to give up.

                                    As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                                    If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                                    1 Reply Last reply Reply Quote 0
                                    • C
                                      Christos
                                      last edited by May 20, 2016, 6:22 AM

                                      Got the 502 Bad Gateway error with 2.3.1  :( :( :(

                                      1 Reply Last reply Reply Quote 0
                                      • G
                                        gordc
                                        last edited by May 26, 2016, 1:21 PM

                                        Has anyone been able to figure out what is happening with this.  I get this every couple of days and the only resolution is to take the 20 minute walk to physically restart the firewall. 
                                        I can log in using ssh but the majority of the commands either give an error on execution or don't work.  When I log in I don't get a menu.  I start the menu with /etc/rc.initial
                                        After that if I use options 11 or 16 I get errors
                                        Restarting webConfigurator…Error: cannot open /var/etc/nginx-webConfigurator.conf in system_generate_nginx_config().

                                        Fatal error: Call to undefined function pfSense_interface_listget() in /etc/inc/interfaces.inc on line 80
                                        PHP ERROR: Type: 1, File: /etc/inc/interfaces.inc, Line: 80, Message: Call to undefined function pfSense_interface_listget()
                                        Fatal error: Call to undefined function gettext() in /etc/inc/rrd.inc on line 60
                                        PHP ERROR: Type: 1, File: /etc/inc/rrd.inc, Line: 60, Message: Call to undefined function gettext()

                                        Killing php-fpm
                                        pkill: signalling pid 737: Operation not permitted
                                        /etc/rc.php-fpm_restart: cannot create /tmp/php_errors.txt: Permission denied
                                        Found XMLRPC lock. Removing.
                                        rm: /tmp/xmlrpc.lock: Operation not permitted
                                        Starting php-fpm
                                        [ERROR] unable to bind listening socket for address '/var/run/php-fpm.socket': Address already in use (48)
                                        [ERROR] FPM initialization failed

                                        If I use option 5 to try to restart the system I get the prompt asking me to continue but the system does not reboot.

                                        I have also tried /etc/rc.initial.reboot
                                        Again I get the prompt asking to proceed but the system does not reboot.

                                        This is costing me too much time.

                                        1 Reply Last reply Reply Quote 0
                                        • J
                                          jahonix
                                          last edited by May 26, 2016, 5:49 PM

                                          Just upgrade to 2.3.1_1 which was released today.

                                          1 Reply Last reply Reply Quote 0
                                          • First post
                                            Last post
                                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.