I recently setup Plex Server on Synology NAS DiskStation DS1520+.
It all works great locally but trying to get remote access is not working.
It’ll give the green check everything is great for a few second but then switch to " Not available outside your network"
I’m doing manual port forwarding to port 32400 on my netgear router.
Gave my NAS a static IP.
Checking https://canyouseeme.org/ gives me an error as well.
I disabled the firewall on the NAS, for testing, to see if that resolved the error but it didn’t.
Any help would be appreciated as I feel like I’ve hit a wall.
I’m having the same issue albeit with a slightly different scenario. I’m running my Plex Media Server on a homemade Windows machine that’s been working remotely with no issues for well over 6 months. Suddenly, two days ago, no one can access it remotely at all. I made no changes to my setup.
I’m running an ASUS RT-AC88U router. As I said, my port-forwarding has been working fine for 6 months or more, then suddenly, nothing.
My ISP is Google Fiber. As I started trying to track down the issue, I realized a latent issues that could have been causing the problem and I thought I had finally isolated the problem as a Double-NAT issue involving the Google Fiber router/modem thing and my ASUS, so I finally bypassed the Google Fiber router/modem altogether and am running directly into my ASUS now, but I’m still having the same issue: It will connect with the green "“Fully Accessible…” message, then it will just change to the “red notice”.
I have manually forwarded port 32400 in my ASUS router, and I’ve tried what seems like every combination of settings to make it accessible, but to no avail.
I have also set up my PC with a static IP on my local network, but that doesn’t seem to matter in the slightest with regards to the setup. The Plex server settings are pointed to my static IP and I currently have not specified an WAN IP address (I’m not on a static IP account with Google Fiber).
My router supports UPnP, and I have it turned on, but that doesn’t seem to matter to Plex.
I’m back up and running. I am admittedly still on a steep learning curve with all this stuff, so it really helps when someone breaks it down for me “Barney-style” like this. What’s better is that, thanks to your step-through, I could see what I was doing wrong.
I tried the steps you outlined. Set my router to port forward to 27123 even internally. Set Plex to use port 27123 in the GUI. Turned off and back on Remote Access. No luck.
Turned off remote access
Set my router to forward to port 32400 internally
Turned on remote access and still no luck.
Turned off remote access and change the port in the Plex GUI to 32400 and turned Remote access on and still no luck.
I have a request to my ISP to see if it’s something on their end that’s blocking it because I think I’m doing everything correctly but canyouseeme still isn’t able to connect.
I’ll update this as I learn more in case it helps others.
Internal port is always 32400. This port number is fixed so that all the software knows where to look to find the server.
We change the external port in the settings (which makes sense.
That green checkmark tells us that Plex.tv can talk to the server.
What’s happening is:
You enable Remote Access
PMS tells Plex.tv “use port 50001”
Plex.tv (any server in Plex’s cloud of servers) attempts to connect to your IP:port.
Where this can fail:
Your external port 50001 isn’t forwarded
Your computer has a firewall block on 32400
– and a common oversight these days —
You have Geo-IP filtering (blocking) enabled but
You didn’t make an exception rule in your firewall to ALLOW Plex’s cloud IPs to connect on port 50001. (You get the list of Plex’s IPs for your server from your log files when PMS starts “Pubsub”
There are three actual steps here
Plex.tv connect to the external port (50001) on the WAN side
Allow the internal port forwarding to transit the WAN request to the LAN side
Ultimately I had to get a static IP from the service provider as they block ports unless I have that.
Once I got that I still had to manually set a port within Plex and setup port forwarding on my router to go from that manually set port to the internal port 32400.
I’m having the same issue. My router port forwarding asks if it should be UDP or TCP or both. Which is the correct way?
I tried setting it up with TCP and on a second PC. This sometimes runs for several minutes then quits. Everything works OK on local LAN. I’m using different ports for the WAN side.
We are having a very similar situation to the original poster, so I thought I’d post here to see if anyone has any thoughts about the best way to troubleshoot our issue. We’ve setup a Plex Media Server on an iMac Pro. The remote access works fine for a few seconds each time we click the “APPLY” button in the “Remote Access” page in the Plex Media Server app, but after a few seconds, we get the “Not available outside your network” error. Similar to the original poster:
I’m doing manual port forwarding to internal port 32400 and external port 42497 on my router.
The iMac Pro has a static local IP.
Checking https://canyouseeme.org/ gives me an error as well.
The firewall on the iMac Pro lets this connection through, so the firewall shouldn’t be blocking remote access on Plex.
Something that is a little different from the original poster:
This ISP gives us an IPv6 and IPv4 public address.
When we connect the iMac Pro to another router/modem in the same house using a completely different and separate ISP and network with just an IPv4 public address, with similar port forwarding rules, the remote access feature on Plex works well consistently. So the issue only occurs when the iMac Pro is connected to one particular network and ISP.
The ISP company in question assures us that the port should be open, but that is not what we are seeing on canyouseeme.org. I’d be interested in knowing if:
There’s any situation you can think of where the port forwarding would be working correctly, but the port on canyouseeme.org registers as closed. We are using our external IPv4 for this test, and the port number that we’ve entered into the “Manually Specify Public Port” text field on the “Remote Access” page in Plex. Is there another way we could test whether the port is open, or is it a sure thing that if the port shows that it is closed on canyouseeme.org, the port forwarding is not working correctly.
There’s any other reason anyone can think of as to why the remote access on our server is not working well for this one particular ISP, but works well for the other ISP in our house. Could the fact that the ISP with the issue gives both an IPv6 and IPv4 public address have anything to do with the issue. If so, how would we resolve it?
I had the same problem. I use a fixed IP address; the issue was the IP providers Firewall on my account was corrupted and would not accept any changes in its settings . After a number of attempts to resolve the issue with tech support finally was connected to a support tech that understood the system and was able to correct the firewall issue, Remote access now works fine and is stable.
We’re looking into something like this with the “problematic” ISP as of a few days ago. After more troubleshooting and several communications with the ISP company in question, we’ve discovered that we appear to be in a “NAT” IP plan and are therefore in a “double NAT” situation with them. So if we can find a way to upgrade our type of IP plan with them to something more stable like a “Dynamic” IP plan, then this currently seems like our next best step towards resolving our Plex streaming remote access issue with this ISP.
