Package List Empty

[yaw]

Is there an issue with Netgate's servers? After updating to 23.01, the "Available Packages" is empty, and I keep getting the following error when running pkg update:

Updating pfSense-core repository catalogue...
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg01.atx.netgate.com
35165192192:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:

[asdjklfjkdslfdsaklj]

This post is deleted!

[yaw]

Must have been a server issue. Package list is working now.

[coolspot]

My list is empty today as well ... pfsense-plus-pkg.netgate.com can't be resolved, is it down again?

[stephenw10]

Nope, because: https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#packages-netgate-com-has-no-a-aaaa-record

steve@steve-NUC9i9QNX:~$ host -t srv _https._tcp.pfsense-plus-pkg.netgate.com
_https._tcp.pfsense-plus-pkg.netgate.com has SRV record 10 10 443 pfsense-plus-pkg01.atx.netgate.com.
_https._tcp.pfsense-plus-pkg.netgate.com has SRV record 10 10 443 pfsense-plus-pkg00.atx.netgate.com.
steve@steve-NUC9i9QNX:~$ host pfsense-plus-pkg01.atx.netgate.com
pfsense-plus-pkg01.atx.netgate.com has address 208.123.73.209
pfsense-plus-pkg01.atx.netgate.com has IPv6 address 2610:160:11:18::209
steve@steve-NUC9i9QNX:~$ host pfsense-plus-pkg00.atx.netgate.com
pfsense-plus-pkg00.atx.netgate.com has address 208.123.73.207
pfsense-plus-pkg00.atx.netgate.com has IPv6 address 2610:160:11:18::207

Steve

[coolspot]

@stephenw10 said in Package List Empty:

Nope, because: https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#packages-netgate-com-has-no-a-aaaa-record

Thanks, I get the following error when trying to force a reinstall of pkg (Bad Request):

[23.01-RELEASE][admin@pfsense.xxx.com]/root: pkg-static upgrade -f
Updating pfSense-core repository catalogue...
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-core/meta.txz: Bad Request
repository pfSense-core has no meta file, using default settings
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-core/packagesite.pkg: Bad Request
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-core/packagesite.txz: Bad Request
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/meta.txz: Bad Request
repository pfSense has no meta file, using default settings
pkg-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.pkg: Bad Request
pkg-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.txz: Bad Request
Unable to update repository pfSense
Error updating repositories!

Even if I force ipv4?

[23.01-RELEASE][admin@pfsense.xxx.com]/root: pfSense-upgrade -4
Your device has not been registered for pfSense+. Please purchase a pfSense+ subscription at the <a href="https://shop.netgate.com/products/pfsense-software-subscription" target="_blank" rel="noopener noreferrer">Netgate store</a> to receive future updates.
ERROR: It was not possible to determine pkg remote version
>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-core/meta.txz: Bad Request
repository pfSense-core has no meta file, using default settings
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-core/packagesite.pkg: Bad Request
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-core/packagesite.txz: Bad Request
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/meta.txz: Bad Request
repository pfSense has no meta file, using default settings
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.pkg: Bad Request
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.txz: Bad Request
Unable to update repository pfSense
Error updating repositories!
ERROR: It was not possible to determine pfSense-upgrade remote version
ERROR: It was not possible to determine pfSense-upgrade remote version
>>> Upgrading pfSense-upgrade... failed.

UPDATE: OK I fixed it, I had to download another pfSense Registration Token, then I ran pfSense-upgrade -4 and now my packages show up...

[stephenw10]

Yeah, bad request there means it's not sending a valid cert that's required to access that repo server. It sounds like maybe your NDI changed if re-registering it fixed the issue.

Steve

[mfld]

@stephenw10 said in Package List Empty:

Yeah, bad request there means it's not sending a valid cert that's required to access that repo server. It sounds like maybe your NDI changed if re-registering it fixed the issue.

Steve

How do y'all re-register ? I have the same issue right now but

/system_register.php

has the key greyed out because it is already registered. What file do I need to rename to make it forget ?

Edit: is it

/usr/local/share/pfSense/keys/pkg

?

[dem]

My available package list has come up empty a couple of times since moving to 23.01. Visiting System->Update seems to cause the list of available packages to repopulate.

[stephenw10]

@mfld said in Package List Empty:

How do y'all re-register ? I have the same issue right now

What device do you have? If you send me your NDI in chat I can check it.

Steve

[stephenw10]

@dem said in Package List Empty:

Visiting System->Update seems to cause the list of available packages to repopulate

If you have the webgui open in a tab for a long time the cert may have expired when you visit the package manager or if you run a pkg command at the CLI you might see that request error.
Visiting the Firmware Upgrade page or the dashboard with the update check enabled or running pfSense-upgrade -c will pull a new cert. So usually that's the first thing that happens when you login and you should always have a current cert.

Steve

[dem]

@stephenw10 I have the dashboard check disabled so that might explain why I've seen the empty list a few times.

[Vollans]

@dem Same here as it slows dashboard loading so much when you login.

[mfld]

@stephenw10 said in Package List Empty:

or running pfSense-upgrade -c will pull a new cert.

Weird. Some boxes are effected and what I see on these is

pfSense-upgrade -c
......ERROR: It was not possible to determine pkg remote version
>>> Updating repositories metadata... failed.
ERROR: It was not possible to determine pfSense remote version
ERROR: It was not possible to determine pfSense-base remote version
ERROR: It was not possible to determine pfSense-kernel-pfSense remote version
Your system is up to date

On a good box I see

pfSense-upgrade -c
>>> Updating repositories metadata... done.
Your system is up to date

pfSense-upgrade -c

did not seem to help.

pkg update
Updating pfSense-core repository catalogue...
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
35158245376:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
35158245376:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
35158245376:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
[snip]
routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-core/meta.txz: **Authentication error**

It keeps happening to different boxes at different times.

[mfld]

@stephenw10 said in Package List Empty:

running pfSense-upgrade -c will pull a new cert.

Is that instant / real-time ? Because I see this on a working box:

mv /etc/ssl/pfSense-repo-custom.cert /etc/ssl/pfSense-repo-custom.cert.TESTING

pfSense-upgrade -c
>>> Updating repositories metadata... done.
Your system is up to date

It seemingly completed fine. But now there is no /etc/ssl/pfSense-repo-custom.cert

[stephenw10]

That's the cert for the CE > Plus upgrade repo. The dynamic repo cert is passed with the repo details and, yes, it's updated close to instantly:

[23.05-DEVELOPMENT][admin@plusdev.stevew.lan]/root: ls -ls /usr/local/etc/pfSense/pkg/repos
total 29
1 -rw-r--r--  1 root  wheel    16 Mar 12 01:08 pfSense-repo-23.05-Devel.abi
1 -rw-r--r--  1 root  wheel    17 Mar 12 01:08 pfSense-repo-23.05-Devel.altabi
5 -rw-r--r--  1 root  wheel   547 Mar 12 01:08 pfSense-repo-23.05-Devel.conf
1 -rw-r--r--  1 root  wheel    36 Mar 12 01:08 pfSense-repo-23.05-Devel.descr
1 -rw-r--r--  1 root  wheel    11 Mar 12 01:08 pfSense-repo-23.05-Devel.name
1 -rw-r--r--  1 root  wheel    16 Mar 12 01:08 pfSense-repo-prev.abi
1 -rw-r--r--  1 root  wheel    17 Mar 12 01:08 pfSense-repo-prev.altabi
5 -rw-r--r--  1 root  wheel   498 Mar 12 01:08 pfSense-repo-prev.conf
1 -rw-r--r--  1 root  wheel    31 Mar 12 01:08 pfSense-repo-prev.descr
1 -rw-r--r--  1 root  wheel     4 Mar 12 01:08 pfSense-repo-prev.name
5 -rw-r--r--  1 root  wheel  2053 Mar 12 01:08 pfSense-repo-stable-cert.pem
5 -rw-------  1 root  wheel  3243 Mar 12 01:08 pfSense-repo-stable-key.pem
1 -rw-r--r--  1 root  wheel    16 Mar 12 01:08 pfSense-repo-stable.abi
1 -rw-r--r--  1 root  wheel    17 Mar 12 01:08 pfSense-repo-stable.altabi
5 -rw-r--r--  1 root  wheel   506 Mar 12 01:08 pfSense-repo-stable.conf
1 -rw-r--r--  1 root  wheel     1 Mar 12 01:08 pfSense-repo-stable.default
1 -rw-r--r--  1 root  wheel    29 Mar 12 01:08 pfSense-repo-stable.descr
1 -rw-r--r--  1 root  wheel     6 Mar 12 01:08 pfSense-repo-stable.name
[23.05-DEVELOPMENT][admin@plusdev.stevew.lan]/root: pfSense-upgrade -c
>>> Updating repositories metadata... done.
Your system is up to date
[23.05-DEVELOPMENT][admin@plusdev.stevew.lan]/root: ls -ls /usr/local/etc/pfSense/pkg/repos
total 29
1 -rw-r--r--  1 root  wheel    16 Mar 12 02:09 pfSense-repo-23.05-Devel.abi
1 -rw-r--r--  1 root  wheel    17 Mar 12 02:09 pfSense-repo-23.05-Devel.altabi
5 -rw-r--r--  1 root  wheel   547 Mar 12 02:09 pfSense-repo-23.05-Devel.conf
1 -rw-r--r--  1 root  wheel    36 Mar 12 02:09 pfSense-repo-23.05-Devel.descr
1 -rw-r--r--  1 root  wheel    11 Mar 12 02:09 pfSense-repo-23.05-Devel.name
1 -rw-r--r--  1 root  wheel    16 Mar 12 02:09 pfSense-repo-prev.abi
1 -rw-r--r--  1 root  wheel    17 Mar 12 02:09 pfSense-repo-prev.altabi
5 -rw-r--r--  1 root  wheel   498 Mar 12 02:09 pfSense-repo-prev.conf
1 -rw-r--r--  1 root  wheel    31 Mar 12 02:09 pfSense-repo-prev.descr
1 -rw-r--r--  1 root  wheel     4 Mar 12 02:09 pfSense-repo-prev.name
5 -rw-r--r--  1 root  wheel  2053 Mar 12 02:09 pfSense-repo-stable-cert.pem
5 -rw-------  1 root  wheel  3243 Mar 12 02:09 pfSense-repo-stable-key.pem
1 -rw-r--r--  1 root  wheel    16 Mar 12 02:09 pfSense-repo-stable.abi
1 -rw-r--r--  1 root  wheel    17 Mar 12 02:09 pfSense-repo-stable.altabi
5 -rw-r--r--  1 root  wheel   506 Mar 12 02:09 pfSense-repo-stable.conf
1 -rw-r--r--  1 root  wheel     1 Mar 12 02:09 pfSense-repo-stable.default
1 -rw-r--r--  1 root  wheel    29 Mar 12 02:09 pfSense-repo-stable.descr
1 -rw-r--r--  1 root  wheel     6 Mar 12 02:09 pfSense-repo-stable.name

Steve

[mfld]

@stephenw10 said in Package List Empty:

That's the cert for the CE > Plus upgrade repo. The dynamic repo cert is passed with the repo details and, yes, it's updated close to instantly:

Weird.

pfSense-upgrade -d -c
......ERROR: It was not possible to determine pkg remote version
>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
34937565184:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
34937565184:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
34937565184:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
34937565184:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-core/meta.txz: Authentication error
repository pfSense-core has no meta file, using default settings
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
34937565184:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
34937565184:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-core/packagesite.pkg: Authentication error
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
34937565184:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
34937565184:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-core/packagesite.txz: Authentication error
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
34937565184:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
34937565184:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
34937565184:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
34937565184:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/meta.txz: Authentication error
repository pfSense has no meta file, using default settings
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
34937565184:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
34937565184:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.pkg: Authentication error
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
34937565184:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
34937565184:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.txz: Authentication error
Unable to update repository pfSense
Error updating repositories!
ERROR: It was not possible to determine pfSense remote version
ERROR: It was not possible to determine pfSense-base remote version
ERROR: It was not possible to determine pfSense-kernel-pfSense remote version
Your system is up to date

But the time stamps of those certs DID update!

ls -ls /usr/local/etc/pfSense/pkg/repos
total 16
5 -rw-r--r--  1 root  wheel  2057 Mar 12 14:52 pfSense-repo-stable-cert.pem
5 -rw-------  1 root  wheel  3243 Mar 12 14:52 pfSense-repo-stable-key.pem
1 -rw-r--r--  1 root  wheel    16 Mar 12 14:52 pfSense-repo-stable.abi
1 -rw-r--r--  1 root  wheel    17 Mar 12 14:52 pfSense-repo-stable.altabi
5 -rw-r--r--  1 root  wheel   506 Mar 12 14:52 pfSense-repo-stable.conf
1 -rw-r--r--  1 root  wheel     1 Mar 12 14:52 pfSense-repo-stable.default
1 -rw-r--r--  1 root  wheel    29 Mar 12 14:52 pfSense-repo-stable.descr
1 -rw-r--r--  1 root  wheel     6 Mar 12 14:52 pfSense-repo-stable.name

Will DM you the NDI

[mfld]

Went nuclear after nothing worked.

mkdir /root/backup && cp -r /usr/local/etc/pfSense/pkg/repos /root/backup/ && rm -rf /usr/local/etc/pfSense/pkg/repos && pfSense-upgrade -c -d

Resolved it on that instance.

[overlordchex]

@stephenw10

I'm having this same issue as I mistakenly acquired a new token thinking I would need one after changing out the OS Drive. the system automatically activates itself with the old token and then drops the SSL certs after about a week. the registration option is grayed out so I have no means of fixing it

[bavcon22]

This post is like I posted in, look at link below: https://forum.netgate.com/post/1097286