Messages

You're not posting your update attempt logs here either.  I'm not sure how to help in that case other than give moral rubber duck support.  ;)


Cheers,
Franco

Hello Franco,

Apologies for the late reply. Attached is the last report I got when doing an audit on the upgrade. Not sure what to make of this. I'm just trying to figure out why the Status and Changelog page shows that I'm on the latest version but when the "Check Update" has ran the result is that Opnsense thinks I'm still on 25.7.8

Code Select Expand

Type opnsense
Version 25.7.10
Architecture amd64
Commit c2f076f30
Mirror https://mirror.sfo12.us.leaseweb.net/opnsense/FreeBSD:14:amd64/25.7
Repositories OPNsense (Priority: 11)
Updated on Fri Dec 19 17:20:40 AEST 2025
Checked on Tue Dec 30 08:22:05 AEST 2025


Code Select Expand

Version Date
25.7.10 (installed) 2025-12-18
25.7.9 2025-12-04


Code Select Expand

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 25.7.10 (amd64) at Tue Dec 30 09:00:56 AEST 2025
Fetching changelog information, please wait... fetch: transfer timed out
fetch: /usr/local/opnsense/changelog/changelog.txz appears to be truncated: 0/195380 bytes
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 928 packages processed.
All repositories are up to date.
Checking for upgrades (82 candidates): .......... done
Processing candidates (82 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.

When this finishes I see this.

Code Select Expand

Package name Current version New version Required action Repository
base 25.7.8 25.7.10 upgrade OPNsense
kernel 25.7.8 25.7.10 upgrade OPNsense


It looks like OPNSense is still in limbo to try and figure out what the latest installed version is.

```
Type    opnsense    
Version    25.7.10    
Architecture    amd64    
Commit    c2f076f30    
Mirror    http://mirror.sfo12.us.leaseweb.net/opnsense/FreeBSD:14:amd64/25.7    
Repositories    OPNsense (Priority: 11)    
Updated on    Fri Dec 19 17:20:40 AEST 2025    
Checked on    Mon Dec 22 09:27:37 AEST 2025
```

The update page again shows that I need to upgrade the base and kernel package.

```
Package name    Current version    New version    Required action    Repository
base   25.7.8   25.7.10   upgrade   OPNsense
kernel   25.7.8   25.7.10   upgrade   OPNsense
```

Something is wrong here but I can't put a finger on it where it may get the discrepancy from.

I think I may have run into an issue where Opnsense has lost it's version tracking capabilities.

The status tab shows

```
Version    25.7.9_7    
Architecture    amd64
```

But when I run the "Check for Updates" the resulting page shows

```
Package name    Current version    New version    Required action    Repository
base   25.7.5   25.7.8   upgrade   OPNsense
kernel   25.7.5   25.7.8   upgrade   OPNsense
```

Any idea what the underlying cause is and how to correct this? I don't want to click on "Update" as that would basically be downgrade from 25.7.9_7 to 25.7.8

Hello axsdenied,

Thank you for your hints. I've started again from scratch and have it working now. I guess your first tip may have resolved this issue and I have a feeling it could've been a copy&paste issue.

Anyway, issue seems to be resolved now.

Regards
Erwin

I've configured a backup schedule to have the xml stored on a Gdrive and the process itself seems to work with the exception that the xml file itself is empty.

The file is created with the name and timestamp in the correct folder but having an empty file doesn't really help..

Anyone an idea what may be causing this?

Code Select Expand

Type opnsense
Version 25.1.8_1
Architecture amd64
Commit 74f397e13
Mirror http://mirror.sfo12.us.leaseweb.net/opnsense/FreeBSD:14:amd64/25.1
Repositories OPNsense (Priority: 11)
Updated on Fri Mar 7 01:36:53 AEST 2025
Checked on N/A


I've configured a backup schedule to have the xml stored on a Gdrive and the process itself seems to work with the exception that the xml file itself is empty.

The file is created with the name and timestamp in the correct folder but having an empty file doesn't really help..

Anyone an idea what may be causing this?

Version    24.7.8    
Architecture    amd64    
Commit    9a689f238    
Mirror    http://mirror.sfo12.us.leaseweb.net/opnsense/FreeBSD:14:amd64/24.7    
Repositories    OPNsense (Priority: 11)    
Updated on    Thu Nov 7 11:37:30 AEST 2024    
Checked on    Sat Nov 16 23:22:08 AEST 2024