[Solved] UPNP fatal error after upgrading to the latest version of Opnsense

Started by Cljackhammer, November 11, 2026, 04:20:23 PM

Previous topic - Next topic
Errorminiupnpd Error reading configuration file /var/etc/miniupnpd.conf
2026-11-11T10:16:53-05:00Errorminiupnpd invalid option in file /var/etc/miniupnpd.conf line 9 : friendly_name=OPNsense UPnP IGD & PCP
2026-11-11T10:15:53-05:00Errorminiupnpd Error reading configuration file /var/etc/miniupnpd.conf
2026-11-11T10:15:53-05:00Errorminiupnpd invalid option in file /var/etc/miniupnpd.conf line 9 : friendly_name=OPNsense UPnP IGD & PCP

Now the service does not start.

We're working through the sloppy submissions to the port and plugin now and hotfix as we progress.

https://www.reddit.com/r/opnsense/comments/1xtjd8f/comment/19shbpitagx35/


Cheers,
Franco

Okay. Thanks Franco. I removed the default_min_port=1024 and friendly_name=OPNsense UPnP IGD & PCP from the configuration file and the service started. I'm not sure if this will negatively impact anything. I'll wait to hear back from the Opnsense team.

I followed the instructions in the Reddit thread that Franco posted and the issue was resolved. This issue has been resolved.

Both port and plugin should be hotfixed now.  May take a bit for all mirrors to pick it up.


Cheers,
Franco

I'm actually getting a different set of errors.  Not sure if the patch addressed this:

2026-11-12T07:21:12-07:00ErrorminiupnpdFailed to broadcast good-bye notifications
2026-11-12T07:21:12-07:00ErrorminiupnpdLast message 'sendto(udp_shutdown=' repeated 10 times, suppressed by syslog-ng on xxx.xxxx.lan
2026-11-12T07:21:12-07:00Errorminiupnpdsendto(udp_shutdown=0) to [FF0E::C]: Socket operation on non-socket
2026-11-12T07:21:12-07:00ErrorminiupnpdLast message 'sendto(udp_shutdown=' repeated 10 times, suppressed by syslog-ng on xxx.xxxx.lan
2026-11-12T07:21:12-07:00Errorminiupnpdsendto(udp_shutdown=0) to [FF05::C]: Socket operation on non-socket
2026-11-12T07:21:12-07:00ErrorminiupnpdLast message 'sendto(udp_shutdown=' repeated 10 times, suppressed by syslog-ng on xxx.xxxx.lan
2026-11-12T07:21:12-07:00Errorminiupnpdsendto(udp_shutdown=0) to [FF02::C]: Socket operation on non-socket
2026-11-12T07:21:12-07:00ErrorminiupnpdLast message 'sendto(udp_shutdown=' repeated 10 times, suppressed by syslog-ng on xxx.xxxx.lan
2026-11-12T07:21:12-07:00Errorminiupnpdsendto(udp_shutdown=0) to 239.255.255.250: Socket operation on non-socket
2026-11-12T07:21:12-07:00ErrorminiupnpdPerforming STUN failed. EXITING
2026-11-12T07:21:12-07:00ErrorminiupnpdSTUN: Performing STUN failed: Device not configured
2026-11-12T07:21:12-07:00ErrorminiupnpdLast message 'STUN server not supp' repeated 3 times, suppressed by syslog-ng on xxx.xxxx.lan
2026-11-12T07:21:12-07:00ErrorminiupnpdSTUN server not supported, not returning OTHER-ADDRESS / support CHANGE-REQUEST's required for endpoint-independent (1:1) CGNAT filtering tests per RFC 5780.
2026-11-12T07:21:12-07:00Errorminiupnpdcould not open lease file: /var/run/miniupnpd.leases-ipv6
2026-11-12T07:21:12-07:00Errorminiupnpdcould not open lease file: /var/run/miniupnpd.leases

OPNsense 25.7.1_1 running on:
Dell Optiplex 3050
Intel I5-7600 @ 3.5Ghz (4 Cores)
Intel i226-V x4 Nic
8G DDR4
256G SSD

Actually removing the STUN host address fixed this issue.
OPNsense 25.7.1_1 running on:
Dell Optiplex 3050
Intel I5-7600 @ 3.5Ghz (4 Cores)
Intel i226-V x4 Nic
8G DDR4
256G SSD