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

    Can't upgrade from 2.7.0 to 2.7.2.

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    2 Posts 1 Posters 3.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.
    • S
      Stewart
      last edited by

      I have the Branch set to
      Current Stable Release (2.7.2)
      But it shows the Current Base System and Latest Base System as
      (2.7.0)
      and Status shows
      Up to date.

      Dropping to the Command Line gives me this:

      [2.7.0-RELEASE][root@pfSense]/root: pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade
      pkg-static: Repository pfSense-core missing. 'pkg update' required
      pkg-static: No package database installed.  Nothing to do!
      Updating pfSense-core repository catalogue...
      pkg-static: An error occured while fetching package
      pkg-static: An error occured while fetching package
      repository pfSense-core has no meta file, using default settings
      pkg-static: An error occured while fetching package
      pkg-static: An error occured while fetching package
      Unable to update repository pfSense-core
      Updating pfSense repository catalogue...
      pkg-static: An error occured while fetching package
      pkg-static: An error occured while fetching package
      repository pfSense has no meta file, using default settings
      pkg-static: An error occured while fetching package
      pkg-static: An error occured while fetching package
      Unable to update repository pfSense
      Error updating repositories!
      
      [2.7.0-RELEASE][root@pfSense]/root: pkg update
      ld-elf.so.1: Shared object "libssl.so.30" not found, required by "pkg"
      
      [2.7.0-RELEASE][root@pfSense]/root: host -t srv _https._tcp.packages.netgate.com
      _https._tcp.packages.netgate.com has SRV record 10 10 443 pkg00-atx.netgate.com.
      _https._tcp.packages.netgate.com has SRV record 10 10 443 pkg01-atx.netgate.com.
      
      [2.7.0-RELEASE][root@pfSense]/root: host pkg01-atx.netgate.com
      pkg01-atx.netgate.com has address 208.123.73.209
      pkg01-atx.netgate.com has IPv6 address 2610:160:11:18::209
      
      [2.7.0-RELEASE][pfSense]/root: host pkg00-atx.netgate.com
      pkg00-atx.netgate.com has address 208.123.73.207
      pkg00-atx.netgate.com has IPv6 address 2610:160:11:18::207
      
      [2.7.0-RELEASE][root@pfSense]/root: pkg-static update -f
      Updating pfSense-core repository catalogue...
      pkg-static: An error occured while fetching package
      pkg-static: An error occured while fetching package
      repository pfSense-core has no meta file, using default settings
      pkg-static: An error occured while fetching package
      pkg-static: An error occured while fetching package
      Unable to update repository pfSense-core
      Updating pfSense repository catalogue...
      pkg-static: An error occured while fetching package
      pkg-static: An error occured while fetching package
      repository pfSense has no meta file, using default settings
      pkg-static: An error occured while fetching package
      pkg-static: An error occured while fetching package
      Unable to update repository pfSense
      Error updating repositories!
      
      

      Not sure the best course of action from this point. Any help would be greatly appreciated.

      S 1 Reply Last reply Reply Quote 0
      • S
        Stewart @Stewart
        last edited by

        @Stewart @SteveITS

        This was solved here.

        Due to changes in pkg, the new version of pkg may not be able to properly locate and use the CA trust store when running on the previous version before upgrading.
        
        If the firewall is unable to load packages or check for updates after selecting the CE 2.7.1 upgrade branch, run certctl rehash from the console, a root shell prompt, or via Diagnostics > Command Prompt. This will allow pkg to utilize the system certificates until the next reboot.
        

        This is true in 2.7.0 as well. Running the certctl rehash brought it up to be able to upgrade.

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