Update error

[HenrysCat]

I keep getting this error when checking for updates, is this normal?

Code: [Select]

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 22.1.2_1 (amd64/OpenSSL) at Sun Mar 20 19:53:09 GMT 2022
Fetching changelog information, please wait... fetch: transfer timed out
Updating OPNsense repository catalogue...
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/22.1/latest/meta.txz: Operation timed out
repository OPNsense has no meta file, using default settings
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/22.1/latest/packagesite.txz: Operation timed out
Unable to update repository OPNsense
Error updating repositories!
pkg: Repository OPNsense cannot be opened. 'pkg update' required
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***

[Lynxcat]

Looks like your wan port doesn't have proper access to Internet or is not setup properly.
Try connecting your wan port as DHCP client to a working network with internet access or make sure your wan port uses proper authentication if PPoE or other than DHCP.

[HenrysCat]

That doesn't make sense to me, this has been working fine for well over a year now, and the internet is working fine otherwise I wouldn't be able to post this, it's only since 22.1 update this has started.

[Lynxcat]

Did you try to change the mirror in the Settings ?

[franco]

It doesn't make sense to us either. The mirror has been working well for years?


Cheers,
Franco

[HenrysCat]

I got it to update by restarting, and I mean power off/on, reboot did not work.

However when I press check for updates again same problem, it wont work until power off/on ?

Code: [Select]

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 22.1.3 (amd64/OpenSSL) at Mon Mar 21 19:17:20 GMT 2022
Fetching changelog information, please wait... fetch: transfer timed out
Updating OPNsense repository catalogue...
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/22.1/latest/meta.txz: Operation timed out
repository OPNsense has no meta file, using default settings
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/22.1/latest/packagesite.txz: Operation timed out
Unable to update repository OPNsense
Error updating repositories!
pkg: Repository OPNsense cannot be opened. 'pkg update' required
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***

[franco]

Can you do the connectivity audit?


Cheers,
Franco

[HenrysCat]

Code: [Select]

***GOT REQUEST TO AUDIT CONNECTIVITY***
Currently running OPNsense 22.1.3 (amd64/OpenSSL) at Mon Mar 21 19:56:58 GMT 2022
Checking connectivity for host: pkg.opnsense.org -> 89.149.211.205
PING 89.149.211.205 (89.149.211.205): 1500 data bytes
1508 bytes from 89.149.211.205: icmp_seq=0 ttl=56 time=15.275 ms
1508 bytes from 89.149.211.205: icmp_seq=1 ttl=56 time=15.204 ms
1508 bytes from 89.149.211.205: icmp_seq=2 ttl=56 time=21.178 ms
1508 bytes from 89.149.211.205: icmp_seq=3 ttl=56 time=15.323 ms

--- 89.149.211.205 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 15.204/16.745/21.178/2.560 ms
Checking connectivity for repository (IPv4): https://pkg.opnsense.org/FreeBSD:13:amd64/22.1
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.txz: .......... done
Processing entries: .......... done
OPNsense repository update completed. 783 packages processed.
All repositories are up to date.
Checking connectivity for host: pkg.opnsense.org -> 2001:1af8:4f00:a005:5::
ping6: UDP connect: No route to host
Checking connectivity for repository (IPv6): https://pkg.opnsense.org/FreeBSD:13:amd64/22.1
Updating OPNsense repository catalogue...
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/22.1/latest/meta.txz: Non-recoverable resolver failure
repository OPNsense has no meta file, using default settings
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/22.1/latest/packagesite.txz: Non-recoverable resolver failure
Unable to update repository OPNsense
Error updating repositories!
***DONE***

[franco]

Yep, your IPv6 is broken but IPv4 works. You can either set to prefer IPv4 (System: Settings: General) or try to fix IPv6 on the box. What's your IPv6 setup?


Cheers,
Franco

[HenrysCat]

I don't use IPv6 at all, I have set "prefer IPv4" and now get this?
(I do have internet as I posted this)

Code: [Select]

***GOT REQUEST TO AUDIT CONNECTIVITY***
Currently running OPNsense 22.1.3 (amd64/OpenSSL) at Mon Mar 21 20:28:16 GMT 2022
Checking connectivity for host: pkg.opnsense.org -> 89.149.211.205
PING 89.149.211.205 (89.149.211.205): 1500 data bytes

--- 89.149.211.205 ping statistics ---
4 packets transmitted, 0 packets received, 100.0% packet loss
Checking connectivity for repository (IPv4): https://pkg.opnsense.org/FreeBSD:13:amd64/22.1
Updating OPNsense repository catalogue...
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/22.1/latest/meta.txz: Operation timed out
repository OPNsense has no meta file, using default settings
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/22.1/latest/packagesite.txz: Operation timed out
Unable to update repository OPNsense
Error updating repositories!
Checking connectivity for host: pkg.opnsense.org -> 2001:1af8:4f00:a005:5::
ping6: UDP connect: No route to host
Checking connectivity for repository (IPv6): https://pkg.opnsense.org/FreeBSD:13:amd64/22.1
Updating OPNsense repository catalogue...
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/22.1/latest/meta.txz: Non-recoverable resolver failure
repository OPNsense has no meta file, using default settings
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/22.1/latest/packagesite.txz: Non-recoverable resolver failure
Unable to update repository OPNsense
Error updating repositories!
***DONE***

[franco]

Now you have two problems... ?!


Cheers,
Franco

[gpb]

I had a GeoIP filter at one point that was blocking that server 89.149.211.205 (I'm assuming that's the primary opnsense update server).

[HenrysCat]

I thought GeoIP filters blocked incoming connections, not outgoing, right?

[gpb]

I set mine up for both directions.  Don't need to click a web page link and go where I don't want to.  So I guess you'd need to check your rules.

[HenrysCat]

I guess my rules are fine then, this problem only started since the v22.x uodates, the actual config has not been modified in over a year, is it still possible to download v21.x image files? I think I'll just reinstall that.