"Limited Connection" & "Indirect" warning when using web app on LAN connection

General Discussions
1

I get this error when logging into https://app.plex.tv/web/app.

Limited Connection
You are not connected directly to this server so streaming quality may be limited. You may be able to connect directly by changing your home network settings. Learn More

The Learn More link goes here https://support.plex.tv/hc/en-us/articles/216766168
I don’t appear to be having the issues described on this page. Remote access appears setup correctly.

My plex server shows “Indirect” under it.

Remote Access shows “Fully accessible outside your network”

If I disable secure connections I am able to access plex (without SSL) and it works fine. Network Secure Connections is currently set to “Preferred” so the error continues.

Any ideas to resolve this issue?

I am running on Ubuntu 14.04 and Plex Version 1.0.3.2461

2

Check your Web App setting to see if unsecured connections are allowed.

Also read this support article, specifically the part on Secured Conenctions, https://support.plex.tv/hc/en-us/articles/204604227-Why-can-t-the-Plex-app-find-or-connect-to-my-Plex-Media-Server-.

3

Well. I thought that was the answer. I changed the Fallback to Insecure Connections from “Never” to “on same network” and “Always”. All three options still shows this local plex server as “indirect”.

All machines are on the same subnet.
I have signed out and in on both server and app.
When I go directly to the Plex IP:port everything seems to work fine. (not a good option)

Any other ideas?

4

Any help on this? My family continues to have the “Limited Connection” error message.

5

You will need to provide the log from the browser that gives you that message.

6

[
{
“type”: “info”,
“host”: “app.plex.tv”,
“userAgent”: “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.89 Safari/537.36”,
“browser”: {
“id”: “chrome”,
“name”: “Chrome”,
“version”: “53.0”,
“webkit”: true,
“platform”: “Windows”,
“platformID”: “windows”,
“platformVersion”: “10”,
“platformModifierKey”: “ctrl”
},
“version”: “2.8.5”,
“primaryServerUrl”: “https://..plex.direct:8443/”,
“primaryServerAuthToken”: true,
“username”: “myusername”,
“cloudUrl”: [
{
“scheme”: “https”,
“address”: “plex.tv”,
“uri”: “https://plex.tv”,
“testState”: “connected”,
“isBundled”: false,
“isFallback”: false,
“relay”: false,
“isPossiblyCrossNetworkProtected”: false,
“isUntested”: false,
“isPending”: false,
“isConnected”: true,
“isUnauthorized”: false,
“isUnavailable”: false,
“isFailed”: false,
“isAborted”: false,
“isLoopback”: false,
“isPrivate”: false,
“isHttps”: true,
“isSecure”: true,
“isPlexDirect”: false,
“currentTest”: null,
“sources”: [
{
“id”: “internal”
}
]
}
],
“cloudAccessToken”: true
}
]

7

Help. I am still fighting this problem.

8

You will need to provide the entire log from Plex Web. Also the corresponding log from PMS for the same time period.

9

Still having the problem. Should I put these logs into this ticket or should I send them another way?

10

Please start the logging, recreate the issue, then view the results. Save the entire thing as a text file and attach it here. Can you also grab the PMS logs and provide those at the same time?

11

Please see attachments.

Thanks,
Eric

I removed server logs as they appear to have too much personal information.

Is there another way to diagnose this?

12

This does not appear to be a double NAT issue as both my OnHub and my Gigapower router have the same IP.

The indirect happens even on my local network. (All machines on same subnet)

13

From your log I see you have 2 servers, but they are on different subnets.

FasterPlex at 192.168.86.254 and
DESKTOP-5MI3QV5 at 192.168.88.20

Are these servers in different locations? If so, then this is fine. If they are on the same network, you have a problem. For your server log, if you don’t want to share it publicly, you can PM them to me.

14

I just removed that server. It was in a different location.

15

Server logs have been PM’ed.

16

I’ve got an OnHub router as well and had these problems. It’s an issue with the software in the router unfortunately, regarding the way it handles NAT (there’s a thread on reddit somewhere about it). I’ve managed to get around it by setting up port forwarding on the router for my server and then setting up EACH client to have manual connections for that server (using the port forwarding settings). It was a pain, but it works now. I no longer get the message you have when using a roku client in the same house on the same network.

17

There’s a specific executable handling Plex Relay features.
(Windows) %ProgramFiles% (x86)\Plex\Plex Media Server\PlexRelay.exe
I solved this on my server by simply denying internet access to this executable. This makes indirect access impossible and everything went back to working as normal.

18

@ericlong - I looked at your log and found this.

Feb 25, 2017 22:21:31.291 [0x7f89f43ff700] DEBUG - PublicAddressManager: got WAN IP 192.168.86.166 from router
Feb 25, 2017 22:21:31.291 [0x7f89f43ff700] WARN - PublicAddressManager: WAN IP is a private IP address

Looks like the router your PMS is connected to is connected to another device that is also routing traffic. So you have what’s called a double-NAT situation. You’ll need to resolve this for remote access to work properly. You can search the forums for solutions.

1 Like
19

Short version is either set the outside router in bridge mode or manually port forward the outside router to the inside router for the plex port of 32400. Either will get the job done.

20

Just curious but could you copy and paste a simple traceroute from the client to your Plex server?