Thanks for the quick reply but this is applicable to all my devices on the local network. I’ve signed out and signed back in again and it’s the same.
If I drop off the WiFi and go to 4G then it works perfectly. Go back to WiFi on local network and it can’t find the server.
A bit stumped.
May 28, 2023 10:16:28.860 [Javascript] WARNING - DEVICE: Server connection https://192-168-194-126.1ae9433f7cca4ed8832f05d985e8b8ce.plex.direct:32400 didn't work for Diskstation: HTTP status -28
May 28, 2023 10:16:28.860 [Javascript] WARNING - DEVICE: Server connection https://118-200-48-163.1ae9433f7cca4ed8832f05d985e8b8ce.plex.direct:32400 didn't work for Diskstation: HTTP status -28
The error is a timeout, which means there’s some sort of fundamental network issue reaching it.
The connection which works on cellular is this one:
May 28, 2023 10:17:42.974 [Javascript] INFO - DEVICE: Server connection worked for Diskstation ~ https://118-200-48-163.1ae9433f7cca4ed8832f05d985e8b8ce.plex.direct:32400
So my guesses:
NAT loopback is disabled or not working on your router, which means Plexamp can’t access your server using public IP when on the LAN.
There is some sort of double NAT issue preventing Plexamp on LAN from connecting to your server.
I don’t see Plexamp trying an indirect connection, which it usually would after all other ways to connect fail. Only reason I can see for this is the cloud isn’t returning one, but I’m not sure why.
I’m not too network savvy so will need to investigate. The strange thing is that all devices on my local network are set in the 10.0.4.xx range and not 192. So why would Plexamp be looking at 192 range?. Also why does the Plex app (on the same device) not have the same issue? (Just out of curiosity).
I do have a double NAT situation and have port forwarding set up for Plex for remote access and it works great on both remote and local side. Is there a way I can force Plexamp to search 10.0.4 range to find the server?
Thanks
Btw. I appreciate your support, last time our paths crossed was back in the PHT days (which I still think is a great app)
Because that’s the address which your server is registering with the cloud at plex.tv.
It does not work great on local side, because you don’t have NAT loopback working. You should be able to access 118.200.48.163 from your LAN, and Plexamp isn’t able to.
I’m kind of curious about that myself, but I suspect that it’s finding your server via network discovery (UDP broadcast).
You can publish any address you want a device to try via the server’s “Custom server access URLs” setting. This may be a way for you to force it to try a specific address.
Thanks Elan.
I
Changed the server setting that is registered on Plex.tv (both the 192.xxx and 10.0.xx) were listed so once I selected the 10.0 one everything worked like a charm.
Thanks for the help and support. Catch you on the plexside