Qnap upnp failing

Plex Media Server Remote Access
,
1

Server Version#: 1.30.1.6562
Player Version#:

Host: QNAP TVS671, i7 cpu, 32GB DDR4. HDD x6 6TB (36TB) RAID10, 2 x M.2 SSD x 256GB Cache.
Firmware: QTS 5.0.1.2248 Build 20221215

Issue Description:
Remote Access to Plex shows ‘Not available outside your network’. External connections show as INDIRECT from Plex Client

Diagnostics:

  1. Check Internet Router: Confirm upnp enabled for device
  2. Disable then re-enable Remote access. Shows as enabled for a few seconds then returns to red status ’ Not available outside your network’
  3. Check Router logs, no entry for any request for upnp.
  4. Change physical network Interface on QNAP, same result.
  5. Check Plex Logs, find:

Thread0x7f177ee33b38

Message[Req#cec] NAT: UPnP, error mapping port 29886, error: The port mapping entry specified conflicts with a mapping assigned previously to another client, controlURL: http://192.168.178.1:49000/igdupnp/control/WANIPConn1.

If anyone has seen this and can offer any insight, it would be greatly appreciated.

2

Some modem/routers don’t clean out very well.

UPNP often means “Universal Plug and Pray” :slight_smile:

Quickest thing to do is log into the modem/router directly.
Look at all UPNP entries there.

Look for the port. If it’s the QNAP and Plex then you know your device doesn’t play well.

Delete the entry.
Consider setting up a manual port forwarding so this doesn’t happen again

3

Thanks, but this has been working fine for a long time and suddenly stopped. The error message is quite spefic. I was hoping someone will have encountered this and know the cause and solution.

4

That’s pretty much exactly what you were provided though…

Cause is in the error, there’s a mapping conflict for an existing or old entry.

The solution is to delete the entry causing the conflict and either try and get UPNP to redo it properly, or better yet set up a manual port forwarding and then you’re not relying on fallible UPNP to try and do it for you.

5

Thanks guys, turns out this has now resolved itself. I assume that a legacy entry has must have caused the conflict and has now aged-out. After the latest Plex restart it now maps the upnp fine. Just seems strange that this configuration has been running fine for years and I have never seen this error before. I will close the post. Thanks again.

6

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.