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

    Can't login to WebGUI after a couple of days

    Scheduled Pinned Locked Moved webGUI
    35 Posts 17 Posters 8.9k Views
    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.
    • 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
                • S
                  Sashi
                  last edited by

                  I have been having 504 timeout issue since last once week now. No updates and no additional package installed lately. I am currently using pfSense version 2.3.2 with standard settings, pfBlockerNG & Snort is configured and the services are executing as expected.

                  I am able to access the shell and the firewall is running smooth without any issues. Can someone please shed some light, thanks in advance.

                  In the meantime, i have changed below values;

                  max_execution_time = 900 -> /etc/php.ini
                  request_terminate_timeout = 300 -> /usr/local/etc/php-fpm.conf

                  
                  2016/08/16 20:42:58 [error] 20217#0: *1 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 10.10.10.101, server: , request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "10.10.10.1", referrer: "http://10.10.10.1/"
                  2016/08/16 21:26:02 [error] 18966#0: *1 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 10.10.10.101, server: , request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "10.10.10.1", referrer: "http://10.10.10.1/"
                  2016/08/16 21:33:05 [error] 18966#0: *5 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 10.10.10.101, server: , request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "10.10.10.1", referrer: "http://10.10.10.1/"
                  2016/08/17 09:51:20 [error] 20268#0: *1 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 10.10.10.101, server: , request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "10.10.10.1", referrer: "http://10.10.10.1/"
                  2016/08/17 16:41:59 [error] 18589#0: *9 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 10.10.10.101, server: , request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "10.10.10.1", referrer: "http://10.10.10.1/"
                  2016/08/17 16:49:59 [error] 18589#0: *20 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 10.10.10.101, server: , request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "10.10.10.1", referrer: "http://10.10.10.1/"
                  2016/08/17 17:13:56 [error] 18589#0: *23 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 10.10.10.101, server: , request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "10.10.10.1"
                  
                  
                  1 Reply Last reply Reply Quote 0
                  • V
                    vronp
                    last edited by

                    Finally, after weeks, I determined that it was pfblockerng that was causing the 504 errors.

                    I disabled pfblockerng and have not had a problem with the GUI since.

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

                      How can I disable pfblockerng

                      1 Reply Last reply Reply Quote 0
                      • BBcan177B
                        BBcan177 Moderator
                        last edited by

                        @vronp:

                        Finally, after weeks, I determined that it was pfblockerng that was causing the 504 errors.

                        I disabled pfblockerng and have not had a problem with the GUI since.

                        Can you provide any more details about this issue?

                        If you have a large DNSBL database, it can take some time to reload the Resolver… and if you are logging into pfSense with the Domain name, then you can have some issues at that time... best to use the pfSense firewall literal IP address to login...

                        Also there are some issues with the Resolver and DHCP....  (Hoping the devs provide some feedback...)
                        https://redmine.pfsense.org/issues/5413

                        "Experience is something you don't get until just after you need it."

                        Website: http://pfBlockerNG.com
                        Twitter: @BBcan177  #pfBlockerNG
                        Reddit: https://www.reddit.com/r/pfBlockerNG/new/

                        1 Reply Last reply Reply Quote 0
                        • K
                          KimmoJ
                          last edited by

                          Happens on the latest 2.3.2 also. In fact, just happened to me.

                          I suspect it's this elusive bug: https://redmine.pfsense.org/issues/6406

                          I tried restarting the webconfigurator but it did nothing, never tried the other option as the box is not yet live, just rebooted.

                          Apparently it's more likely to happen if you leave the web page up for a period of time.

                          Thankfully it doesn't affect SSH, and it doesn't affect functionality, so it's an annoyance rather than a bona fide forest fire emergency.

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