Recent posts

#1
General Discussion / Re: OPNsense can't update.
Last post by coffeecup25 - Today at 03:31:27 PM
Weird, but I fixed it.

I added 1.1.1.1 to Systems / Settings / General / DNS and the update ran perfectly. Prior, I had no DNS entries there, having removed them to see if Unbound was carrying the load.  It updated afterward.

To test if Unbound was working, I removed all dns sites other than my router:5353 ipconfig on windows pointed to my router.  Everything worked great for weeks like that. That made me assume Unbound was doing everything. The Adguard Home install instructions also said Unbound was doing all the work.

So, I will put my old DNS entries back on that page and let OPNsense figure out which DNS is in use at any given time. All I really care about is ad blocking.

Thanks for your help.
#2
General Discussion / Re: OPNsense can't update.
Last post by Patrick M. Hausen - Today at 03:25:11 PM
Quote from: coffeecup25 on Today at 03:19:47 PMI don't understand what you are asking.

Use the SSH program on your desktop system to get a command line login on your OPNsense firewall, then enter the command "host one.one.one.one".

You know what a command line is?
#3
General Discussion / Re: OPNsense can't update.
Last post by coffeecup25 - Today at 03:19:47 PM
Quote from: patient0 on Today at 03:16:37 PM
Quote from: coffeecup25 on Today at 03:15:05 PMDoes that answer your question?
Mmmh, can you login to OPNsense and do a "host one.one.one.one" or something similar?

I don't understand what you are asking.
#4
General Discussion / Re: OPNsense can't update.
Last post by patient0 - Today at 03:16:37 PM
Quote from: coffeecup25 on Today at 03:15:05 PMDoes that answer your question?
Mmmh, can you login to OPNsense and do a "host one.one.one.one" or something similar?
#5
General Discussion / Re: OPNsense can't update.
Last post by coffeecup25 - Today at 03:15:05 PM
Quote from: patient0 on Today at 03:07:28 PMDNS, it's always DNS ;)

Fetching changelog information, please wait... fetch: https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/sets/changelog.txz: Host does not resolveThe router can't resolve pkg.opnsense.org. Can you resolve anything else from the OPNsense?

Unbound is doing my DNS, i believe. Adguard Home works. I tried it with Adguard Home disabled - it made no difference. Does that answer your question?

A click on the pkg.opnsense.org works fine.  But not from the updater.

It can't resolve any other sites related to mirrors, either.
#6
General Discussion / Re: OPNsense can't update.
Last post by patient0 - Today at 03:07:28 PM
DNS, it's always DNS ;)

Fetching changelog information, please wait... fetch: https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/sets/changelog.txz: Host does not resolveThe router can't resolve pkg.opnsense.org. Can you resolve anything else from the OPNsense?
#7
General Discussion / OPNsense can't update.
Last post by coffeecup25 - Today at 03:04:00 PM
I can't update OPNsense. It can't find the repository. Defaults are selected. It doesn't work if I change to any other download site either.

Here's the log

-----------------------------
***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 25.7.7_4 (amd64) at Sun Dec  7 07:59:11 CST 2025
Fetching changelog information, please wait... fetch: https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/sets/changelog.txz: Host does not resolve
Updating OPNsense repository catalogue...
pkg: Repository OPNsense has a wrong packagesite, need to re-create database
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
repository OPNsense has no meta file, using default settings
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
Unable to update repository OPNsense
Updating mimugmail repository catalogue...
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
repository mimugmail has no meta file, using default settings
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
Unable to update repository mimugmail
Error updating repositories!
Upgrading package manager from version '2.3.1_1' to ''
Updating OPNsense repository catalogue...
pkg: Repository OPNsense has a wrong packagesite, need to re-create database
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
repository OPNsense has no meta file, using default settings
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
Unable to update repository OPNsense
Error updating repositories!
***DONE***
-----------------------------------------------
#8
25.7, 25.10 Series / Re: Update 25.7 -> 25.7.9 Unex...
Last post by Simon1 - Today at 01:31:46 PM
I just waited until I heard the familiar beep on reboot. Some minutes later, the webinterface was accessible again and it seems the upgrade went fine.

Will monitor my FWs behaviour but it seems to be OK.
#9
25.7, 25.10 Series / Re: 25.7.9: pkg exited on sign...
Last post by kozistan - Today at 01:22:29 PM
Thank you, Franco. I'll stay with the downgraded pkg for now since it's stable on my box and the libs are compatible.
Once a pkg/curl fix for the HTTPS bug in issue #2191 is available, I'll switch back to the current pkg version again.
#10
25.7, 25.10 Series / Re: 25.7.9: pkg exited on sign...
Last post by franco - Today at 01:09:46 PM
PS: It's this bug and nobody cares https://github.com/freebsd/pkg/issues/2191