Messages

I think it is the right time to change the thread title to the fact what it is.
Something like "problems configuring opnsense network details".

Let us ask the crystal ball:

- From which opnsense version started to which new version was the upgrade path ?

- There was no interaction by admin ?
All rules deleted only by a firmware upgrade ?

This sounds exciting. More input would be helpful.

You should correct the thread title.
The actual title is not the real situation.
There is no way readable you described in the past with a hack concerning opnsense.
So be so serious and change the title to whatever, i was hacked or so.

Thought there were patches already ?


https://forum.opnsense.org/index.php?topic=50561.0

Ok, found a match with same problem.
https://forum.opnsense.org/index.php?topic=49123.msg249366#msg249366

Anyone here with an idea how to resolve my little problem?

After successful installation of the plugin I want to configure the q-feeds plugin.
If I insert my new API key from my account and activate "register domain feed" I got this error message while apply the config:


Error reconfiguring QFeeds connect

I couldn't find the reason, so if anyone have an idea, let me know.

After getting it to work with a lot of effort only to have it break again after not even a day when updating I consider the wlan support so broken that I am ready to give up and look for a more stable solution and use an external access point.

This is a common bad decision, using one device for everything ( many with me included have been there ), if it dies or issues, there goes the entire network.

Like Seimus recommended, I have an Asus RT-AX53U running openwrt for years now.
You set it and forget, the latest release is 24.10.5 but if you few up to some adventure, you can get snapshot or RC images.

Sorry, you must really differentiate the situation.
There is a working function now broken and need to be fixed.
This is not a question of separate functions by spreading it to different devices.
There are lots of use cases an all-in-one appliance is the right answer f.e. in small remote branches.

How can I solve the sipproxd message I get with 26.1 to 26.1_4 update?


Hooking into /etc/rc.shutdown
Starting configd.
>>> Invoking update script 'refresh.sh'
*** OPNsense\Siproxd\General migration failed from 0.0.0 to 1.1.0, check log for details
Flushing all caches...done.
Writing firmware settings: FreeBSD OPNsense SunnyValley




-----------------------------
full update log
‐-----------------------------

***GOT REQUEST TO UPDATE***
Currently running OPNsense 26.1 (amd64) at Fri Jan 30 16:22:45 UTC 2026
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
Fetching meta.conf: . done
SunnyValley repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
Fetching meta.conf: . done
SunnyValley repository is up to date.
All repositories are up to date.
Checking for upgrades (5 candidates): ..... done
Processing candidates (5 candidates): .... done
The following 3 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
   hostwatch: 1.0.9 -> 1.0.11 [OPNsense]
   opnsense: 26.1 -> 26.1_4 [OPNsense]
   os-git-backup: 1.1_2 -> 1.1_3 [OPNsense]

Number of packages to be upgraded: 3

7 MiB to be downloaded.
[1/3] Fetching hostwatch-1.0.11.pkg: .......... done
[2/3] Fetching os-git-backup-1.1_3.pkg: . done
[3/3] Fetching opnsense-26.1_4.pkg: .......... done
Checking integrity... done (0 conflicting)
[1/3] Upgrading hostwatch from 1.0.9 to 1.0.11...
===> Creating groups
Using existing group 'hostd'
===> Creating users
Using existing user 'hostd'
[1/3] Extracting hostwatch-1.0.11: ..... done
[2/3] Upgrading opnsense from 26.1 to 26.1_4...
[2/3] Extracting opnsense-26.1_4: .......... done
Stopping configd...done
Resetting root shell
Updating /etc/shells
Unhooking from /etc/rc
Unhooking from /etc/rc.shutdown
Updating /etc/shells
Registering root shell
Hooking into /etc/rc
Hooking into /etc/rc.shutdown
Starting configd.
>>> Invoking update script 'refresh.sh'
*** OPNsense\Siproxd\General migration failed from 0.0.0 to 1.1.0, check log for details
Flushing all caches...done.
Writing firmware settings: FreeBSD OPNsense SunnyValley
Writing trust files...done.
Scanning /usr/share/certs/untrusted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Scanning /usr/local/share/certs for certificates...
certctl: No changes to trust store were made.
Writing trust bundles...done.
Configuring login behaviour...done.
Configuring cron...done.
Configuring system logging...done.
[3/3] Upgrading os-git-backup from 1.1_2 to 1.1_3...
[3/3] Extracting os-git-backup-1.1_3: ..... done
Reloading plugin configuration
Flushing all caches...done.
Configuring system logging...done.
=====
Message from opnsense-26.1_4:

--
One step ahead, one step behind it, now you gotta run to get even
Checking integrity... done (0 conflicting)
Nothing to do.
Checking all packages: .......... done
The following package files will be deleted:
   /var/cache/pkg/os-git-backup-1.1_3.pkg
   /var/cache/pkg/os-git-backup-1.1_3~f195faf38f.pkg
   /var/cache/pkg/opnsense-26.1_4~37c8c2b668.pkg
   /var/cache/pkg/hostwatch-1.0.11.pkg
   /var/cache/pkg/opnsense-26.1_4.pkg
   /var/cache/pkg/hostwatch-1.0.11~c2a36a32e4.pkg
The cleanup will free 7 MiB
Deleting files: ...... done
Nothing to do.
Starting web GUI...done.
***DONE***

And what is shown in the firewall log ?

Upgrade from 26.1.rc1 to 26.1.rc2.
Need two upgrade steps and then it was done successful.
A short test shows normal functionality.

Thanks for the clarification.
Switched now to 26.1_r1 and wait for the next releases.

I know this link. There is described the process how to move to the 26.1 pre-release version.
My question concerns the way from pre-release to the final 26.1.
If there is a need to pay attention to hotfixes or something ?
If i move the repo to community the 26.1_r9 is deleted and replaced with 26.1_r1.
So the question is if i should move the repo to community back if 26.1 final is available or is there a need to manually do something ?

Dear opnsense team,

I was interested in the new firewall look and feel  migrate to 26.1.r_1 and update to 26.1.r_9.
Need to manually add firewall rules, but all fine now.

Used the following patches from the other thread:

opnsense-patch ba8194de
opnsense-patch 94081fd82f
opnsense-patch d1519593
configctl webgui restart

opnsense-patch 67668828146e80de49bc6b607db06acb12da8a61
configctl webgui restart

Repository is development.

To get 26.1 final release i will switch the repo to community and get the new 26.1 release then ? Or need I to pay attention to other things ?

Thanks for your time.

Thanks for the tip concerning health audit check.
A run get the info that all is ok.

Ok, i forced a reboot and then it works.