Bug #16052
closed
UPNP does not apply unless saved again on reboot
Added by Dwight Northwood 2 months ago.
Updated about 2 months ago.
Affected Architecture:
amd64
Description
Noticed my plex was being blocked on beta 25.03 as the UPNP was not working correctly.
I would go into the option for UPNP and to get it working again, click save. Then on plex I can do a retry on the connection and it now gets a port number. If pfsense is restarted, I have to click save again on UPNP.
Worked fine on the previous version.
- Status changed from New to Incomplete
Dwight Northwood wrote:
Noticed my plex was being blocked on beta 25.03 as the UPNP was not working correctly.
I would go into the option for UPNP and to get it working again, click save. Then on plex I can do a retry on the connection and it now gets a port number. If pfsense is restarted, I have to click save again on UPNP.
Worked fine on the previous version.
Hello Dwight,
Are you seeing the service not start or just it not creating the port forwards? I just tested on the latest 25.03-BETA builds and the service started on a reboot without issue.
The service is started on my system but not creating the port forwards until I click on save. Minor issue as it is an easy workaround once I realized what was happening but thought I would let you guys know.
I can't reproduce this here on the latest beta build. From a fresh boot I can immediately open a port mapping and it shows in UPnP status in the GUI and in the pf ruleset (pfSsh.php playback pfanchordrill)
A couple things to check:
- Check the Routing log for any messages from
miniupnpd -- if it logs an error it may explain there why it isn't working as expected in your environment. Compare log messages from boot with after restarting the service.
- Check the UPnP status to see if the port mapping shows up even when it doesn't appear to work -- is it there? Or is it missing?
Good evening. You can close the ticket. It seems only to happen if plex is already connected to a port like 15478 and if pfsense is rebooted, plex will report it is disconnected from the internet. If I disable remote access on plex and reboot pfsense, once pfsense is back online, plex will then get a port number once remote access is enabled.
- Status changed from Incomplete to Closed
For reference, there's also an issue with it on the current 25.03-BETA which results in the service crashing. A fix will be in the next public build.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by