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

    XG-7100 on 22.01 (DEVEL) - Unable to check for updates since November 5 - repository pfSense has no meta file, using default settings

    Official Netgate® Hardware
    2
    4
    937
    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.
    • V
      victorhooi
      last edited by

      I have a Netgate XG-7100, running the Netgate pfSense Plus 22.01 DEVEL branch.

      It's currently on the November 05, 2021 build:

      22.01-DEVELOPMENT (amd64)
      built on Fri Nov 05 05:21:41 UTC 2021
      FreeBSD 12.3-PRERELEASE
      

      However, when I go to Update, it says unable to check for update.

      If I try to do an update from the CLI, I get:

      Enter an option: 13
      
      >>> Updating repositories metadata...
      Updating pfSense-core repository catalogue...
      pkg-static: packagesite URL error for pkg+https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-core/meta.conf -- pkg+:// implies SRV mirror type
      pkg-static: packagesite URL error for pkg+https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-core/meta.txz -- pkg+:// implies SRV mirror type
      repository pfSense-core has no meta file, using default settings
      pkg-static: packagesite URL error for pkg+https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-core/packagesite.pkg -- pkg+:// implies SRV mirror type
      pkg-static: packagesite URL error for pkg+https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-core/packagesite.txz -- pkg+:// implies SRV mirror type
      Unable to update repository pfSense-core
      Updating pfSense repository catalogue...
      pkg-static: packagesite URL error for pkg+https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-pfSense_plus_devel/meta.conf -- pkg+:// implies SRV mirror type
      pkg-static: packagesite URL error for pkg+https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-pfSense_plus_devel/meta.txz -- pkg+:// implies SRV mirror type
      repository pfSense has no meta file, using default settings
      pkg-static: packagesite URL error for pkg+https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-pfSense_plus_devel/packagesite.pkg -- pkg+:// implies SRV mirror type
      pkg-static: packagesite URL error for pkg+https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-pfSense_plus_devel/packagesite.txz -- pkg+:// implies SRV mirror type
      Unable to update repository pfSense
      Error updating repositories!
      ERROR: Unable to compare version of pfSense-repo
      Netgate 7100 - Serial: 1436180422 - Netgate Device ID: 12b1c2a76aec5bee45e5
      

      Does anybody know what's going on?

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

        Yes, it looks like there was an issue with last nights pkg updates.

        Either run this command:

        sed -i '' -e 's/%%MIRROR_TYPE%%/srv/; s/%%SIGNATURE_TYPE%%/fingerprints/' /usr/local/share/pfSense/pkg/repos/pfSense-repo-devel.conf
        

        Or toggle the repo branch to previous version and then back to development snapshots which will re-fetch the, now correct, file.

        Steve

        V 1 Reply Last reply Reply Quote 1
        • V
          victorhooi @stephenw10
          last edited by

          @stephenw10 I can confirm that the sed command worked - Thanks Stephen!

          (Toggling the update repo between different ones, and back did not work).

          Will we need to do the sed command on every single XG-7100, or will it fix itself over time?

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

            Toggling the repo should work. It may not have refreshed the pkg if you did it too quickly.

            Any device that is running a development snapshot and pulled the bad repo details at that time will need to be corrected manually.

            Steve

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