checking for updates failing after fresh install

[skyeci2018]

Hi,

I fired up my old apu and did a fresh install of 22.7. Whilst that all went well I keep getting this error when trying to check from updates from the console and in the gui...

Enter an option: 12

Fetching change log information, please wait... Certificate verification failed for /C=BE/O=GlobalSign nv-sa/CN=GlobalSign GCC R3 DV TLS CA 2020
34389172224:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1921:
fetch: https://pkg.opnsense.org/FreeBSD:13:amd64/22.7/sets/changelog.txz: Authentication error

Any ideas?

thanks

[franco]

Possibly the bad ACME bundles from System: Trust: Authorities that are installed in your system.


Cheers,
Franco

[skyeci2018]

this is a fresh install downloaded today...?

[franco]

First of all you cropped the error but didn't give the full log which can hide numerous issues to no benefit of being able to support you.

Secondly, you could still have restored an older config.xml and chose to not tell us.


Cheers,
Franco

[skyeci2018]

Hi Franco

I did not install any previous settings or configs. This was a completly fresh install - no tweaks or otherwise.

I have also seen this message as well in case its of any interest. I didn't crop the logs - I displayed what was displayed ...

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 22.7_4 (amd64/OpenSSL) at Sun Jul 31 12:30:48 BST 2022
Fetching changelog information, please wait... fetch: transfer timed out
Updating OPNsense repository catalogue...
pkg: Repository OPNsense has a wrong packagesite, need to re-create database

[Mistery]

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 22.7_4 (amd64/OpenSSL) at Sun Jul 31 12:30:48 BST 2022
Fetching changelog information, please wait... fetch: transfer timed out
Updating OPNsense repository catalogue...
pkg: Repository OPNsense has a wrong packagesite, need to re-create database

Same issue here after upgrading from 22.1 to 22.7, updates failing with transfer timed out error, tried other mirrors and failing as well

[hushcoden]

Fresh install today, no restore from config file and same issue.

[thebandit]

Same for me. Seems like there's something wrong with an update server.

[cookiemonster]

What shows for System > Firmware > Status > Connectivity ?
It should show a failure to the repository that can be worked on.

[Dav3]

Is your date/time set accurately ?
If not, is your dns working ?

If not, temporarily set dns to something simple like 8.8.8.8, then sync clock

[axsdenied]

Interesting... i just did this today with no issue.

[Mistery]

Is your date/time set accurately ?
If not, is your dns working ?

If not, temporarily set dns to something simple like 8.8.8.8, then sync clock

I tried this as well and still not working, anyway this issue appeared just after upgrading to 22.7 so there must be something broken with this release.

[franco]

I don't see any evidence supporting this yet. Make it sound like we don't generally test firmware upgrades for a major upgrade...

Connectivity audits now please. Change your mirror to see if that helps.


Cheers,
Franco

[Mistery]

I don't see any evidence supporting this yet. Make it sound like we don't generally test firmware upgrades for a major upgrade...
Connectivity audits now please. Change your mirror to see if that helps.

As previously reported I already tried switching to many different mirrors and the result is the same.
Also there are no issues with the connectivity from my side

[franco]

This is really really bogus because the OP stated:

Fetching change log information, please wait... Certificate verification failed for /C=BE/O=GlobalSign nv-sa/CN=GlobalSign GCC R3 DV TLS CA 2020
34389172224:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1921:
fetch: https://pkg.opnsense.org/FreeBSD:13:amd64/22.7/sets/changelog.txz: Authentication error

And you CANNOT get that error with another mirror.

So that's what you get for cross-posting "same issue" and I'm unwilling to debug your local issue further. Good luck.


Cheers,
Franco