The outside interface that PLEX is seeing is wrong, but there isn’t a clean way to correct it. We even tried to add the correct interface into the Networking section under “Custom Server Access URL’s”. When I try enabling the remote access…it flashes green for about 5 seconds then turns red.
I get a message on the FireTV stick that it’s not “directly connected” but I’m still getting my content from the server right now, and I’m out of the country so it’s making it challenging to troubleshoot the problem. Looked thru the guides listed and nothing worked…
Remote Access is never working. When it initially goes green, Plex is trying to get remote access working. It turns red when it fails to do so.
Are you using Starlink (your log has a Starlink IP address)?
Starlink uses CG-NAT addressing, which is incompatible with Plex remote access. It places the server in a double-NAT situation.
There are workarounds. However, I’ve never found a good reference with step by step instructions on how to make it work.
The Firestick is connecting via Plex Relay. The stream is tunneled through a server at Plex. Bandwidth is limited to 2 Mbps (1 Mbps w/o a Plex Pass). If you monitor the stream via Plex Dashboard → Now Playing + Expanded View, you’ll see it is an Indirect connection.
PMS will always turn the Remote Access GREEN to indicate access when you enable it.
It then tests to see if really reachable from Plex.tv (your ports are open)
For you,
Your NAS has 3 network ports (2x 1GbE and 1x 10GbE)
In your logs, I see
– 192.168.68.x – Your home LAN ?
– 169.254.10.x – UNKNOWN but generally not a good sign.
– 169.259.9.x – UNKNOWN and also not a good sign.
In Plex.tv, I see:
– Your LAN IPs — GOOD
– Your WAN IP — Starlink (always causes problems due to double NAT)
If I look at the IPs presented, I see,
– IP address in Big “D”
– IP address located between Johnson City and San Antonio.
Questions:
How many WAN connections do you have inbound ?
Are you running a VPN?
Does any of this matter given you’re already behind a DoubleNAT due to starlink?
EDIT: Apologies. I did not see FordGuy post while I was writing.
Only a single port on the NAS is connected. Ports 2&3 don’t have anything plugged into them.
We have 2 WAN’s with a PepLink to be the traffic cop. One is commercial WiFi, and the other is StarLink.
We had a feeling the StarLink was the issue, just wasn’t sure of why. Might need to force the NAT to push the NAS traffic out the WiFi side to make it work properly.
I was running a VPN only to get into my system at the house to allow me to make changes to the settings in PLEX…but no, NOT running VPN to try and stream the server directly.
You and FordGuy have given me the answer I needed…gives us a roadmap to fix it.
ChuckPA,
My network guys say they want to put an ASA in and create a permanent VPN tunnel to our UK house.
We work while we are in the UK and need to VPN to the house anyway, so doing this allows us to be just like we are there in Texas. It’s our house in the UK and we come here 4-5x a year, and since the television programming is crap we want to watch what we already have.
The Mother-in-law is 97 this month…spending more time here in the UK to be with her and help with renovations at the house.
You’ll get more usable throughput given a fixed bandwidth.
I find WireGuard tolerates interruptions & changes better. It recovers / reconnects very quickly. I can be out, on cellular/LTE/4G, with my IP bouncing around and WireGuard never flutters as long as I have service.
As for performance: I have 235 Mbps upload. WireGuard tunnel from East Coast → West Coast US sustains 230-231 Mbps. I’m very pleased with it. When we tried other VPN protocols. the best we could manage was 30-40 Mbps.
