Help with Log Error - Newbie

Server Version#: 1.13.8.5395
Player Version#: Web Client 3.73.1

(Yes, I have read the faqs a couple dozen times to get this far and thank you for those!)

“NAT: UPnP, error unmapping port 12882, error: The specified value does not exist in the array.”

It’s been a fun week as I didn’t even know about NAS or Synology or Plex a couple weeks ago. Since then I splurged and I am up and running on a DS918+ with my own Domain. I obtained a Lets Encrypt Cert, set up the Port Forwarding rules, and the Firewall, and other security measures. It seems to be working fine.

I then found out about Plex versus Video Station and dived in. Took some doing and learning curve but it’s been up and for the most part stable for a few days now with only a couple issues. The biggest issue is remote access goes up and down. I eliminated most of it which was do to my manually deleting and adding files and folders to the server which was killing the Server Service PID on the NAS. It didn’t like it. As long as I delete files I already added to Plex and were scanned through Plex it is fine. Lessons learned.

But in other cases it goes down with errors like: “NAT: UPnP, error unmapping port 12882, error: The specified value does not exist in the array.” This is the Public Port that Verizon Provides mapped to the private 32400. I’m confused a little by this though and how I can manually specify this?

In the Troubleshooting Remote Access guide it states the Public Port Default is 32400 but anything between 20000 - 50000 is normal. But mine comes in at 12882. I tried changing it but that fails.

So looking for suggestions on how to stabilize this. If I address this, some clean-up on my server and folders, and figure out an issue with sharing, I’m pretty much there. (I hope!!!)

Thank you!

After I wrote this I did some more playing around. I manually set it to 32400 and it initially failed. I restarted everything and now it is working with it set at 32400. So I will monitor it and see how it goes with both public and private set there. But if anyone has suggestions it would be appreciated. Thank you.

I’m thinking perhaps either I was not clear in my question or you misunderstood. I totally understand 32400 to be the internal port at 32400 and that the error was coming from the external port. I initially tried forcing the external port but when I did it killed it. However, on the last try I forced it and restarted everything and that worked.

The document\page stated 20000 to 50000 for external which I clearly understood but what I did not understand was why my providing was why I was connecting externally with 12882 (why does a provider send that or is it arbitrary) and if I just chose say 20000 will it just work? But in my follow-up note and testing it further with 32400 (EXTERNALLY as well as INTERNALLY) it has been maintaining the remote connection.

Thank you

I am not aware of an ISP providing port forwarding automatically like that. That error is related to UPnP, which is something your router does. Basically, PMS tells your router “hey, I need a port” and your router automatically assigns one and tells PMS “here you go”. PMS then tries to use that port. So your router picked 12882, but PMS didn’t like it. Why? unknown.

Personally, I feel UPnP doesn’t work well with Plex so it’s best to use a manually specified port and not rely on UPnP.

1 Like

Thank you. That helps a great deal as to why. System has been stable since forcing it.

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