Hi all. This is driving me nuts. My logs are filled with “WARN - NAT: PMP, got an error: Not Supported by gateway.”. My router doesn’t support uPNP, and I’ve got manual mappings setup, but it’s continuing to try uPNP anyway. Anyone know how to disable it?
2 Likes
in the remote access setting enter your external port you used in Manually specify public port and check the box to enable it. that tells it you are using manual port forwarding and lets plex.tv know what external port you are using.
https://support.plex.tv/hc/en-us/articles/200289506-Remote-Access
That’s how I have it setup, but the server is still trying to do uPNP based on the logs.
Same problem here.
Trying to lower SSD writes as much as I can 
The URL BigWheel posted states:
Tip!: If you manually forward a port in your router then you MUST enable this setting or else your Server will continue to try and automatically map the port and will almost certainly fail.
So I guess this is a bug.
+1 BUMP, same problem here
This has NEVER worked on either OS X or linux… manually specifying a port in PMS and a static reservation and port map on my router with upnp turned off and plex still constantly spams the logs with nat PMP not supported on the gateway BS
I even brought this up with Elan last year and of course it was never addrssed or fixed
+1 - I reinstalled PMS onto a Linux box last night, and am seeing this error in the log quite a bit:
WARN - NAT: PMP, got an error: Not Supported by gateway.
It’d be nice if PMS was smart enough to realize that anyone specifying a port manually doesn’t want UPnP attempts being made constantly. This is filling my log with useless errors. Very annoying when trying to debug other problems.
been asking for this to be fixed for YEARS…
this is still not fixed, and it’s not limited to plex running on fBSD
You would think that even a 5 year old would get that if you are specifying a port… you should not be requesting UPNP…
But I guess they were fresh out of 5 year olds
1 Like
Bump!! Still an issue - can Plex team make note of this and work on getting it fixed? My Alexa won’t work because of this 
Bump. Plex team, can you please take a look at this and fix it? Issue is on FreeBSD, Linux and OSX (and maybe more).
If you manually specify a port, Plex should stop doing UPnP requests. It’s filling the logs with useless warnings.
@BigWheel
Want to share my +1 as well: This is causing a lot of redundant logs and wasted CPU cycles…
Thats a +1 from me too. I’m running ubuntu 16.04 ( Docker Container )
me too. on windows. becuase of new virus acivity with upnp looked at router . plex had millions of ports open… i have specific ports for remote access setup for plex. please fix this
Bump … 3 years later…
Same for me.
I disabled uPNP feature in my router due obvious security issue and I still get some of these lines.
I’m running plex in a docker container.
Please fix it
Why is this still an issue in Oct 2019? A simple “if then” to disable uPNP if the user has manually specified a port is all that’s needed.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
