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

Blank Web Configurator after upgrade from 22.9 to 23.05.01

Scheduled Pinned Locked Moved General pfSense Questions
13 Posts 4 Posters 1.0k 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.
  • S
    sinbox_pfs
    last edited by Aug 13, 2023, 6:01 AM

    Hi,

    After deciding to upgrade from 22.9 to 23.05.01, web configurator is no longer loading. It's showing a blank page. Firewall seems to be working fine and I did not notice any errors during upgrade. I don't seem to be able to restore back to 22.9 using the Restore Configuration feature via shell. What logs do I need to look into or provide here to help me understand what's going on?

    S 1 Reply Last reply Aug 13, 2023, 9:00 AM Reply Quote 0
    • S
      sinbox_pfs @sinbox_pfs
      last edited by Aug 13, 2023, 9:00 AM

      Should clarify that I was upgrading from pfSense CE (22.9?) to 23.05.01.

      Tried following options:

      1. PS: Resetting to factory defaults hasn't helped.
      2. Trying to force upgrade packages using
        pkg-static clean -ay ; pkg-static install -fy pkg pfSense-repo pfSense-upgrade
        but get the "Certificate verification failed" error
      3. I have had pfSense CE run without issues on the Sophos SG125w for a couple of years now. I took a backup of the config.xml and trying to reinstall pfSense via USB, but for some reason the Sophos refuses to boot into the USB drive even though it is recognised in the BIOS
      S 1 Reply Last reply Aug 13, 2023, 5:32 PM Reply Quote 0
      • S
        stephenw10 Netgate Administrator
        last edited by Aug 13, 2023, 2:24 PM

        If it was CE it would have been 2.6 or maybe 2.5.2.
        22.09 would be Plus but that version was never publicly released.

        Check the System and nginx logs

        Check that nginx is running at all:

        ps -aux | grep nginx
        

        Check that it's listening on port 443 (or a custom port of you've set that):

        sockstat | grep 443
        
        S 2 Replies Last reply Aug 22, 2023, 9:22 AM Reply Quote 0
        • S
          SteveITS Galactic Empire @sinbox_pfs
          last edited by Aug 13, 2023, 5:32 PM

          @sinbox_pfs A blank page can be a PHP parsing error, where it canโ€™t even load the page. Probably not a good sign. Could indicate the wrong PHP version is being used, or similar.

          Restoring a configuration (file) does not change the OS or pfSense code.

          Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
          When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
          Upvote ๐Ÿ‘ helpful posts!

          1 Reply Last reply Reply Quote 0
          • S
            sinbox_pfs @stephenw10
            last edited by Aug 22, 2023, 9:22 AM

            @stephenw10 nginx seems to be running:

            [23.05.1-RELEASE][admin@pfSense.home.arpa]/root: ps -aux | grep nginx
            root 391 0.0 0.9 114248 36668 - I 13Aug23 0:00.49 php-fpm: pool nginx (php-fpm)
            root 392 0.0 0.9 114248 37072 - I 13Aug23 0:01.27 php-fpm: pool nginx (php-fpm)
            root 73028 0.0 0.2 29060 7696 - Is 13Aug23 0:00.00 nginx: master process /usr/loca
            root 73129 0.0 0.2 29060 8228 - I 13Aug23 0:00.00 nginx: worker process (nginx)
            root 73307 0.0 0.2 31620 9180 - S 13Aug23 0:00.14 nginx: worker process (nginx)
            root 51138 0.0 0.1 12768 2376 0 S+ 19:19 0:00.00 grep nginx

            [23.05.1-RELEASE][admin@pfSense.home.arpa]/root: sockstat | grep 443
            root nginx 73307 5 tcp4 *:443 :
            root nginx 73307 6 tcp6 *:443 :
            root nginx 73129 5 tcp4 *:443 :
            root nginx 73129 6 tcp6 *:443 :
            root nginx 73028 5 tcp4 *:443 :
            root nginx 73028 6 tcp6 *:443 :

            @SteveITS I came across a few other posts where users faced similar issue after upgrading from 2.6 to pfSense CE. Is there a way to reinstall the PHP packages without having to perform a fresh install?

            1 Reply Last reply Reply Quote 0
            • S
              sinbox_pfs @stephenw10
              last edited by Aug 22, 2023, 9:30 AM

              @stephenw10 you are correct...it should have been either 2.6 or 2.5.2

              1 Reply Last reply Reply Quote 0
              • S
                stephenw10 Netgate Administrator
                last edited by Aug 22, 2023, 11:45 AM

                Does pkg-static update succeed? If it fails try running pfSense-repoc first.

                If that succeeds you can try force reinstalling the php components:
                https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#forced-pkg-reinstall

                However at that point it might be easier to reinstall clean.

                Steve

                S 1 Reply Last reply Aug 22, 2023, 10:15 PM Reply Quote 0
                • S
                  sinbox_pfs @stephenw10
                  last edited by Aug 22, 2023, 10:15 PM

                  @stephenw10 said in Blank Web Configurator after upgrade from 22.9 to 23.05.01:

                  Does pkg-static update succeed? If it fails try running pfSense-repoc first.

                  pkg-static fails with the Certificate Verification failed error (I have tried power cycling the system a few times; along with checking the date/time is in sync with an NTP server)

                  pfSense-repoc does not seem right to me:

                  pkg-static: No package(s) matching pfSense-pkg-*
                  pfSense-repoc: si_get_packages: failed to run the pkg info command: /usr/local/sbin/pkg-static info -R --raw-format json-compact pfSense-pkg-*
                  pfSense-repoc: no pfSense packages installed

                  I'm running this on a Sophos SG125w. Looks like a clean reinstall is the best option, but for some reason I was not able boot off an USB stick. I'll keep trying...

                  R S 2 Replies Last reply Aug 22, 2023, 10:19 PM Reply Quote 0
                  • R
                    rcoleman-netgate Netgate @sinbox_pfs
                    last edited by Aug 22, 2023, 10:19 PM

                    @sinbox_pfs said in Blank Web Configurator after upgrade from 22.9 to 23.05.01:

                    I'm running this on a Sophos SG125w. Looks like a clean reinstall is the best option, but for some reason I was not able boot off an USB stick. I'll keep trying...

                    Two questions:

                    1. what are the last 8 chars of your NDI?

                    2. What was your shopify order # for your Plus license/token?

                    Ryan
                    Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
                    Requesting firmware for your Netgate device? https://go.netgate.com
                    Switching: Mikrotik, Netgear, Extreme
                    Wireless: Aruba, Ubiquiti

                    S 1 Reply Last reply Aug 23, 2023, 3:16 AM Reply Quote 0
                    • S
                      stephenw10 Netgate Administrator @sinbox_pfs
                      last edited by Aug 22, 2023, 11:17 PM

                      @sinbox_pfs said in Blank Web Configurator after upgrade from 22.9 to 23.05.01:

                      pfSense-repoc does not seem right to me:

                      pkg-static: No package(s) matching pfSense-pkg-*
                      pfSense-repoc: si_get_packages: failed to run the pkg info command: /usr/local/sbin/pkg-static info -R --raw-format json-compact pfSense-pkg-*
                      pfSense-repoc: no pfSense packages installed

                      Yeah that looks like an old repoc pkg that had a bug.
                      What does pkg-static info -x pfsense show the package version is?

                      S 1 Reply Last reply Aug 23, 2023, 3:11 AM Reply Quote 0
                      • S
                        sinbox_pfs @stephenw10
                        last edited by Aug 23, 2023, 3:11 AM

                        @stephenw10

                        pfSense-23.05.1
                        pfSense-Status_Monitoring-php82-1.8_3
                        pfSense-base-23.05.1
                        pfSense-boot-23.05.1
                        pfSense-default-config-23.05.1
                        pfSense-kernel-pfSense-23.05.1
                        pfSense-rc-23.05.1
                        pfSense-repo-23.05.1
                        pfSense-repoc-20230605
                        pfSense-upgrade-1.0_68
                        php82-pfSense-module-0.95

                        1 Reply Last reply Reply Quote 0
                        • S
                          sinbox_pfs @rcoleman-netgate
                          last edited by Aug 23, 2023, 3:16 AM

                          @rcoleman-netgate

                          NDI is *********99bb3488

                          The Order # for the license was SO23-83777

                          1 Reply Last reply Reply Quote 0
                          • S
                            stephenw10 Netgate Administrator
                            last edited by Aug 23, 2023, 11:20 AM

                            Hmm, that all look good. I can see that NDI chekcing in and it's being validated.

                            After running that pkg-static update still fails?

                            Try pkg-static -d update to see more error output.

                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post
                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                              This community forum collects and processes your personal information.
                              consent.not_received