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

    Ver 21.02.2 fails to install

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 2 Posters 492 Views 2 Watching
    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.
    • G Offline
      grounddave
      last edited by

      Currently running 2.4.5-RELEASE on a Netgate SG-5100. System detects (albeit very slowly) an available update (21.02.2). Confirming the update install causes the router UI to first go blank, and then disappear (looks like a 303 error) when using Safari 14.1.

      Eventually the UI becomes responsive again but nothing has installed. The router is remote so I've opened up the admin UI to the world, seeking to close that off asap.

      Using Chrome, the router does get get to: "Please wait while the update system initializes", but never past that.

      Any ideas?

      1 Reply Last reply Reply Quote 0
      • stephenw10S Offline
        stephenw10 Netgate Administrator
        last edited by

        Enable SSH and connect to it that way.

        At the cli run pkg-static -d update make sure completes without errors.

        If it does exit back to the menu and run option 13 to upgrade from there. You'll get far more feedback about what's happening.

        Steve

        G 1 Reply Last reply Reply Quote 0
        • G Offline
          grounddave @stephenw10
          last edited by

          @stephenw10

          Well hell. I enabled ssh (and that's it) and now the web UI isn't responding nor is ssh. Router is still pinging. Any way out of this pickle without being onsite?

          1 Reply Last reply Reply Quote 0
          • stephenw10S Offline
            stephenw10 Netgate Administrator
            last edited by

            You just enabled SSH? You hadn't yet added a firewall rule or port forward to access it?

            Hard to imagine what that could have caused if so.

            Is it inaccessible both internally and externally? Can you get the serial console connected to anything locally?

            It's possible the process required to generate the SSH keys is simply using all the available CPU cycles if something else was already stuck using a lot. If that is the case it may finish doing that after some time and become available again.

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