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

    failed to fetch the repo data. Unable to perform update from 2.7.2 to 2.8.0 after restoring crashed 2.8.0 pfSense.

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    12 Posts 5 Posters 347 Views 4 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
      GregBinSD
      last edited by

      Our whitebox pfSense 2.8.0 router failed after a power outage on July 14, 2025, this Monday. I switched cables over to my identical standby pfSense 2.8.0 router and we were back in business at the school.
      There was a voltage spike when power was restored, and I had to replace the SSD and reload the OS on the original pfSense router. I successfully restored pfSense 2.7.2 and all the packages, but I am unable to upgrade the original router to 2.8.0.
      The error message says "failed to fetch the repo data".

      I hope that someone can tell me what can cause this and how I can get past it and perform the upgrade so that I can make my original pfSense into a standby unit.

      Thank you.

      C W 3 Replies Last reply Reply Quote 0
      • C Offline
        comet424 @GregBinSD
        last edited by

        @GregBinSD
        its looking like servers for updating might be down as i having same issue i cant i installed 2.7.2 from an iso as i couldnt do updater

        and i get failed to update the repository or failed to fet the repo data. so currently i running 2.7.2 earlier it wouldnt import my 2.8.0 configuration but now it did so i also waiting for 2.8.0 update to work probably by tomorrow

        1 Reply Last reply Reply Quote 0
        • C Offline
          comet424 @GregBinSD
          last edited by

          @GregBinSD it should be working now i was able to upgrade 20 min ago so.. so the update servers must be working again

          1 Reply Last reply Reply Quote 0
          • W Offline
            Wolfgangthegreat @GregBinSD
            last edited by

            Still cannot access the upgrade files, at the system > update I get "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-* 2>&1 pfSense-repoc: no pfSense packages installed pfSense-repoc: failed to fetch the repo data"

            Update from the console gives:
            pfSense-repoc-static: si_get_packages: failed to run the pkg info command: /usr/local/sbin/pkg-static info -R --raw-format json-compact pfSense-pkg-* 2>&1
            pfSense-repoc-static: no pfSense packages installed
            pfSense-repoc-static: failed to fetch the repo data
            failed to read the repo data.
            failed to update the repository settings!!!
            failed to update the repository settings!!!

            C 1 Reply Last reply Reply Quote 0
            • C Offline
              comet424 @Wolfgangthegreat
              last edited by

              @Wolfgangthegreat
              ya i was getting those errors last night.. maybe servers down again?

              i did try last night from the console shell

              certctl rehash

              and then things didnt work and i waited till this morning and i was able to update from gui.

              W rcfaR 2 Replies Last reply Reply Quote 0
              • W Offline
                Wolfgangthegreat @comet424
                last edited by

                @comet424 OK, I was able now to fetch the upgrade files and upgraded successfully. FYI

                G 1 Reply Last reply Reply Quote 0
                • G Offline
                  GregBinSD @Wolfgangthegreat
                  last edited by

                  @Wolfgangthegreat
                  Thank you for the info. I won't be able to attempt the upgrade to 2.8.0 until tomorrow.
                  I'll let you know status then.

                  1 Reply Last reply Reply Quote 0
                  • G Offline
                    GregBinSD
                    last edited by

                    @Wolfgangthegreat
                    ...and to @comet424

                    I wasn't able to perform the 2.8.0 update this weekend, but when I got to the school this morning, it worked perfectly!

                    I appreciate the support from both of you, and from Netgate.

                    The backup/standby pfSense instance is back in place and ready in case I have a hardware failure, or a failure of the gray matter between my ears!

                    My best to all of you.

                    1 Reply Last reply Reply Quote 3
                    • rcfaR Offline
                      rcfa @comet424
                      last edited by

                      @comet424 said in failed to fetch the repo data. Unable to perform update from 2.7.2 to 2.8.0 after restoring crashed 2.8.0 pfSense.:

                      certctl rehash

                      I just get a whole slew of errors when I run that command

                      root: certctl rehash
certctl: Skipping untrusted certificate c47d9980 (/etc/ssl/untrusted/c47d9980.0)
certctl: Skipping untrusted certificate 0b7c536a (/etc/ssl/untrusted/0b7c536a.0)
certctl: Skipping untrusted certificate 5e98733a (/etc/ssl/untrusted/5e98733a.0)
certctl: Skipping untrusted certificate 03179a64 (/etc/ssl/untrusted/03179a64.0)
certctl: Skipping untrusted certificate 5d3033c5 (/etc/ssl/untrusted/5d3033c5.0)
certctl: Skipping untrusted certificate 4304c5e5 (/etc/ssl/untrusted/4304c5e5.0)
certctl: Skipping untrusted certificate 4a6481c9 (/etc/ssl/untrusted/4a6481c9.0)
certctl: Skipping untrusted certificate d853d49e (/etc/ssl/untrusted/d853d49e.0)
certctl: Skipping untrusted certificate 26312675 (/etc/ssl/untrusted/26312675.0)
certctl: Skipping untrusted certificate ee1365c0 (/etc/ssl/untrusted/ee1365c0.0)
certctl: Skipping untrusted certificate 116bf586 (/etc/ssl/untrusted/116bf586.0)
certctl: Skipping untrusted certificate 76cb8f92 (/etc/ssl/untrusted/76cb8f92.0)
certctl: Skipping untrusted certificate 2e5ac55d (/etc/ssl/untrusted/2e5ac55d.0)
certctl: Skipping untrusted certificate 0c4c9b6c (/etc/ssl/untrusted/0c4c9b6c.0)
certctl: Skipping untrusted certificate 1320b215 (/etc/ssl/untrusted/1320b215.0)
certctl: Skipping untrusted certificate dc45b0bd (/etc/ssl/untrusted/dc45b0bd.0)
certctl: Skipping untrusted certificate 080911ac (/etc/ssl/untrusted/080911ac.0)
certctl: Skipping untrusted certificate 18856ac4 (/etc/ssl/untrusted/18856ac4.0)
certctl: Skipping untrusted certificate 349f2832 (/etc/ssl/untrusted/349f2832.0)
certctl: Skipping untrusted certificate 7aaf71c0 (/etc/ssl/untrusted/7aaf71c0.0)
certctl: Skipping untrusted certificate a8dee976 (/etc/ssl/untrusted/a8dee976.0)
certctl: Skipping untrusted certificate 57bcb2da (/etc/ssl/untrusted/57bcb2da.0)
certctl: Skipping untrusted certificate 9c2e7d30 (/etc/ssl/untrusted/9c2e7d30.0)
certctl: Skipping untrusted certificate 5a7722fb (/etc/ssl/untrusted/5a7722fb.0)
certctl: Skipping untrusted certificate f90208f7 (/etc/ssl/untrusted/f90208f7.0)
certctl: Skipping untrusted certificate 08063a00 (/etc/ssl/untrusted/08063a00.0)
certctl: Skipping untrusted certificate 3e44d2f7 (/etc/ssl/untrusted/3e44d2f7.0)
certctl: Skipping untrusted certificate 5a4d6896 (/etc/ssl/untrusted/5a4d6896.0)
certctl: Skipping untrusted certificate 442adcac (/etc/ssl/untrusted/442adcac.0)
certctl: Skipping untrusted certificate b1b8a7f3 (/etc/ssl/untrusted/b1b8a7f3.0)
certctl: Skipping untrusted certificate 1636090b (/etc/ssl/untrusted/1636090b.0)
certctl: Skipping untrusted certificate 66445960 (/etc/ssl/untrusted/66445960.0)
certctl: Skipping untrusted certificate c01cdfa2 (/etc/ssl/untrusted/c01cdfa2.0)
certctl: Skipping untrusted certificate cb59f961 (/etc/ssl/untrusted/cb59f961.0)
certctl: Skipping untrusted certificate 5e98733a (/etc/ssl/untrusted/5e98733a.0)
certctl: Skipping untrusted certificate 57bcb2da (/etc/ssl/untrusted/57bcb2da.0)
certctl: Skipping untrusted certificate 18856ac4 (/etc/ssl/untrusted/18856ac4.0)
certctl: Skipping untrusted certificate 08063a00 (/etc/ssl/untrusted/08063a00.0)

                      Any ideas on how to fix that?

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

                        Those are not errors, it's expected to skip untrusted certs.

                        But you also shouldn't need to run that manually from 2.7.2. It was only an issue in 2.7.0.

                        What problem are you seeing?

                        rcfaR 1 Reply Last reply Reply Quote 0
                        • rcfaR Offline
                          rcfa @stephenw10
                          last edited by rcfa

                          @stephenw10 Pretty much the same things described here, but trying to go from 2.8.0 to the 2.8.1 beta.

                          Upgrading from the console:

                          Enter an option: 13

pfSense-repoc-static: failed to fetch the repo data
failed to read the repo data.
failed to update the repository settings!!!
failed to update the repository settings!!!
pfSense - Netgate Device ID: xyzblahblah

                          From the webUI:
                          1.PreUpgrade.png 2.PostUpgrade.png

                          Tried the fixes described in this thread and that one "Another instance of pfSense-upgrade is running. Try again later"

                          No change. Now while I can do w/o the beta, it seems something’s messed up, and that something will come to bite me once 2.8.1 is out of beta, so just shrugging the shoulders is just kicking the can down the road...

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

                            OK try at the command line: pfSense-repoc -ND

                            What error is shown?

                            Send me your NDI in chat and I can check what it should be seeing.

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