After upgrade to Jazzy Jaguar, update fails (403). Is the repo locked down?

Started by d0zr, January 07, 2020, 12:39:13 PM

Previous topic - Next topic
Recently upgraded to 19.7 from the latest 19.1.

Used the installer to restore my config from 19.1, everything worked except it wouldn't update. 
"Firmware status check was aborted internally. Please try again."

So I installed from scratch with the default network settings, connected to the world, updated successfully all the way to 19.7.8.  Then restored from my most recent 19.1.x config.xml. 

After restore, update was broken again.  Searching around the usual suspects are:

0. Pressing update again. (always works 2nd time).  Not for me :(

1. Disaabling IPv6. Mine has always been disabled.  With legacy IPv6, connectivity can be broken so the package manager will not resolve. Made no difference for me :(

2. pkg update -f
Updating OPNsense repository catalogue...
pkg: https://opnsense-update.deciso.com/FreeBSD:11:amd64/19.7/latest/meta.txz: Forbidden
repository OPNsense has no meta file, using default settings
pkg: https://opnsense-update.deciso.com/FreeBSD:11:amd64/19.7/latest/packagesite.txz: Forbidden
Unable to update repository OPNsense
Error updating repositories!


3. Tried to update a single pkg
***GOT REQUEST TO REINSTALL: ca_root_nss***
Updating OPNsense repository catalogue...
pkg-static: https://opnsense-update.deciso.com/FreeBSD:11:amd64/19.7/latest/meta.txz: Forbidden
repository OPNsense has no meta file, using default settings
pkg-static: https://opnsense-update.deciso.com/FreeBSD:11:amd64/19.7/latest/packagesite.txz: Forbidden
Unable to update repository OPNsense
Error updating repositories!
Checking integrity... done (0 conflicting)
Nothing to do.
***DONE***


Is the repo locked down atm?
Is it looking at the correct URL?  Connecting at the console with opnsense-update -fp -n "19.7\/latest", or using a browser, responds the same way: Access Denied.
/usr/local/etc/pkg/repos/OPNsense.conf points to the url: "pkg+https://opnsense-update.deciso.com/${ABI}/19.7/latest"  Can this be edited to fix it?

PS. Sorry about bringing this up twice, seems there is another just like this 2 days ago; https://forum.opnsense.org/index.php?topic=15436.0 Maybe we can get 2 birds with one stone!

Do you have a business subscription? If not this isn't the right update server to use.


Cheers,
Franco

Thanks Franco, fixed!

Just had to go System>Firmware>Updates>Settings and select a different (open) mirror.

Maybe in waiting to move to 19.7, I missed an update that addressed this (unless the default changed 'otherhow')

I managed to miss that config in the UI too.  :-[ My sincerest apologies for the long post...  ::)