No available packages

tedquade

@g-hammer see:

https://redmine.pfsense.org/issues/14137

Ted Quade

stephenw10

@g-hammer said in No available packages:

Where would I do this?

You can run it at the command line via the console or ssh. Or you can run in Diag > Command Prompt in the GUI.

Steve

G.Hammer

@stephenw10
rm: /usr/local/share/pfSense/pkg/repos/pfSense-repo-custom.*: No such file or directory

Already gone.
I do have a package listing and have installed what I wanted.
Thanks for the rapid diagnosis and solution.

flatsphere

@stephenw10 Received this message at Diagnostics/Command Prompt

rm: /usr/local/share/pfSense/pkg/repos/pfSense-repo-custom.*: No such file or directory

Still no packages.

G.Hammer

@tedquade Working for you, meaning you have a packages list and can install? Have you rebooted to make certain the fix survives?

No reason to think it doesn't, just checking.

tedquade

@g-hammer Yes, Yes and Yes (I'm a person of few words).

Ted Quade

stephenw10

@flatsphere said in No available packages:

rm: /usr/local/share/pfSense/pkg/repos/pfSense-repo-custom.*: No such file or directory
Still no packages.

Did you also resave the update repo settings?

Are you also seeing the 'Bad Request' error from pkg -d update?
There are other reasons you might not see packages. Bug #14137 only applies to recent upgrades from CE.

flatsphere

@stephenw10 said in No available packages:

pkg -d update

Hi Stephen,

Yes, saved but I've no selections in update other than "Latest Stable Version (23.01)" . Saved and rebooted. Also tried "Disable the Dashboard auto-update check", saved and rebooted.
Yes, getting "bad request" from pkg -d update.
I did recently upgrade from latest version of CE.

Cheers!
R

tedquade

@flatsphere

From the Dashboard go to:
System > Update > Update Settings then "Save"

Then Diagnostics > Command Prompt > Execute Shell Command then in Command enter the following:
rm /usr/local/share/pfSense/pkg/repos/pfSense-repo-custom.*

Then select Execute.

That is the sequence I followed and it worked for me.

Ted Quade

flatsphere

@tedquade said in No available packages:

rm /usr/local/share/pfSense/pkg/repos/pfSense-repo-custom.*

I did that and received the "No such file or directory" message.

Thanks!
R

stephenw10

Send me your NDI and the output pkg -d update in chat and I'll check it.

p1erre

@stephenw10 said in No available packages:

Send me your NDI and the output pkg -d update in chat and I'll check it.

Hi Stephen

I get the same error on my Netgate 6100 without upgrading from a CE

Error messages posted on https://redmine.pfsense.org/issues/14137

stephenw10

Did you resave the stable repo settings?

p1erre

@stephenw10 said in No available packages:

Did you resave the stable repo settings?

Yes I did. It also shows me the latest stable version 23.01

Current Base System23.01
Latest Base System23.01
StatusUp to date.

stephenw10

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

That error means it's trying to authenticate the repo using the wrong cert. Resaving the repo should set the correct line in the config file so it then uses the correct cert.

Steve

tedquade

@p1erre You need to do the following in order to save as instructed by Steve:

System > Update > Update Settings > Save

This is what worked for me when I had similar issues to yours.

Ted Quade

p1erre

@tedquade Thanks Ted, but I already did it. Issue still there. I also did

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

as suggested in another thread. Still getting

pfSense-upgrade -c -d
......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
34942701568: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
...
34942701568: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
34942701568: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

tsrats

I too am unable to see any packages. I believe I switched to pfSense+ but cannot remember. I have followed all the steps in this thread and the bug report and no progress. I also see the following, even though I have registered (and now reregistered) it with pfSense+

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-pkg01.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-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-core/packagesite.pkg: Bad Request                                             
pkg-static: https://pfsense-plus-pkg01.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 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

stephenw10

Most likely your NDI changed since you first registered it. Send it to me in chat and I can check.

DominikHoffmann

I was sent here by @p1erre (Thanks!) from an original thread I had posted: No available packages. My hardware is a Netgate 2100 that had never been on the CE of pfSense. About three weeks ago I updated it from 22.05 to 23.01 using the

run usbrecovery

method, when I had experienced a couple of catastrophic update failures with other pfSense installations I manage.