Messages

Please open a new thread for your issue

Sorry I figured out my issue I had to change boot to UEFI

Is there a place to download the 25.1.4 iso it ran just fine?

I'm having issues after upgrading to the 25.1.5_4 as well it updated rebooted and now just freezes at the main opnsens menu screen.

You should be able to do a backup which backs up the config information and restore it to the new hardware once you have Opnsense installed.

While I appreciate your Sarcasm.. I also thank you for the fix... I was in the middle of searching the forums after posting this.  Thank you for the help.

I'm getting the below error -
***GOT REQUEST TO UPGRADE***
Currently running OPNsense 23.7.12_5 at Tue Feb 27 09:45:01 EST 2024
Fetching packages-24.1-amd64.tar: ................................................... done
Fetching base-24.1-amd64.txz: ............ done
Fetching kernel-24.1-amd64.txz: ...... done
Extracting packages-24.1-amd64.tar... done
Extracting base-24.1-amd64.txz... done
Extracting kernel-24.1-amd64.txz... done
Please reboot.
>>> Invoking upgrade script 'squid-plugin.php'
Squid web proxy is not active. Not installing replacement plugin.
>>> Invoking upgrade script 'unbound-duckdb.py'
Traceback (most recent call last):
  File "/usr/local/opnsense/site-python/duckdb_helper.py", line 65, in __enter__
    self.connection = duckdb.connect(database=self._path, read_only=self._read_only)
duckdb.IOException: IO Error: Trying to read a database file with version number 39, but we can only read version 51.
The database file was created with DuckDB version v0.6.0 or v0.6.1.

The storage of DuckDB is not yet stable; newer versions of DuckDB cannot read old database files and vice versa.
The storage will be stabilized when version 1.0 releases.

For now, we recommend that you load the database file in a supported version of DuckDB, and use the EXPORT DATABASE command followed by IMPORT DATABASE on the current version of DuckDB.

See the storage page for more information: https://duckdb.org/internals/storage

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/etc/rc.syshook.d/upgrade/20-unbound-duckdb.py", line 41, in <module>
    if export_database('/var/unbound/data/unbound.duckdb', '/var/cache/unbound.duckdb', 'unbound', 'unbound'):
  File "/usr/local/opnsense/site-python/duckdb_helper.py", line 147, in export_database
    with DbConnection(source, read_only=True) as db:
  File "/usr/local/opnsense/site-python/duckdb_helper.py", line 75, in __enter__
    raise StorageVersionException(str(e))
duckdb_helper.StorageVersionException: IO Error: Trying to read a database file with version number 39, but we can only read version 51.
The database file was created with DuckDB version v0.6.0 or v0.6.1.

The storage of DuckDB is not yet stable; newer versions of DuckDB cannot read old database files and vice versa.
The storage will be stabilized when version 1.0 releases.

For now, we recommend that you load the database file in a supported version of DuckDB, and use the EXPORT DATABASE command followed by IMPORT DATABASE on the current version of DuckDB.

See the storage page for more information: https://duckdb.org/internals/storage
>>> Error in upgrade script '20-unbound-duckdb.py'
***DONE***

it's working fine now mine updated

I'm running  OPNsense 22.1.2_1 and noticed my GeoIP hasn't updated since 3/29/2022 so it hasn't updated in over a week.   I created a new license and set it up to verify it's not an issue with the settings, and verified by using the URL that I added to config worked. Just wanted to verify if it was just me or if maybe GeoIP hasn't made any updates as of late?  I also noticed the following in my log files but seems that has been going on for some time.

2022-04-06T11:19:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 639076)   
2022-04-05T11:18:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 639076)   
2022-04-04T11:17:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 639076)   
2022-04-03T11:16:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 639076)   
2022-04-02T11:15:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 639076)   
2022-04-01T11:14:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 639076)   
2022-03-31T11:13:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 639076)   
2022-03-30T11:12:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 639076)   
2022-03-29T11:11:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 639076)   
2022-03-28T11:10:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 906989)   
2022-03-27T11:09:03-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 906989)   
2022-03-26T11:08:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 906989)   
2022-03-25T11:07:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 906989)   
2022-03-24T11:06:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 906989)   
2022-03-23T11:05:03-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 906989)   
2022-03-22T11:04:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 906526)   
2022-03-21T11:03:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 906526)   
2022-03-20T11:02:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 906526)

@Fright that worked for me I just tested it and now my FFox is fine.

Doesn't work for me Firefox 86.0 @ Linux Debia

can you try
# opnsense-patch 4053952
?

Mine are blank in Ffox as well.

Did you turn off the Block Private network on the LAN side if it's using a private network of 172.19.0.0   Interfaces/Lan/ there is a block bogon and block private network option.  Not sure if this helps.

Not sure if it's relevant as well but it could be that you need to setup the 172 network in the Virtual IP's so that it knows it's a relevant LAN network.

change to SRC and Contains whatever ip should get what you want

I run a https://www.dell.com/us/en/business/servers/poweredge-r210/pd.aspx?refid=poweredge-r210&cs=04&s=bsd that I found on Ebay they are older servers but they run great, I'm on 1gb and I normally have about 940mb throughput

So apparently I thought it was my Velops causing it, but it's started up again, so not sure what's causing those?

Apparently this was my Linksys Velop System causing this, as it was stuck in an online/offline state.   Once I rebooted the Velop system (they are in bridge mode and only serve as WAPs) the errors cleared up.  Odd but I guess I'm not shocked lol