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

    Web GUI isn't accessible after upgrade

    Scheduled Pinned Locked Moved webGUI
    9 Posts 4 Posters 1.7k 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.
    • Q
      qaiserajaz
      last edited by

      Hey guys,

      Hope you all are good!

      I've recently upgraded my Pfsense from 2.2.6 to 2.3.3 and noticed that I am not able to access my Web GUI. The login page shows up but when I put my credentials and hit login, it takes ages to load and ended up with an error "504 Gateway Time-out nginx". I did some quick search for troubleshooting this issue by restarting option 16) Restart PHP-FPM and 11) Restart webConfigurator but not luck.

      I was not even able to login once after I upgraded to 2.3.3 and I don't have IPSec enabled or have this panel on the dashboard. Could anyone please help me out to fix this issue as I am not really expert in FreeBSD and not sure where to start looking to fix this issue.

      Thanks

      1 Reply Last reply Reply Quote 0
      • Q
        qaiserajaz
        last edited by

        Is there no one who can help me out in this?

        1 Reply Last reply Reply Quote 0
        • w0wW
          w0w
          last edited by

          Did you try to reboot?

          1 Reply Last reply Reply Quote 0
          • Q
            qaiserajaz
            last edited by

            @w0w

            Yes, I rebooted it twice, did everything that I could do, but couldn't make it work.

            1 Reply Last reply Reply Quote 0
            • R
              regis_f
              last edited by

              Did you have a config backup of your system? I think the best solution is to make a clean instalation of pfsense…

              1 Reply Last reply Reply Quote 0
              • Q
                qaiserajaz
                last edited by

                @regis_f

                Yes, I did have the backup and unfortunately, I had to revert back to the previous version 2.2.6 as the upgrade was a terrible experience for me. However, I didn't try with the fresh installation of 2.3.3 and restoring the backup config file into it. I will give it a try and let community know if it works fine.

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

                  im getting the same thing.. i did an upgrade on development branch last night. internet works, but i can not log into the webconfigurator

                  i power cycle the pfsense box

                  i load the login page

                  i enter credentials and hit login

                  browser spins, tried 2 browsers, spins for about 5 minutes or so then

                  
                  <title>504 Gateway Time-out</title>
                  
                  <center>
                  
                  # 504 Gateway Time-out
                  
                  </center>
                  
                  * * *
                  
                  <center>nginx</center>
                  
                  

                  i can never get the login page to load again, even on a different browser

                  have to power cycle

                  this is a repeating cycle.. i dont know what to do

                  
                  *** Welcome to pfSense 2.3.4-DEVELOPMENT (amd64 full-install) on server ***
                  
                   WAN (wan)       -> igb0       -> v4/DHCP4: /23
                                                    v6/6to4: ::/16
                   LAN (lan)       -> igb1       -> v4: 192.168.1.1/24
                   OPENVPN (opt1)  -> ovpns2     -> v4: 192.168.10.1/24
                   OPT2 (opt2)     -> ovpns1     -> v4: 192.168.10.1/24
                  
                   0) Logout (SSH only)                  9) pfTop
                   1) Assign Interfaces                 10) Filter Logs
                   2) Set interface(s) IP address       11) Restart webConfigurator
                   3) Reset webConfigurator password    12) PHP shell + pfSense tools
                   4) Reset to factory defaults         13) Update from console
                   5) Reboot system                     14) Disable Secure Shell (sshd)
                   6) Halt system                       15) Restore recent configuration
                   7) Ping host                         16) Restart PHP-FPM
                   8) Shell
                  
                  Enter an option:
                  
                  
                  1 Reply Last reply Reply Quote 0
                  • M
                    meruem
                    last edited by

                    Update:

                    i wouldnt recomend this but because it sounds like you'll lose everything, but I did option #4, (Reset to factory defaults), and then confirmed yes. The terminal stoped stdout and appeared frozen and then all of the sudden my spinning webconfigurator in my browser loaded. now im up and running , I lost nothing, all my config is still there. O_o . I even rebooted and im still good

                    1 Reply Last reply Reply Quote 0
                    • Q
                      qaiserajaz
                      last edited by

                      @meruem:

                      Update:

                      i wouldnt recomend this but because it sounds like you'll lose everything, but I did option #4, (Reset to factory defaults), and then confirmed yes. The terminal stoped stdout and appeared frozen and then all of the sudden my spinning webconfigurator in my browser loaded. now im up and running , I lost nothing, all my config is still there. O_o . I even rebooted and im still good

                      I would give it a try and let you know whether it works fine for me or not. Well, I now have to install it on a spare machine and would do these experiments as I can't touch my Pfsense in our normal working hours. Glad to hear a response from you on this and thanks a million for your help :)

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