No packages in available packages list

cefinformatique

Here are my update settings :

Capture d’écran_2025-01-13_11-31-28.png

and

Capture d’écran_2025-01-13_13-35-39.png

so the smartest thing to do right now, is not trying to update pfSense.
It's something at 'their' side.

Got it. I'll wait a few days and hope the issue will be resolved.

DominikHoffmann

@cefinformatique: I have the exact same issue. Awaiting a solution.

Gertjan

@DominikHoffmann said in No packages in available packages list:

Awaiting a solution.

It's not a solution.
Just wait until Netgate stopped messing around with their package servers and things will 'work' again.
Probably some maintenance going on right now.

edit :

Enter an option: 13

Messages:
Your Netgate device has pfSense+ as part of your device purchase.
>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: . done
Processing entries: . done
pfSense-core repository update completed. 7 packages processed.
Updating pfSense repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: .......... done
Processing entries: .......... done
pfSense repository update completed. 735 packages processed.
All repositories are up to date.
Your packages are up to date
Netgate 4100 - Serial: 2014221462 - Netgate Device ID: e57dfdc41deadbeefa2527a

and

So, it works again.

stephenw10

It looks like there were some backend issues earlier but they should be resolved now.

Try refereshing the packaage/update list or running at the CLI: pfSense-repoc -N

cefinformatique

I confirm that the issue is resolved.

HansWerner3dit

I have the exact same problem, but it still does not work :(

Even working through the update troubleshoot page, does not fix the issue.

[24.03-RELEASE][admin@pfSense.3dit.local]/root: pkg-static update -f
Updating pfSense-core repository catalogue...
Fetching meta.conf: 100%    178 B   0.2kB/s    00:01    
Fetching packagesite.pkg: 100%    2 KiB   1.6kB/s    00:01    
pkg-static: No trusted public keys found
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
Fetching meta.conf: 100%    178 B   0.2kB/s    00:01    
Fetching packagesite.pkg: 100%  192 KiB 196.3kB/s    00:01    
pkg-static: No trusted public keys found
Unable to update repository pfSense
Error updating repositories!

The so called "Force pkg Metadata Update" or "Rewrite Repository Information" do not help either :/

Is a full reinstall really the last resort here?

Any help is much appreciated.

Netgate 5100
Serial: NG201812003658
Netgate Device ID: 2a5dafd7126cfa1f6d3c

stephenw10

Try running pkg -d update and see what additional debug info you get.

HansWerner3dit

@stephenw10 thanks for your fast response!

i do get nearly the same like messages like the initial op

switching to 24.11 results in the same, but other package path...

[24.03-RELEASE][admin@pfSense.3dit.local]/root: pkg -d update
DBG(1)[7866]> pkg initialized
Updating pfSense-core repository catalogue...
DBG(1)[7866]> PkgRepo: verifying update for pfSense-core
DBG(1)[7866]> PkgRepo: need forced update of pfSense-core
DBG(1)[7866]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
DBG(1)[7866]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/meta.conf
DBG(1)[7866]> curl_open
DBG(1)[7866]> Fetch: fetcher used: pkg+https
DBG(1)[7866]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/meta.conf

DBG(1)[7866]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pfsense-plus-pkg01.atx.netgate.com in the .netrc file; using defaults
*   Trying [2610:160:11:18::209]:443...
* Connected to pfsense-plus-pkg01.atx.netgate.com (2610:160:11:18::209) port 443
* ALPN: curl offers http/1.1
*  CAfile: /etc/ssl/netgate-ca.pem
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=pfSense Plus; CN=pfsense-plus-pkg01.atx.netgate.com
*  start date: Mar 15 20:23:37 2022 GMT
*  expire date: Feb 19 20:23:37 2122 GMT
*  common name: pfsense-plus-pkg01.atx.netgate.com (matched)
*  issuer: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=Netgate CA; CN=Netgate CA
*  SSL certificate verify ok.
* using HTTP/1.1
> GET /pfSense_plus-v24_03_amd64-core/meta.conf HTTP/1.1
Host: pfsense-plus-pkg01.atx.netgate.com
User-Agent: pkg/1.20.9
Accept: */*
If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT

< HTTP/1.1 200 OK
Fetching meta.conf:   0%< Server: nginx
< Date: Mon, 27 Jan 2025 15:32:05 GMT
< Content-Type: application/octet-stream
< Content-Length: 178
< Last-Modified: Fri, 19 Apr 2024 01:25:58 GMT
< Connection: keep-alive
< ETag: "6621c826-b2"
< Accept-Ranges: bytes
< 
Fetching meta.conf: 100%    178 B   0.2kB/s    00:01    
* Connection #0 to host pfsense-plus-pkg01.atx.netgate.com left intact
DBG(1)[7866]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/packagesite.pkg
DBG(1)[7866]> curl_open
DBG(1)[7866]> Fetch: fetcher used: pkg+https
DBG(1)[7866]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/packagesite.pkg

DBG(1)[7866]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pfsense-plus-pkg01.atx.netgate.com in the .netrc file; using defaults
* Found bundle for host: 0x18a2050248d0 [serially]
* Re-using existing connection with host pfsense-plus-pkg01.atx.netgate.com
> GET /pfSense_plus-v24_03_amd64-core/packagesite.pkg HTTP/1.1
Host: pfsense-plus-pkg01.atx.netgate.com
User-Agent: pkg/1.20.9
Accept: */*
If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT

< HTTP/1.1 200 OK
Fetching packagesite.pkg:   0%< Server: nginx
< Date: Mon, 27 Jan 2025 15:32:05 GMT
< Content-Type: application/octet-stream
< Content-Length: 1580
< Last-Modified: Fri, 19 Apr 2024 01:25:58 GMT
< Connection: keep-alive
< ETag: "6621c826-62c"
< Accept-Ranges: bytes
< 
Fetching packagesite.pkg: 100%    2 KiB   1.6kB/s    00:01    
* Connection #0 to host pfsense-plus-pkg01.atx.netgate.com left intact
DBG(1)[7866]> PkgRepo: extracting packagesite.yaml of repo pfSense-core
DBG(1)[11169]> PkgRepo: extracting signature of repo in a sandbox
pkg: No trusted public keys found
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
DBG(1)[7866]> PkgRepo: verifying update for pfSense
DBG(1)[7866]> PkgRepo: need forced update of pfSense
DBG(1)[7866]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
DBG(1)[7866]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/meta.conf
DBG(1)[7866]> curl_open
DBG(1)[7866]> Fetch: fetcher used: pkg+https
DBG(1)[7866]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/meta.conf

DBG(1)[7866]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pfsense-plus-pkg00.atx.netgate.com in the .netrc file; using defaults
*   Trying [2610:160:11:18::207]:443...
* Connected to pfsense-plus-pkg00.atx.netgate.com (2610:160:11:18::207) port 443
* ALPN: curl offers http/1.1
*  CAfile: /etc/ssl/netgate-ca.pem
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=pfSense Plus; CN=pfsense-plus-pkg00.atx.netgate.com
*  start date: Mar 15 20:23:11 2022 GMT
*  expire date: Feb 19 20:23:11 2122 GMT
*  common name: pfsense-plus-pkg00.atx.netgate.com (matched)
*  issuer: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=Netgate CA; CN=Netgate CA
*  SSL certificate verify ok.
* using HTTP/1.1
> GET /pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/meta.conf HTTP/1.1
Host: pfsense-plus-pkg00.atx.netgate.com
User-Agent: pkg/1.20.9
Accept: */*
If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT

< HTTP/1.1 200 OK
Fetching meta.conf:   0%< Server: nginx
< Date: Mon, 27 Jan 2025 15:32:06 GMT
< Content-Type: application/octet-stream
< Content-Length: 178
< Last-Modified: Thu, 23 Jan 2025 20:49:15 GMT
< Connection: keep-alive
< ETag: "6792ab4b-b2"
< Accept-Ranges: bytes
< 
Fetching meta.conf: 100%    178 B   0.2kB/s    00:01    
* Connection #0 to host pfsense-plus-pkg00.atx.netgate.com left intact
DBG(1)[7866]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/packagesite.pkg
DBG(1)[7866]> curl_open
DBG(1)[7866]> Fetch: fetcher used: pkg+https
DBG(1)[7866]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/packagesite.pkg

DBG(1)[7866]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pfsense-plus-pkg00.atx.netgate.com in the .netrc file; using defaults
* Found bundle for host: 0x18a205024900 [serially]
* Re-using existing connection with host pfsense-plus-pkg00.atx.netgate.com
> GET /pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/packagesite.pkg HTTP/1.1
Host: pfsense-plus-pkg00.atx.netgate.com
User-Agent: pkg/1.20.9
Accept: */*
If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT

< HTTP/1.1 200 OK
Fetching packagesite.pkg:   0%< Server: nginx
< Date: Mon, 27 Jan 2025 15:32:06 GMT
< Content-Type: application/octet-stream
< Content-Length: 196336
< Last-Modified: Thu, 23 Jan 2025 20:49:15 GMT
< Connection: keep-alive
< ETag: "6792ab4b-2fef0"
< Accept-Ranges: bytes
< 
Fetching packagesite.pkg: 100%  192 KiB 196.3kB/s    00:01    
* Connection #0 to host pfsense-plus-pkg00.atx.netgate.com left intact
DBG(1)[7866]> PkgRepo: extracting packagesite.yaml of repo pfSense
DBG(1)[11768]> PkgRepo: extracting signature of repo in a sandbox
pkg: No trusted public keys found
Unable to update repository pfSense
Error updating repositories!

HansWerner3dit

@stephenw10 do you have any further recommendation / ideas to try out?

else I will go the route of reinstalling the operation system...

stephenw10

Ah, sorry, got distracted by...numerous other things! Let me see here....

What repo branches do you see available? If you set it back to 24.03 and re-run pkg -d update do you see the same error?

HansWerner3dit

@stephenw10 no worries ;)

regarding the pkg -d update: it is exactly the same error for both branches.

see the diff for both commands on different branches

https://www.diffchecker.com/k3NqSkre/

Gertjan

@HansWerner3dit said in No packages in available packages list:

https://www.diffchecker.com/k3NqSkre/

Actually, everything look fine, except for the last 4,5 lines.

DBG(1)[95168]> PkgRepo: extracting signature of repo in a sandbox
pkg: No trusted public keys found
Unable to update repository pfSense

signatures are extract to a temporary location (before used).
What if this temporary location (aka sandbox) couldn't be created because of file system errors ?

Free disk space ok ?
File system ok ? See Netgate Youtube channel, there is a video that shopws you how to test the file system.

stephenw10

Check: /usr/local/share/pfSense/keys/pkg/trusted/
Do you see keys present?

Check: /usr/local/etc/pfSense/pkg/repos
Do you see entries for the available branches?

HansWerner3dit

@Gertjan said in No packages in available packages list:

Free disk space ok ?

space usage should not be a problem except the devfs (/dev) one?

[24.03-RELEASE][admin@pfSense.3dit.local]/root: df -h
Filesystem                     Size    Used   Avail Capacity  Mounted on
/dev/ufsid/5e9a0bc1bef83450    6.7G    2.5G    3.7G    40%    /
devfs                          1.0K      0B    1.0K     0%    /dev
tmpfs                           60M    288K     60M     0%    /tmp
tmpfs                          100M     16M     84M    16%    /var

HansWerner3dit

@stephenw10 said in No packages in available packages list:

Check: /usr/local/share/pfSense/keys/pkg/trusted/
Do you see keys present?

Yes, there are a few keys in there. but are those ok'ish?

[24.03-RELEASE][admin@pfSense.3dit.local]/root: ls -la /usr/local/share/pfSense/keys/pkg/trusted/
total 24
drwxr-xr-x  2 root wheel 512 Jan 13 12:06 .
drwxr-xr-x  4 root wheel 512 Apr 19  2024 ..
-rw-r--r--  1 root wheel  95 Apr 19  2024 beta.pfsense.org.20151223
-rw-r--r--  1 root wheel  95 Apr 19  2024 ce-beta.pfsense.org.20151223
-rw-r--r--  1 root wheel  95 Apr 19  2024 ce-pkg.pfsense.org.20160406
-rw-r--r--  1 root wheel  95 Jan 13 12:06 pkg.pfsense.org.20160406

HansWerner3dit

@stephenw10 said in No packages in available packages list:

Check: /usr/local/etc/pfSense/pkg/repos
Do you see entries for the available branches?

i do see some repository files in there...

[24.03-RELEASE][admin@pfSense.3dit.local]/usr/local/etc/pfSense/pkg/repos: ls /usr/local/etc/pfSense/pkg/repos
pfSense-repo-0000-cert.pem pfSense-repo-0000.default  pfSense-repo-0001-key.pem  pfSense-repo-0001.name
pfSense-repo-0000-key.pem  pfSense-repo-0000.descr    pfSense-repo-0001.abi      pfSense-repo-0001.version
pfSense-repo-0000.abi      pfSense-repo-0000.name     pfSense-repo-0001.altabi
pfSense-repo-0000.altabi   pfSense-repo-0000.version  pfSense-repo-0001.conf
pfSense-repo-0000.conf     pfSense-repo-0001-cert.pem pfSense-repo-0001.descr

the fingerprints entry points to /usr/local/share/pfSense/keys/pkg instead of the trusted subpath /usr/local/share/pfSense/keys/pkg/trusted. could that be an issue?

[24.03-RELEASE][admin@pfSense.3dit.local]/usr/local/etc/pfSense/pkg/repos: cat pfSense-repo-0000.conf 
FreeBSD: { enabled: no }

pfSense-core: {
    url: "pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core",
    mirror_type: "srv",
    signature_type: "fingerprints",
    fingerprints: "/usr/local/share/pfSense/keys/pkg",
    enabled: yes
}

pfSense: {
    url: "pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03",
    mirror_type: "srv",
    signature_type: "fingerprints",
    fingerprints: "/usr/local/share/pfSense/keys/pkg",
    enabled: yes
}

Gertjan

@HansWerner3dit said in No packages in available packages list:

the fingerprints entry points to /usr/local/share/pfSense/keys/pkg instead of the trusted subpath /usr/local/share/pfSense/keys/pkg/trusted. could that be an issue?

I'm on 24.11, and see the same thing, so I presume that not an issue.

Your /usr/local/etc/pfSense/pkg/repos looks fine, but I have one file more :
pfSense-repo-0000.release
and it contains one character :

Important detail (that you didn't show) :

[24.11-RELEASE][root@pfSense.bhf.tld]/root: ll  /usr/local/etc/pfSense/pkg/repos/
total 17
-rw-r--r--  1 root wheel 2057 Feb  4 09:34 pfSense-repo-0000-cert.pem
-rw-r--r--  1 root wheel 3243 Feb  4 09:34 pfSense-repo-0000-key.pem
-rw-r--r--  1 root wheel   16 Feb  4 09:34 pfSense-repo-0000.abi
-rw-r--r--  1 root wheel   17 Feb  4 09:34 pfSense-repo-0000.altabi
-rw-r--r--  1 root wheel  506 Feb  4 09:34 pfSense-repo-0000.conf
-rw-r--r--  1 root wheel    1 Feb  4 09:34 pfSense-repo-0000.default
-rw-r--r--  1 root wheel   30 Feb  4 09:34 pfSense-repo-0000.descr
-rw-r--r--  1 root wheel    5 Feb  4 09:34 pfSense-repo-0000.name
-rw-r--r--  1 root wheel    1 Feb  4 09:34 pfSense-repo-0000.release
-rw-r--r--  1 root wheel   12 Feb  4 09:34 pfSense-repo-0000.version

= the files date and time. Mine are all pretty recent, as they get updated when "pkg" syncs with the package server. Last time that happened was today, at 09h34, or about 70 minutes ago.
You see the same time date ?

I don't have the file that start with
pfSense-repo-0001*

Files in /usr/local/share/pfSense/keys/pkg/trusted/
I have the same set of files. Same names, same file size (95 bytes).

HansWerner3dit

@Gertjan said in No packages in available packages list:

Important detail (that you didn't show) :

Sorry, i had them, but my post always got flagged as spam :/

[24.03-RELEASE][admin@pfSense.3dit.local]/usr/local/etc/pfSense/pkg/repos: ls -l /usr/local/etc/pfSense/pkg/repos
total 68
-rw-r--r--  1 root wheel 2053 Feb  4 10:03 pfSense-repo-0000-cert.pem
-rw-r--r--  1 root wheel 3243 Feb  4 10:03 pfSense-repo-0000-key.pem
-rw-r--r--  1 root wheel   16 Feb  4 10:03 pfSense-repo-0000.abi
-rw-r--r--  1 root wheel   17 Feb  4 10:03 pfSense-repo-0000.altabi
-rw-r--r--  1 root wheel  506 Feb  4 10:03 pfSense-repo-0000.conf
-rw-r--r--  1 root wheel    1 Feb  4 10:03 pfSense-repo-0000.default
-rw-r--r--  1 root wheel   31 Feb  4 10:03 pfSense-repo-0000.descr
-rw-r--r--  1 root wheel    9 Feb  4 10:03 pfSense-repo-0000.name
-rw-r--r--  1 root wheel   12 Feb  4 10:03 pfSense-repo-0000.version
-rw-r--r--  1 root wheel 2053 Feb  4 10:03 pfSense-repo-0001-cert.pem
-rw-r--r--  1 root wheel 3243 Feb  4 10:03 pfSense-repo-0001-key.pem
-rw-r--r--  1 root wheel   16 Feb  4 10:03 pfSense-repo-0001.abi
-rw-r--r--  1 root wheel   17 Feb  4 10:03 pfSense-repo-0001.altabi
-rw-r--r--  1 root wheel  506 Feb  4 10:03 pfSense-repo-0001.conf
-rw-r--r--  1 root wheel   30 Feb  4 10:03 pfSense-repo-0001.descr
-rw-r--r--  1 root wheel    5 Feb  4 10:03 pfSense-repo-0001.name
-rw-r--r--  1 root wheel   12 Feb  4 10:03 pfSense-repo-0001.version

i have been moving the 0001 repos out of the folder and created a .release file with content 1 ... but did had no effect when running the pkg -d update command.
furthermore, when changing the release branch, the folder structure was restored (with 0000 and 0001 repos)

in addition, i have been running the fsck command mulltiple times (like in the youtube netgate video shown) ... filesystem should be ok.

Gertjan

@HansWerner3dit said in No packages in available packages list:

i have been moving the 0001 repos out of the folder and created a .release file with content 1 ... but did had no effect when running the pkg -d update command.
furthermore, when changing the release branch, the folder structure was restored (with 0000 and 0001 repos)

The time / date is very recent, like minutes ago. So nothing awkward there.
I guess the "0001" files are there as they indicate the 'future' version ? (check content to be sure)

@HansWerner3dit said in No packages in available packages list:

i have been running the fsck command mulltiple times

From the console, while booting, right ?

stephenw10

Ok that all looks good.

Check:

[24.11-RELEASE][admin@4200.stevew.lan]/root: ls -ls /usr/local/etc/pkg/repos
total 1
1 -rw-r--r--  1 root wheel 25 Nov 21 21:00 FreeBSD.conf
1 lrwxr-xr-x  1 root wheel 55 Jan  7 16:45 pfSense.conf -> /usr/local/etc/pfSense/pkg/repos/pfSense-repo-0002.conf

That symlink is what gets changed when you set a different repo branch.

If it's pointing at /usr/local/share/pfSense/pkg/repos then check that: ls -ls /usr/local/share/pfSense/pkg/repos
That#s the old repo system that would only ever be used now if the system cannot access the dynamic repos.