26.1_4: Siproxd 1.1.0 not possible?

[notspam]

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***

[Monviech (Cedrik)]

Most likely this, required interface but no default:

https://github.com/opnsense/plugins/blob/4773ff712e97ee30bb49731c5f564ca6866a45ca/net/siproxd/src/opnsense/mvc/app/models/OPNsense/Siproxd/General.xml#L10

[Monviech (Cedrik)]

In my maintained plugins I use this code fu to avoid that migration issue:

https://github.com/opnsense/plugins/blob/4773ff712e97ee30bb49731c5f564ca6866a45ca/net/ndp-proxy-go/src/opnsense/mvc/app/models/OPNsense/NdpProxy/NdpProxy.php#L40


Best open an issue in plugins for the sipproxy maintainer

[franco]

In 26.1.1 we'll see the error in the console to fix it immediately upon report.  Something that the hunt for the interface settings migration error taught us.

FWIW, the error was probably in the plugin for a long time.


Cheers,
Franco