Messages

Hello, same problem here, but How to fix it I don't understand. Some "how to" explanation available?

And this is the key point: the audit is irrelevant if your updates work.


Cheers,
Franco

Hello Franco, the Upgrade Process starts only with "Prefer to use IPv4 even if IPv6 is available" checked in Settings > General > Networking.

Now I'm on OPNsense Version 25.7.1. Well done guys! You're magic!

OK. Later I'll try the Upgrade process again. Thx.

I've disable IPv6 on WAN (and LAN) according to this guide:

https://www.thomas-krenn.com/en/wiki/OPNsense_disable_IPv6

But even if I set Prefer IPv4 over IPv6 the result of the audit is the same.

@OPNefx it probably prefers the defunct IPv6 on your end.  Either disable IPv6 on WAN or use Prefer IPv4 over IPv6 setting, whatever works best.


Cheers,
Franco

Hello Franco, thank you very much for your quick reply. After the change you suggested nothing change.

I've found this error on System > Log Files > Web GUI:

"Error   lighttpd   (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.79/src/gw_backend.c.533) connect() /var/lib/php/tmp/php-fastcgi.socket-4: Connection refused".

Could it be that this error is related to my problem?

Same Problem here. AUDIT CONNECTIVITY reports:

***GOT REQUEST TO AUDIT CONNECTIVITY***
Currently running OPNsense 25.1.12 (amd64) at Wed Jul 30 16:51:43 CEST 2025
Checking connectivity for host: mirror.fra10.de.leaseweb.net -> 37.58.58.140
PING 37.58.58.140 (37.58.58.140): 1500 data bytes
1508 bytes from 37.58.58.140: icmp_seq=0 ttl=57 time=18.735 ms
1508 bytes from 37.58.58.140: icmp_seq=1 ttl=57 time=18.795 ms
1508 bytes from 37.58.58.140: icmp_seq=2 ttl=57 time=18.638 ms
1508 bytes from 37.58.58.140: icmp_seq=3 ttl=57 time=18.892 ms

--- 37.58.58.140 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 18.638/18.765/18.892/0.092 ms
Checking connectivity for repository (IPv4): https://mirror.fra10.de.leaseweb.net/opnsense/FreeBSD:14:amd64/25.1
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 900 packages processed.
All repositories are up to date.
Checking connectivity for host: mirror.fra10.de.leaseweb.net -> 2a00:c98:2030:a034::21
ping: UDP connect: No route to host
Checking connectivity for repository (IPv6): https://mirror.fra10.de.leaseweb.net/opnsense/FreeBSD:14:amd64/25.1
Updating OPNsense repository catalogue...
pkg: https://mirror.fra10.de.leaseweb.net/opnsense/FreeBSD:14:amd64/25.1/latest/meta.txz: Non-recoverable resolver failure
repository OPNsense has no meta file, using default settings
pkg: https://mirror.fra10.de.leaseweb.net/opnsense/FreeBSD:14:amd64/25.1/latest/packagesite.pkg: Non-recoverable resolver failure
pkg: https://mirror.fra10.de.leaseweb.net/opnsense/FreeBSD:14:amd64/25.1/latest/packagesite.txz: Non-recoverable resolver failure
Unable to update repository OPNsense
Error updating repositories!
Checking server certificate for host: mirror.fra10.de.leaseweb.net
depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = R10
verify return:1
depth=0 CN = mirror.leaseweb.com
verify return:1
DONE
Checking server certificate for host: pkg.opnsense.org
depth=2 C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert Global Root G2
verify return:1
depth=1 C = US, O = DigiCert Inc, OU = www.digicert.com, CN = RapidSSL TLS RSA CA G1
verify return:1
depth=0 CN = pkg.opnsense.org
verify return:1
DONE
***DONE***