Fetching base-26.7.3-amd64.txz [fetch: transfer timed out] failed, no signature

Started by nerd, August 31, 2026, 09:45:40 AM

Previous topic - Next topic
Upgraded to 26.7.3_8 when it came out. As far as I noticed no issues appeared during the upgrade.
Now however, the OPNsense VM keeps claiming "There are 2 updates available, total download size is 125.1MiB. This upgrade requires a reboot."
The 2 files it want me to upgrade are base & kernel, both current version 26.7.2, new version 26.7.3.

Rebooting the FW does not resolve this. Neither does selecting a different mirror.
When I click the Update button it fails to do anything:

***GOT REQUEST TO UPDATE***
Currently running OPNsense 26.7.3_8 (amd64) at Mon Aug 31 09:25:24 CEST 2026
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking for upgrades (0 candidates): . done
Processing candidates (0 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking integrity... done (0 conflicting)
Nothing to do.
Checking all packages: .......... done
Nothing to do.
Nothing to do.
Flushing temporary package files... done
Starting web GUI...done.
Fetching base-26.7.3-amd64.txz: ...[fetch: transfer timed out] failed, no signature found
***DONE***


How do I get rid of this mess?

root@OPNsense:~ # configctl firmware product
{
    "CORE_ABI": "26.7",
    "CORE_ARCH": "amd64",
    "CORE_COMMIT": "26.7.3 8 bf16bfcda",
    "CORE_CONFLICTS": "os-firewall os-firewall-devel os-wireguard os-wireguard-devel os-wireguard-go os-wireguard-go-devel",
    "CORE_COPYRIGHT_HOLDER": "Deciso B.V.",
    "CORE_COPYRIGHT_WWW": "https://www.deciso.com/",
    "CORE_COPYRIGHT_YEARS": "2014-2026",
    "CORE_GID": "789",
    "CORE_GROUP": "wwwonly",
    "CORE_HASH": "bf16bfcda",
    "CORE_MAINTAINER": "project@opnsense.org",
    "CORE_NAME": "opnsense",
    "CORE_NEXT": "27.1",
    "CORE_NICKNAME": "Xenial Xenops",
    "CORE_PACKAGESITE": "https://pkg.opnsense.org",
    "CORE_PKGVERSION": "26.7.3_8",
    "CORE_PRODUCT": "OPNsense",
    "CORE_PYTHON_DOT": "3.13",
    "CORE_SERIES": "26.7",
    "CORE_SERIES_FW": "26.7 ",
    "CORE_SYSLOGNG": "4.12",
    "CORE_UID": "789",
    "CORE_USER": "wwwonly",
    "CORE_VERSION": "26.7.3",
    "CORE_WWW": "https://opnsense.org/",
    "product_abi": "26.7",
    "product_arch": "amd64",
    "product_check": {
        "api_version": "2",
        "connection": "ok",
        "downgrade_packages": [],
        "download_size": "",
        "last_check": "Mon Aug 31 09:36:22 CEST 2026",
        "needs_reboot": "1",
        "new_packages": [],
        "os_version": "FreeBSD 15.1-RELEASE-p2",
        "product_id": "opnsense",
        "product_target": "opnsense",
        "product_version": "26.7.3_8",
        "product_abi": "26.7",
        "reinstall_packages": [],
        "remove_packages": [],
        "repository": "ok",
        "upgrade_major_message": "",
        "upgrade_major_version": "",
        "upgrade_needs_reboot": "0",
        "upgrade_packages": [
            {
                "name": "base",
                "size": "97993432",
                "repository": "OPNsense",
                "current_version": "26.7.2",
                "new_version": "26.7.3"
            },
            {
                "name": "kernel",
                "size": "33187412",
                "repository": "OPNsense",
                "current_version": "26.7.2",
                "new_version": "26.7.3"
            }
        ],
        "upgrade_sets": []
    },
    "product_conflicts": "os-firewall os-firewall-devel os-wireguard os-wireguard-devel os-wireguard-go os-wireguard-go-devel",
    "product_copyright_owner": "Deciso B.V.",
    "product_copyright_url": "https://www.deciso.com/",
    "product_copyright_years": "2014-2026",
    "product_email": "project@opnsense.org",
    "product_hash": "bf16bfcda",
    "product_id": "opnsense",
    "product_latest": "26.7.3",
    "product_license": [],
    "product_log": 1,
    "product_mirror": "https://pkg.opnsense.org/FreeBSD:15:amd64/26.7",
    "product_name": "OPNsense",
    "product_nickname": "Xenial Xenops",
    "product_repos": "OPNsense (Priority: 11)",
    "product_series": "26.7",
    "product_tier": "1",
    "product_time": "Fri Aug 28 22:18:09 CEST 2026",
    "product_version": "26.7.3_8",
    "product_website": "https://opnsense.org/"
}


Change the mirror.

Try this in the terminal. If it finishes successfully reboot. Else post the output here

opnsense-update -bkr 26.7.3

Tried with multiple mirrors.
Command errors in the same was as in the upgrade message:
root@OPNsense:~ # opnsense-update -bkr 26.7.3
Fetching base-26.7.3-amd64.txz: ................................[fetch: transfer timed out
fetch: /var/cache/opnsense-update/64157/base-26.7.3-amd64.txz.sig appears to be truncated: 0/1332 bytes] failed, no signature found
root@OPNsense:~ #

Looks like you're hitting a DNS timeout here.  The file doesn't actually download.  Please fix your DNS.


Cheers,
Franco

Not a DNS issue, but close.
IPv6 bugging out was the cause. Apparently the FW itself can't speak IPv6 with the outside world anymore hence IPv6 timed out.
Clients behind the FW have no issue with IPv6. Weird.

Already tried disabling IPv6, but I missed that there was still a default fe80:: route learned via RA that caused the timeout.
After deleting that route:

Starting web GUI... done.
Fetching base-26.7.3-amd64.txz: ................. done
Fetching kernel-26.7.3-amd64.txz: ............... done
!!!!!!!!!!!!!! ATTENTION !!!!!!!!!!!!!!
! A critical upgrade is in progress. !
! Please do not turn off the system. !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Installing kernel-26.7.3-amd64.txz... done
Installing base-26.7.3-amd64.txz... done
Cleaning obsolete files... done
Please reboot.
***REBOOT***


Still confused how the FW rebooted with the last upgrade when kernel and base were missing. Don't suppose anybody feels like explaining that bit to the noob? :)
Anyway, upgrade fixed. Now of to figure out why IPv6 from the FW itself no longer works.

Much appreciated!

Well if it was using IPv6 IP it would still be a DNS issue technically.  ;)

Firewall should not reboot when these don't apply.  If you have a log that says otherwise let me know.


Cheers,
Franco

unless those logs are kept across several reboots and the final successful upgrade, i do not have any logs to share.
if they are, and you really want to investigate further, let me know where I can find them please.


Quote from: nerd on Today at 12:36:27 PMunless those logs are kept across several reboots and the final successful upgrade, i do not have any logs to share.
if they are, and you really want to investigate further, let me know where I can find them please.

The last one that reboots is held on to for a while which you can display with:

# opnsense-update -G

But I don't think that's the one you saw the faulty reboot on.

Quote from: sternchen45 on Today at 01:31:03 PMkernel and base also did not install here

Details please :)


Cheers,
Franco

I am guessing you meant lower-case g instead of uppercase G?

           -G               Return the log file of the last upgrade.  Since
                            upgrades run without network connectivity and user
                            interaction there is no direct way to observe it
                            other than an attached console or monitor which
                            can still miss important context.

           -g               Return the log file of the last update.  Update
                            logs are stored persistently when the update or
                            upgrade procedure requested a reboot.  It is also
                            stored when errors have been encountered.  This
                            can help with diagnosing update problems, package
                            conflicts and package manager bugs.


lowercase g is indeed only from when the upgrade succeeded so not useful to debug further.

Yes, sorry.  Remembered it wrong.  Wonder who made these options so confusing.  ;)


Cheers,
Franco