Plex Player on Android can't detect server on local network

Plex Players Mobile Devices
,
1

Server Version#: 1.41.5.9626-72009626
Player Version#: 2026.0.0 (966828661)
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

I run a Plex server on my Synology NAS. I can use all of these to connect to the server while on the local network (Google Nest WiFi, all one subnet): App on Windows, Web app on Windows, LG WebOS

When I try to connect on Android devices (phone and tablet) I get ‘No Libraries Available’ and the dropdown shows my NAS server as offline. I work in IT (server infrastructure no less) so I assumed I could work this out, but neither the existing threads no the logs have helped so far. I hope someone can either point me at a thread I’ve missed or help me debug what’s going on!

Server has secure connections set to preferred.
I’ve changed my DNS servers on the Nest Router to custom, to try and disable any DNS Rebinding protection (https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections/#toc-4)
I’ve tried lots of other things, including a full data and cache clear on Android, but I hope the below is most useful.

I’ve downloaded the logs from the Android app and it doesn’t include enough to know whether the problem is a DNS rebinding one, or that the Plex server on Synology isn’t responding to the right URL over HTTPS.

I don’t think it is a DNS problem. From the logs:
01-25 14:02:56.103 d: 01/25/2026 14:02:46:088 [pp90ziis058phx120r16ts9g] [Connections] Fetch timeout GET https://xxx-xxx-xxx-xxx-b5bf921e0b684281ab2d1e67960b2895.plex.direct:32400/media/providers 10010ms

When I ping this from my Windows machine (which is behind the same Google Nest WiFi router:
Pinging xxx-xxx-xxx-xxx.b5bf921e0b684281ab2d1e67960b2895.plex.direct [xxx.xxx.xxx.xxx] with 32 bytes of data:
Reply from xxx.xxx.xxx.xxx: bytes=32 time=1ms TTL=64

I don’t see any reason why the Android app would get a different response.

This would suggest it’s correctly trying to open the HTTPS connection to the Synology NAS IP, but if I go to that URL in Windows, I get a 401 Unauthorized.

Later on in the log it has:
01-25 14:02:56.109 e: 01/25/2026 14:02:51:666 [pp90ziis058phx120r16ts9g] Failed to check server status for (979105ae0a49af1607512038c6e01b9ba9099810): {
“type”: “[object Error]”,
“stack”: “TypeError: Network request failed\n at anonymous (address at index.android.bundle:1:702704)\n at apply (native)\n at anonymous (address at index.android.bundle:1:653770)\n at _callTimer (address at index.android.bundle:1:653054)\n at callTimers (address at index.android.bundle:1:654839)\n at apply (native)\n at __callFunction (address at index.android.bundle:1:454924)\n at anonymous (address at index.android.bundle:1:453224)\n at __guard (address at index.android.bundle:1:454180)\n at callFunctionReturnFlushedQueue (address at index.android.bundle:1:453182)”,
“name”: “TypeError”,
“message”: “Network request failed”
}:

01-25 14:02:56.109 e: 01/25/2026 14:02:51:670 [pp90ziis058phx120r16ts9g] Failed to check server status for (979105ae0a49af1607512038c6e01b9ba9099810): {
“type”: “[object Error]”,
“stack”: “TypeError: Network request failed\n at anonymous (address at index.android.bundle:1:702704)\n at apply (native)\n at anonymous (address at index.android.bundle:1:653770)\n at _callTimer (address at index.android.bundle:1:653054)\n at callTimers (address at index.android.bundle:1:654839)\n at apply (native)\n at __callFunction (address at index.android.bundle:1:454924)\n at anonymous (address at index.android.bundle:1:453224)\n at __guard (address at index.android.bundle:1:454180)\n at callFunctionReturnFlushedQueue (address at index.android.bundle:1:453182)”,
“name”: “TypeError”,
“message”: “Network request failed”
}:

which I guess could be because of the 401, or might be a different issue.

Can anyone suggest how I can get more info from the Android app? It’s quite limiting not being able to use Plex on portable devices!

2

Your issue sounds very similar to a double NAT issue, although I don’t think that is the issue.

In the Google Nest settings, set the DNS server to point to your router’s DNS server address.

Most of the time, the router DNS server will use the router’s gateway address x.x.x.1, depending on how things are configured in your router.

It’s worth a shot at least.

3

Thanks @trumpy81, I did think a DNS problem might be the cause when I was reading so many reports over the years of issues with DNS rebinding. However, if it was a DNS problem, I wouldn’t be able to resolve the address on Windows either. My PC would make a DNS request for the domain, it would get resolved as an internal IP, which would then get rejected by the router (Google Nest WiFi). Given I can resolve it, I don’t see any reason to suspect that the Android Plex app is encountering a problem. To double check, I’ve chucked a ping app on a phone and that too can resolve the domain to the local IP and ping it.

Unfortunately the DNS server suggestion also isn’t going to help. The Nest WiFi is my router. It is a FTTP service, so uses PPPoE. There is no other router to point to.

4

I was thinking that a double DNS lookup may have been the issue and causing some weird address translations or something along those lines at least.

If the Nest is your router though, then it probably does not have a double DNS issue.

The error messages you posted do suggest some sort of addressing issue though, but I am at a loss to say what that may be.

Have you tried rebooting everything, including your portable WiFi devices?

Have you made sure the Plex server is properly claimed after opening it with http://NAS-IP-ADDRESS:32400 ?