I decided to access my server through apps.plex.tv, instead of my local IP:32400, since I was getting sick of having to try and log in 3-8 times in a row before I was allowed access. The local option is also unencrypted, and I wanted to get back into the having an encrypted connection from my local workstation browser.
Having never used the apps.plex.tv to log in before, I am not sure if this is normal.
Apps.plex.tv shows “Plex - Indirect” when looking at my settings.
Connecting to mylocalip:32400, does not show this.
Everything is working fine, and no issues with access with any clients nor any errors that anything is connecting indirectly. This is only showing up on the webpage itself.
Any input would be helpful to figure out whether or not I need to work to fix something.
“indirect” means plex.tv cannot find/see your server “directly” and needs to establish the connection through a relay server of Plex. This usually happens, if your remote access is working but has some hiccups.
Having an indirect connection also has consequences to your playback. The traffic routed through a Plex relay is limited to 1 Mbit/s (2 Mbit/s for Plex Pass users).
The encryption is more my OCD and seeing the web connection in the browser showing not protected when connecting using the IP address… Not critical obviously.
Interesting about the server somehow having to go through a relay when using the apps.plex.tv route. There is definitely no bandwidth limitations for clients streaming when I check the dashboard (300+ Mbps currently), so where would you suggest I start troubleshooting?
Port 32400 is forwarded on the firewall to the server, and I have set the manual port on the server to match.
Remote access shows the green check mark and that the server is Fully accessible outside my network.
The client literally cannot connect directly to the plex server. On a typical home network the only time you see this is if you have a wireless segment that is walled off from your wired segment. some routers do this to protect your wired devices from a roque wireless connection. In my UNIFI setup they call it a Guest network, or more specifically enable guest policies.
No guest networks are set up on the router. All devices are on the same network. The Synology box is hardwired, as well as the workstation that I am using to connect to it through the apps.plex.tv site.
Just verified that I am also not in a double-NAT situation. The routers WAN IP matches what is showing up on the IP checking websites. Verified that the port is actually being forwarded using the CanYouSeeMe.org website.
Not using Jumbo Frames, and do not use the carriers modem. I have a DD-WRT router connected directly to the fiber drop.
Your linked fix worked for the Plex issue overall. A BIG thank you to you, and the rest of the commenters here.
Apparently the latest stable build for my router using the online database doesn’t like to have the “rebind-domain-ok=/plex.direct/” line in the config if any of my hardwired network connections are plugged in for a reboot or power loss. The router just goes into a constant reboot cycle as soon as it reconnects to the internet.
I have to unplug all but the WAN cable, let it connect to the internet, then plug everything back in.
Not a Plex issue, so I will post the issue on the DD-WRT forums. Perhaps a more recent beta might fix it.
For anyone looking for more details about this hiccup, I am using the Linksys 3200acm, (now) running DD-WRT v3.0-r40559 std (08/06/19)
