Remote Access - Manually specific public port bug?

server-nvidia-shield

#1

I have several Plex servers and a static IP from my ISP
2 x Shield pro, 1 x Synology, 1x Qnap, 2 x Windows 10, 1 x Drobo.
At most times the Qnap is the main PMS with a Shield and/or win10 as reserves/backups

So e.g say my PMS is 192.168.100.117 I set up port forwarding in my Asus router to 42117 > 32400
Another server Ip is 192.168.100.107 so port forwarding is 42107 > 32400

So for convenience the port is 42 + my PMS's IP last 3 digits
I might have 5 PF with this style of setup
So here is the bug

I manually put in "Manually speciify public port" to 42117 and click apply!

Connecting to Server - says in red "Not available outside your network"
Untick "Manually speciify public port" and click RETRY and a random port is next to Public 123.123.123.123- random port
Connecting to server goes to green "Fully accessible outside your network"

Ok so it is working but not with the Set PF !
But sometimes I re click apply with the manual box ticked and I get the green "Fully accessible outside your network"
i.e. with the set PF number
Other times I disable then re- enable and i get green - but not always.
This happens on ALL my servers.

I cannot find a consistent or common setup.
Some of my servers have "Manually " box ticked and other's don't.
And next time I try the opposite will work!

I cannot image i am on my own with this issue!

I guess 2 questions to the gurus here is :
Does it matter ?
Why am I port forwarding if not needed?


#2

Gurus and geeks !

No ideas??


#3

Not sure this is the same issue, but since the shield Oreo update and me having to do a total shield reset (would not re-boot and even after I removed the sd card to finally get it to reboot, PMS would no longer sartup no matter what I tried) and when I setup everything up from scratch, did PMS function again using adopted storage. Before all this, my shield PMS was working great and perfectly accessible outside the network. Not any more. I have my port forwarding set as before and the address of the shield assigned as before with the same settings and addresses. Sometimes I get green on outside accessible but it doesn’t stay that way. It’s as if the shield goes to sleep and PMS along with it.
Again, maybe different than your situation. I too have noticed what you are saying. My synology nas and Mac mini servers are perfectly accessible at all times. Not sure what I am missing here.


#4

@audiomixer said:
Not sure this is the same issue, but since the shield Oreo update and me having to do a total shield reset (would not re-boot and even after I removed the sd card to finally get it to reboot, PMS would no longer sartup no matter what I tried) and when I setup everything up from scratch, did PMS function again using adopted storage. Before all this, my shield PMS was working great and perfectly accessible outside the network. Not any more. I have my port forwarding set as before and the address of the shield assigned as before with the same settings and addresses. Sometimes I get green on outside accessible but it doesn’t stay that way. It’s as if the shield goes to sleep and PMS along with it.
Again, maybe different than your situation. I too have noticed what you are saying. My synology nas and Mac mini servers are perfectly accessible at all times. Not sure what I am missing here.

One thing I have not tried but i think was an issue in the past.
That being - even though the light goes red it is still available remotely!!
Worth checking !


#5

So far when it’s red then it is not accessible from outside at all. What I did do was to go into my asus router and remove the port forwarding for the shield and allow PMS to handle via UPnP. My mini and Synology NAS has port forwarding set manually and they work fine as well. So far it is working perfectly. Time will tell. Also the latest version of PMS just released seems to be working fine with metadata for TV shows and adopted storage is also working well with PMS.