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

    Surprised, No Available Packages

    Scheduled Pinned Locked Moved General pfSense Questions
    29 Posts 6 Posters 3.2k 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.
    • G
      Gradius @NollipfSense
      last edited by

      Well, I'm on 23.05.01 and after a simple restore. I get "no package available" now.

      I'm using PPPoE, so the pkg update has been ABORTED (got that message).

      Tried many things and nothing seems to work:

      [23.05.1-RELEASE][admin@pfSense.home.arpa]/: pfSense-upgrade -c
      pfSense-repoc-static: invalid signature
      failed to read the repo data.
      failed to update the repository settings!!!
      failed to update the repository settings!!!

      [23.05.1-RELEASE][admin@pfSense.home.arpa]/: pkg -d update
      DBG(1)[85657]> pkg initialized
      Updating pfSense-core repository catalogue...
      DBG(1)[85657]> PkgRepo: verifying update for pfSense-core
      DBG(1)[85657]> PkgRepo: need forced update of pfSense-core
      DBG(1)[85657]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
      DBG(1)[85657]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_05_1_amd64-core/meta.conf
      DBG(1)[85657]> opening libfetch fetcher
      DBG(1)[85657]> Fetch > libfetch: connecting
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/meta.conf with opts "i"
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/meta.conf with opts "i"
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/meta.conf with opts "i"
      DBG(1)[85657]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_05_1_amd64-core/meta.txz
      DBG(1)[85657]> opening libfetch fetcher
      DBG(1)[85657]> Fetch > libfetch: connecting
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/meta.txz with opts "i"
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/meta.txz with opts "i"
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/meta.txz with opts "i"
      pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/meta.txz: Bad Request
      repository pfSense-core has no meta file, using default settings
      DBG(1)[85657]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_05_1_amd64-core/packagesite.pkg
      DBG(1)[85657]> opening libfetch fetcher
      DBG(1)[85657]> Fetch > libfetch: connecting
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/packagesite.pkg with opts "i"
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/packagesite.pkg with opts "i"
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/packagesite.pkg with opts "i"
      pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/packagesite.pkg: Bad Request
      DBG(1)[85657]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_05_1_amd64-core/packagesite.txz
      DBG(1)[85657]> opening libfetch fetcher
      DBG(1)[85657]> Fetch > libfetch: connecting
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/packagesite.txz with opts "i"
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/packagesite.txz with opts "i"
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/packagesite.txz with opts "i"
      pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/packagesite.txz: Bad Request
      Unable to update repository pfSense-core
      Updating pfSense repository catalogue...
      DBG(1)[85657]> PkgRepo: verifying update for pfSense
      DBG(1)[85657]> PkgRepo: need forced update of pfSense
      DBG(1)[85657]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
      DBG(1)[85657]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/meta.conf
      DBG(1)[85657]> opening libfetch fetcher
      DBG(1)[85657]> Fetch > libfetch: connecting
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/meta.conf with opts "i"
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/meta.conf with opts "i"
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/meta.conf with opts "i"
      DBG(1)[85657]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/meta.txz
      DBG(1)[85657]> opening libfetch fetcher
      DBG(1)[85657]> Fetch > libfetch: connecting
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/meta.txz with opts "i"
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/meta.txz with opts "i"
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/meta.txz with opts "i"
      pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/meta.txz: Bad Request
      repository pfSense has no meta file, using default settings
      DBG(1)[85657]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/packagesite.pkg
      DBG(1)[85657]> opening libfetch fetcher
      DBG(1)[85657]> Fetch > libfetch: connecting
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/packagesite.pkg with opts "i"
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/packagesite.pkg with opts "i"
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/packagesite.pkg with opts "i"
      pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/packagesite.pkg: Bad Request
      DBG(1)[85657]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/packagesite.txz
      DBG(1)[85657]> opening libfetch fetcher
      DBG(1)[85657]> Fetch > libfetch: connecting
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/packagesite.txz with opts "i"
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/packagesite.txz with opts "i"
      DBG(1)[85657]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/packagesite.txz with opts "i"
      pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/packagesite.txz: Bad Request
      Unable to update repository pfSense
      Error updating repositories!

      Yes, I did the System > Update > Update Settings save thing. Same problems.

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

        The Bad Request error indicates it's using an invalid client cert.

        The invalid signature error from pfSense-repoc indicates it's unable to update it.

        Send me your NDI in chat and I'll check it.

        Steve

        1 Reply Last reply Reply Quote 0
        • NollipfSenseN
          NollipfSense
          last edited by

          Well after some hiccups with not getting anything on the monitor, I finally have a cleaner installed version...available packages now normal.

          Screenshot 2023-08-30 at 8.31.13 PM.png

          pfSense+ 23.09 Lenovo Thinkcentre M93P SFF Quadcore i7 dual Raid-ZFS 128GB-SSD 32GB-RAM PCI-Intel i350-t4 NIC, -Intel QAT 8950.
          pfSense+ 23.09 VM-Proxmox, Dell Precision Xeon-W2155 Nvme 500GB-ZFS 128GB-RAM PCIe-Intel i350-t4, Intel QAT-8950, P-cloud.

          GertjanG 1 Reply Last reply Reply Quote 1
          • GertjanG
            Gertjan @NollipfSense
            last edited by Gertjan

            @NollipfSense

            I've done the same test on my side.
            I didn't have any issues, but saw something strange while posting here :

            7eb70e5e-42f8-483a-af82-1f8227a226b0-image.png

            and that's new : I'm reaching the forum over IPv4 .... normally, it's IPv6 for years now.
            I've checked using several tools to check my IPv6 connection, like this one https://test-ipv6.com/ and Googlev6. All well.

            This :

            [23.05.1-RELEASE][root@pfSense.bhf.net]/root: pkg-static -4 -d update

            finished in a fraction of a second.

            [23.05.1-RELEASE][root@pfSense.bhf.net]/root: pkg-static -6 -d update

            takes minutes ..... (I'll wait to see if it times out, or is just very slow / bad )

            pfSense (GUI etc) will prefer and use IPv6 if both are declared present ...
            Probably the IPv6 between the old world and the newer one.
            Can some one from the US, or Texas, confirm ?

            [23.05.1-RELEASE][root@pfSense.bhf.net]/root: dig pfsense-plus-pkg00.atx.netgate.com A +short
208.123.73.207
[23.05.1-RELEASE][root@pfSense.bhf.net]/root: dig pfsense-plus-pkg00.atx.netgate.com AAAA +short
2610:160:11:18::207

            edit :
            eventually, while using the "-6" option :

            ...
Unable to update repository pfSense
Error updating repositories!

            again, IPv4 worked well.

            Btw : where is my "sometimes, it's not DNS" t-shirt ?

            No "help me" PM's please. Use the forum, the community will thank you.
            Edit : and where are the logs ??

            stephenw10S 1 Reply Last reply Reply Quote 0
            • V
              Vollans
              last edited by

              Yeah, same here. IPv4 works fine, IPv6 is down. This is with Aussie Broadband in Australia.

              GertjanG 1 Reply Last reply Reply Quote 0
              • GertjanG
                Gertjan @Vollans
                last edited by

                @Vollans said in Surprised, No Available Packages:

                This is with Aussie Broadband in Australia

                Definitely the new world for me, but we share the same "under water" link to the destination.
                Thanks for the feed back.

                No "help me" PM's please. Use the forum, the community will thank you.
                Edit : and where are the logs ??

                V 1 Reply Last reply Reply Quote 0
                • V
                  Vollans @Gertjan
                  last edited by Vollans

                  @Gertjan It seems to get stuck once it gets to CoreNap’s network.

                  
Traceroute6 to pfsense-plus-pkg00.atx.netgate.com (2610:160:11:18::207) from 2403:580d:7fff:6824:<redacted>, 64 hops max, 28 byte packets
 1  *
    fe80::2a2:ff:feb2:c2%igc3  9.781 ms *
 2  * * *
 3  ae-36.a00.sydnau05.au.bb.gin.ntt.net  33.349 ms  30.772 ms  21.186 ms
 4  lag-6.ear1.Tokyo4.Level3.net  25.018 ms  40.442 ms  26.179 ms
 5  * * *
 6  NETWORK-APP.edge1.Washington1.Level3.net  237.627 ms  237.859 ms  237.900 ms
 7  2610:160::ffff:4014:e5a6  223.901 ms  215.223 ms  219.037 ms
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
                  1 Reply Last reply Reply Quote 0
                  • GertjanG Gertjan referenced this topic on
                  • GertjanG
                    Gertjan
                    last edited by

                    Things don't get any better :

                    97a50986-e48a-4de6-a4ea-19f931658a4a-image.png

                    No "help me" PM's please. Use the forum, the community will thank you.
                    Edit : and where are the logs ??

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

                      @Gertjan said in Surprised, No Available Packages:

                      Btw : where is my "sometimes, it's not DNS" t-shirt ?

                      Ha. Lies! It's always DNS. 😉

                      Though I'm also unable to hit the pkg server over v6 from the UK. Digging....

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

                        @stephenw10 Appears someone has dried out the cable, as I can get updates this morning.

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

                          Yup, local v6 routing issue has been resolved. 👍

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