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

    Can't login to WebGUI after a couple of days

    webGUI
    17
    35
    8.8k
    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.
    • C
      cmb
      last edited by

      Most if not all remaining instances of 504 gateway timeouts were fixed in 2.3.1_1.

      1 Reply Last reply Reply Quote 0
      • V
        vronp
        last edited by

        @cmb:

        Most if not all remaining instances of 504 gateway timeouts were fixed in 2.3.1_1.

        I'm still experiencing the problem with 2.3.1_1

        Dave

        1 Reply Last reply Reply Quote 0
        • 2
          2chemlud Banned
          last edited by

          +1

          2.3.1_1 64bit full, especially when re-starting a snort interface.

          Intel(R) Atom(TM) CPU D525 @ 1.80GHz 4 CPUs, with 4 GB RAM and 120 GB SSD.

          1 Reply Last reply Reply Quote 0
          • A
            afreaken
            last edited by

            I just had this happen at our remote site, not using the ipsec widget.

            Netgate SG-2440

            2.3.1-RELEASE-p1 (amd64)
            built on Wed May 25 14:56:42 CDT 2016

            1 Reply Last reply Reply Quote 0
            • A
              afreaken
              last edited by

              @afreaken:

              I just had this happen at our remote site, not using the ipsec widget.

              Netgate SG-2440

              2.3.1-RELEASE-p1 (amd64)
              built on Wed May 25 14:56:42 CDT 2016

              Just happened to our local pfsense box, same as above (2.3.1_1). Will try to restart the web interface from console.

              1 Reply Last reply Reply Quote 0
              • luckman212L
                luckman212 LAYER 8
                last edited by

                https://redmine.pfsense.org/issues/6396 is marked closed.  Is that a different bug, or should it be re-opened? I know there are 502's and 504's going on.

                In any case, what is the correct redmine ticket for the remaining issue being discussed here?

                edit: I found https://redmine.pfsense.org/issues/6406  which seems to be "this"

                1 Reply Last reply Reply Quote 0
                • A
                  afreaken
                  last edited by

                  @luckman212:

                  https://redmine.pfsense.org/issues/6396 is marked closed.  Is that a different bug, or should it be re-opened? I know there are 502's and 504's going on.

                  In any case, what is the correct redmine ticket for the remaining issue being discussed here?

                  edit: I found https://redmine.pfsense.org/issues/6406  which seems to be "this"

                  I'm getting
                  "504 Gateway Time-out

                  nginx"

                  It just seems to happen randomly. Doing the reset from the console fixes it for some time.

                  My one box was up for ~12 days before it happened, the other was ~9 days. So…

                  EDIT: The widgets I'm using on both are: System Information, Interfaces, Gateways, Traffic Graphs

                  Not sure if that helps. Also running ipsec tunnel between locations.

                  1 Reply Last reply Reply Quote 0
                  • T
                    The Brave Sir Robin
                    last edited by

                    Just happened to me. 2.3.1_1. No IPSec or OpenVPN widgets. 20 days uptime. 504 error. I have an IPSec site-to-site running.

                    :(

                    OpenVPN server also stops working

                    Doing an option 16) Restart PHP-FPM  did allow me to access the web gui but did not fix OpenVPN. Had to restart OpenVPN server to fix OpenVPN access.

                    1 Reply Last reply Reply Quote 0
                    • A
                      afreaken
                      last edited by

                      Happened again a couple days ago… I want to say this problem has persisted through the "fixes" in 2.3.1_1

                      1 Reply Last reply Reply Quote 0
                      • DerelictD
                        Derelict LAYER 8 Netgate
                        last edited by

                        Do people seeing this with any regularity have anything interesting in the system log? Try filtering on frag.

                        Chattanooga, Tennessee, USA
                        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                        Do Not Chat For Help! NO_WAN_EGRESS(TM)

                        1 Reply Last reply Reply Quote 0
                        • A
                          afreaken
                          last edited by

                          @Derelict:

                          Do people seeing this with any regularity have anything interesting in the system log? Try filtering on frag.

                          well… could I make a suggestion, could the "Reset Log Files" button not be the default accept button on the logs settings page, rather than the save button... I was trying to increase the number of logs per page, hit enter and instinctively clicked OK as I read the message, and instantly regretted my decision.

                          Not sure if this is the same error, but I saw a lot of these in the logs before the above happened.

                          nginx: 2016/06/20 08:37:47 [error] 18895#0: *1464191 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 192.168.1.27, server: , request: "POST /status_ipsec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "192.168.10.2:445", referrer: "https://192.168.10.2:445/status_ipsec.php"

                          I see there is an update 5, running update 5 and will report back if it happens again, though it took 9 days of uptime to happen last time.

                          1 Reply Last reply Reply Quote 0
                          • A
                            afreaken
                            last edited by

                            @afreaken:

                            @Derelict:

                            Do people seeing this with any regularity have anything interesting in the system log? Try filtering on frag.

                            well… could I make a suggestion, could the "Reset Log Files" button not be the default accept button on the logs settings page, rather than the save button... I was trying to increase the number of logs per page, hit enter and instinctively clicked OK as I read the message, and instantly regretted my decision.

                            Not sure if this is the same error, but I saw a lot of these in the logs before the above happened.

                            nginx: 2016/06/20 08:37:47 [error] 18895#0: *1464191 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 192.168.1.27, server: , request: "POST /status_ipsec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "192.168.10.2:445", referrer: "https://192.168.10.2:445/status_ipsec.php"

                            I see there is an update 5, running update 5 and will report back if it happens again, though it took 9 days of uptime to happen last time.

                            UPDATE: 10days 8Hours uptime, hasn't happened yet, so maybe the issue has been resolved between release 1 and release 5?

                            UPDATE: 22 Days uptime without issue. I'd say whatever caused my specific issue has been resolved.

                            1 Reply Last reply Reply Quote 0
                            • C
                              cmb
                              last edited by

                              @afreaken:

                              UPDATE: 10days 8Hours uptime, hasn't happened yet, so maybe the issue has been resolved between release 1 and release 5?

                              Several possibilities for that to happen were fixed between update 1 and 5.

                              1 Reply Last reply Reply Quote 0
                              • M
                                matsan
                                last edited by

                                @cmb:

                                Several possibilities for that to happen were fixed between update 1 and 5.

                                Just happened to me in 2.3.1_p5. Same error logged about the thermal sensors and OpenVPN required a restart to allow connections again. I left the WebGUI open during the night on the status screen (my mistake)

                                nginx: 2016/07/01 06:07:42 [error] 49003#0: *57704 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 192.168.17.18, server: , request: "GET /widgets/widgets/thermal_sensors.widget.php?getThermalSensorsData=11467344975628 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "192.168.17.4", referrer: "https://192.168.17.4/"

                                The first message logged is about the IPSec widget:

                                2016/07/01 05:11:08 [error] 49003#0: *57391 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 192.168.17.18, server: , request: "POST /widgets/widgets/ipsec.widget.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "192.168.17.4", referrer: "https://192.168.17.4/"

                                Luckily I am able to login using SSH to an internal host and can then go back to the pfsense box and restart php-fpm (option 16) to get the WebGUI restarted and then restart OpenVPN. With vacations coming up I see a lot of calls from colleagues not being able to connect…  :'(

                                1 Reply Last reply Reply Quote 0
                                • O
                                  odric
                                  last edited by

                                  Hi I have the same problem. A random day the webgui cant access and OpenVPN Client not connect. (by Ldap valitation, localy i dont test)

                                  I have temporally solution by restart PHP-FPM by ssh local connection (option 16 of menu).

                                  I have some error logs like that:

                                  nginx: 2016/07/05 10:20:50 [error] 29511#0
                                  nginx: 2016/07/05 10:20:49 [error] 29543#0

                                  See attach fille.
                                  It's happens from update 2.2.6 > 2.3.1 and untill 2.3.1-RELEASE-p5 (amd64)

                                  Thanks for your helps
                                  I hope that fix the problem becase if not, i will donwgrade.

                                  pfsenselog2016-07.txt

                                  1 Reply Last reply Reply Quote 0
                                  • A
                                    Artemiy
                                    last edited by

                                    I have the same problem with the latest version 2.3.1-p5 and the older one
                                    It happen randomly.

                                    Hope will be fixed as soon as possible , can't work this way  :'(

                                    1 Reply Last reply Reply Quote 0
                                    • V
                                      vronp
                                      last edited by

                                      p5 still results in:

                                      504 Gateway Time-Out

                                      1 Reply Last reply Reply Quote 0
                                      • V
                                        vronp
                                        last edited by

                                        Ugh, please tell me I'm not the only one still getting this.

                                        I'm getting 502 and 504 errors.  I do the menu choice 16 reset but the problem returns within about 2 minutes or less.

                                        It seems the 502 is tied to the "initial login" but then I get 504 errors afterward.

                                        FreeBSD 10.3-RELEASE-p5

                                        1 Reply Last reply Reply Quote 0
                                        • T
                                          trlizard
                                          last edited by

                                          Hello,
                                          I have same problem, cant access 14.14.14.14
                                          I need log file in pfsense server. how can i get log file.

                                          Ekran.jpg
                                          Ekran.jpg_thumb
                                          ekran1.jpg
                                          ekran1.jpg_thumb

                                          1 Reply Last reply Reply Quote 0
                                          • T
                                            trlizard
                                            last edited by

                                            Web configuration error, while pc is opening.

                                            16.jpg
                                            16.jpg_thumb
                                            web.jpg
                                            web.jpg_thumb
                                            16.jpg
                                            16.jpg_thumb
                                            web.jpg
                                            web.jpg_thumb

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