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

    Packages won’t update

    Scheduled Pinned Locked Moved pfSense Packages
    9 Posts 2 Posters 1.3k 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.
    • M
      markn62
      last edited by

      Until recently packages no longer update. On 2.4.5-RELEASE-p1. After “Confirm” is chose it just sits on “ Please wait while the update system initializes” and wont finish. Suggestions?

      1 Reply Last reply Reply Quote 0
      • bmeeksB
        bmeeks
        last edited by bmeeks

        You normally cannot update packages any longer when you are not running the current version of pfSense. So since you are running 2.4.5, and the latest pfSense version is 2.5.2, you won't be able to install or update packages in the conventional way. And if you were to find a way to force it, you would probably totally break your firewall. This is because the packages repository is always recompiled with each update of pfSense. And new package versions generally can't run on older pfSense versions due to changes in shared libraries.

        There is an option on the SYSTEM > UPDATE page to switch your repository branch to the "Previous stable version (2.4.5 DEPRECATED)". If you do that, you can install new packages on the firewall, but there are no actual "updated" packages in that tree for the reason I mentioned above. They will all be frozen at whatever version they had when pfSense released the 2.5.x stable branch.

        If you want to truly update any installed packages to newer versions, then you must first upgrade your firewall to the latest pfSense version.

        If you have already attempted to install a new package, or update an existing package, with the repo set incorrectly, you may have broken the pkg subsystem on the firewall. Search the pfSense documentation here for help with fixing that. Or maybe export your configuration, then install the latest pfSense version and then import your configuration.

        M 2 Replies Last reply Reply Quote 0
        • M
          markn62 @bmeeks
          last edited by

          @bmeeks Thanks for your response. Upgraded to 2.5.2 and all packages are now updated as well. However, the NordVpn client is no longer up. Perhaps I need to start a new post on a different group for this.

          1 Reply Last reply Reply Quote 0
          • M
            markn62 @bmeeks
            last edited by

            @bmeeks Didn't expect it to break. Not sure how to fix other than to start from scratch.
            OpenVpn log;
            Aug 21 10:43:44 openvpn 61452 VERIFY KU OK
            Aug 21 10:43:44 openvpn 61452 VERIFY OK: depth=1, C=PA, O=NordVPN, CN=NordVPN CA6
            Aug 21 10:43:44 openvpn 61452 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA
            Aug 21 10:43:44 openvpn 61452 VERIFY WARNING: depth=2, unable to get certificate CRL: C=PA, O=NordVPN, CN=NordVPN Root CA
            Aug 21 10:43:44 openvpn 61452 VERIFY WARNING: depth=1, unable to get certificate CRL: C=PA, O=NordVPN, CN=NordVPN CA6
            Aug 21 10:43:44 openvpn 61452 VERIFY WARNING: depth=0, unable to get certificate CRL: CN=us8961.nordvpn.com

            1 Reply Last reply Reply Quote 0
            • bmeeksB
              bmeeks
              last edited by

              Lot's of things changed with OpenVPN. It went to a new binary version. There are many posts in the OpenVPN sub-forum here. I recommend reading and searching posts in there, and then perhaps creating your own new one if nothing existing solves your problem.

              I'm not a VPN provider user. I don't use OpenVPN for anything other than remote access back into my LAN, so I can't be of any help with provider issues.

              M 1 Reply Last reply Reply Quote 0
              • M
                markn62 @bmeeks
                last edited by

                @bmeeks Thanks, appreciate your responses. Up until recently that's all I used as well, a remote in. It still works fine. I'll go through and recreate, it's a good hour when I implemented a month ago, uggg!

                bmeeksB 1 Reply Last reply Reply Quote 0
                • bmeeksB
                  bmeeks @markn62
                  last edited by

                  @markn62 said in Packages won’t update:

                  @bmeeks Thanks, appreciate your responses. Up until recently that's all I used as well, a remote in. It still works fine. I'll go through and recreate, it's a good hour when I implemented a month ago, uggg!

                  Yeah, I had no issues with my remote access migrating. But lots of folks using the various VPN providers for privacy reasons posted about having problems. There were a number of related threads in the OpenVPN sub-forum here on the Netgate forum.

                  M 1 Reply Last reply Reply Quote 0
                  • M
                    markn62 @bmeeks
                    last edited by

                    @bmeeks Thanks again. Was a quick checkbox fix from this post. Working now. 😁

                    bmeeksB 1 Reply Last reply Reply Quote 0
                    • bmeeksB
                      bmeeks @markn62
                      last edited by

                      @markn62 said in Packages won’t update:

                      @bmeeks Thanks again. Was a quick checkbox fix from this post. Working now. 😁

                      👍

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