Server Version#: 1.32.4.7195
Player Version#: N/A
Hi - I would like to access my PMS without using the Plex Relay Service so that I can get higher quality video streams when accessing remotely. The Plex Relay Service limits my PMS bandwidth to 2000 kbps, which is just SD video.
However, when I uncheck the Network >> Enable Relay option, I never can connect remotely to my PMS.
How can I fix this?
You have to configure you’re remote access using these guides
https://support.plex.tv/articles/200289506-remote-access/
https://support.plex.tv/articles/200931138-troubleshooting-remote-access/
Look at access control issues; firewalling on your PC or connectivity device. Your router may be blocking the incoming connection, or perhaps your ISP is. I’ve got a fiber provider, and even though their standard service gives you a public IP, they use something called carrier NAT, which won’t allow an incoming connection. I have to have their static IP service to get that to work.
Best way to start would be to run a portscanner on your IP address from the outside to look at the ports you’re listening on to see if they can be reached.
@JaysPlex - Thanks for those articles. I had already done most of those configurations already, but I double-checked to be sure that everything was in place. I didn’t find anything wrong after checking my settings.
@Annoyed - I think you may be onto something there. I ran a port scanner using the Port Checker on canyouseeme.org, and neither of the two manually-configured ports I used for my two Plex Servers were visible. I don’t know if this is ISP related or not.
Another thing that’s weird with my Plex Server (Which I should have mentioned before) is that when I run the Remote Access test - with the relay service set to Enabled - is that it shows “Available” for just a couple of seconds, and then always shows “Unavailable” after that. It is available though, since I can connect Plex clients when the relay service is Enabled.
When it goes green and shows available for a few seconds that’s just Plex testing the connection. When the test is over and it fails it reverts back to red. It’s not actually working for a short time
Are you using any VPNs?
Not Plex side as remote working fine for me and my users.
Edit - to OP, assume firewall exception rules are in place ?
The link you supplied appears to be database issues on a Synology and this is a remote access problem on Windows
Remote access is almost never a Plex issue. It’s specific to you and your network or ISP
You should probably start your own thread so you can get the proper help
@JohnAlex - I checked my Windows firewall exceptions, and the various Plex applications are not blocked in any way.
@JaysPlex - Am I interpreting your response correctly that the remote availability indication going back to red is the normal operation? If so, it’s kind of odd, but that’s OK I guess.
And if that is true … Things are a little odder for me now.
My ISP is Verizon’s 5G Home Internet. I don’t use VZW’s Internet gateway module for my router, I have most of the router functionality and its WiFi totally disabled. I have my Netgear Orbi mesh network router to run my home LAN.
So I went into the VZW gateway (an ARC-XCI55AX) settings to see if I may be restricted there, and I made a few changes. I enabled the DMZ Host (“Allow a single device to be fully exposed to the Internet”) for my Netgear Orbi router. I also deleted built-in Traceroute and TFTP Port Forwarding rules that affected the Plex port range.
Now, when I have the Relay Service Disabled, the Remote Access test acts the same as when I have the Relay Service Enabled - With Relay Service Disabled, the remote accessibility indication goes green for a few seconds, and then goes back to red after that. But, I still can’t get to my Plex Media Server with the Relay Service Disabled.
Sigh.
Not sure if related to this but alot of ISPs in different countries are switching to using “CGNAT” for users that don’t require a static IP so you might have to purchase a static IP or see if you can opt-out from “CGNAT” hope that helps.
Background about CGNAT:-
Carrier-grade NAT (CGNAT, also known as large-scale NAT), is a method of sharing a single unique public IP address with multiple services to allow providers to extend their pool of usable IPv4 addresses. This means your modem or router will be assigned a private IP address instead of a unique public IP address. Our network will then translate that into a shared public address allowing you to access the Internet.
In summary if you want to host something & your ISP is using CGNAT you will either have to ask your ISP to disable CGNAT on your internet service or pay additional for a static IP.
Good luck hope this information helps hopefully you can google etc to see if your ISP has recently transitioned to using CGNAT.
Made an announcement post here to help others as thought it was useful news 
I’m sure their are exceptions but the ISP should be using IP addresses from 100.64.0.0 to 100.127.255.255 if it is CGNAT. Get you public IP from https://www.whatsmyip.org/ and compare.
The good thing about the Orbi’s is that you can put them into AP mode and still use the Mesh features in cases where there is a vendor router in between. You would then manage port forwarding in the Vendor router if available, if it’s not, well then it is time to look for a VPN that allows port forwarding.
All that being said the Verizon 5G service will probably not give consistent enough service to be reliable all the time for Plex streaming.
Thanks, @pl_5309 - My current IP address is not in that range (currently 75.xx.xx.xx), so maybe I am not dealing with CGNAT.
The VZW gateway/router does support port forwarding. Are you suggesting that I am required to do the port forwarding using the VZW router instead of my Orbi? I had thought that putting the Orbi on the DMZ was the equivalent of removing the VZW router functionality from the equation, and turning it into the equivalent of an “ISP modem” to the Orbi. I currently have all the WiFi radios turned off in the VZW gateway, and I have a dedicated wired P2P network connection (on a totally different IP range) between the VZW gateway and the Orbi’s Internet input port - Which looks similar to the connection between a cable modem to an independent router.
My Verizon 5G service is totally rock-solid, with 24/7 300+ Mbps down / 20+ Mbps up every time I have tested it, even during peak times. It helps that I am within 1/4 mile of a new VZW 5G Home Internet antenna - I can see the antenna from my house. I think I should be able to stream Plex very reliably if I can figure out how to get past this connectivity issue.
As others have mentioned, Verizon 5G uses CG-NAT addressing (as does T-Mobile & Starlink). This places you in a double-NAT scenario.
Plex remote access is not compatible with CG-NAT addressing, which is why connections are using Plex Relay.
Search on the Internet for options. Search for “Plex CG-NAT,” “CG-NAT port forwarding,” or similar terms.
Some I’ve seen listed:
Tailscale or similar VPNs. Requires a VPN on all remote clients. Search the forum for Tailscale and you’ll see how people are using it.
VPN service with port forwarding. A VPN that supports port forwarding should support Plex remote access. There’s probably several caveats, such as cost, location of tunnel exit point, how often the public address might change, etc. From reddit: List of VPNs that allow port-forwarding (2022)
Using a VPS: Bypassing a CGNAT with Wireguard
@FordGuy61 - Good suggestions!
I have a VPN that supports port forwarding, which I have enabled. I verified that the port forwarding through the VPN is working correctly by running a torrent client and then testing the port with the canyouseeme port checker. That port visibility test passed.
When I terminated the torrent client and did the canyouseeme port test with just the Plex Server running, the port check failed. The remote test did its usual thing, where it went green for a second or two, and then back to red.
Running Plex on my phone using the cell network and using Advanced >> Manual Connections with the VPN IP address and port number still wouldn’t connect to my Plex Server.
I had high hopes for this, but they were crushed. 
OK … I think I have found the fix (for me, at least).
Three of the key missing pieces appear to be these:
Once I did that, my PMS would appear available for remote access 100% of the time (no longer “green” then “red” after a few seconds).
I did set up a manually specified public port for Plex, though I don’t know how important that was.
After that, I set up a hotspot with my phone, and started streaming HD video content to a WiFi connected tablet with a constant 17 Mbps data rate. Note: I did have to limit my Remote Access Internet upload speed to 14 Mbps and Limit remote stream bitrate to 12 Mbps (1080p) or else I would end up with drop-outs and excessive buffering. With these settings, I was seeing smooth HD video playback on the devices.
Cheers!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
