Remote Access (4G LTE) issues with Plex app, Plexamp, and Plex Dash with TailScale VPN: Library is not being recognized

Server Version#: Latest
Player Version#: Latest

The official Plex app, Plexamp, and Plex Dash on my iPhone will not recognize my library when connected to LTE remotely using the TailScale VPN. I’m using TailScale because my ISP has CGNAT, so I can’t port forward. TailScale thus allows me to access my home network through its mesh VPN. I’ve added all the necessary devices to its network.

On TailScale, I enabled a subnet router for my Plex Media Server on my Mac. As a result, whenever I’m connected to any type of Wi-Fi signal remotely (home, work, or friends), Plex library loads fine.

The problem occurs the moment I switch to an LTE data connection: Plex doesn’t recognize the library at all. And I’m not sure what the issue is. I’ve even tried to add the TailScale VPN of my Mac running PMS in Settings > Advanced in the iOS app. But it doesn’t let me. My guess is the Plex servers try to hit the IP but can’t because my TailScale network is locked down (ie., not public).

But let me say again, I can access all my library content remotely, when connected to any type of Wi-Fi signal. The problem occurs only on LTE, remotely. And that too, with all apps.

Also, movies on the Plex app play fine remotely on LTE. Music content on the official Plex app will load (ie., the metadata loads), but the music won’t play (it just sort of hangs). The music will once again play fine on any type of Wi-Fi. Music is not recognized on Plexamp remotely on LTE. Plex Dash won’t recognize my library remotely on LTE. And I’m connected to the VPN in all these instances.

I can even enter the private IP of my Plex Server in Safari on iOS and it loads just fine (on WiFi and LTE)! It’s just the apps that are facing this issue!

I’ve attached the Plexamp logs to this thread.
Plexamp-Logs-2022-03-25-3.zip (86.5 KB)

It seems to be trying these connections:

https://192-168-12-196.4d052f8bf1a345f2a23b47ef210a25e9.plex.direct:32400
https://100-113-203-20.4d052f8bf1a345f2a23b47ef210a25e9.plex.direct:80

If those IP addresses aren’t correct, you’ll need to publish the specific one for your VPN gateway via the server settings Network > Custom server access URLs.

Those are the correct server URL’s, that’s the thing?

It’s timing out trying to connect:

Mar 25, 2022 13:46:53.658 [Javascript] WARNING - DEVICE: Server connection https://100-113-203-20.4d052f8bf1a345f2a23b47ef210a25e9.plex.direct:80 didn't work for pokkulafamily’s MacBook Pro: HTTP status -28

I see the same timeout here (probably because I’m not on the VPN?)

Yeah and I think Plex’s trying to connect to it (but it can’t, because Plex isn’t authenticated on the VPN)

Best I understood, when you have a VPN, it’s just another network interface which requests get routed to and it should Just Work.

Yeah I guess I just don’t understand what I need to add for it to work on LTE.

Because it works fine on WiFi?

If you’re on WiFi it’s presumably using the LAN address?

What IP address should I authorize in Plex for LTE access, according to the logs then?

I don’t understand the question, if you have to authorize each source address then you’ll need luck :sweat_smile: Your LTE provider probably has some sort of DHCP w/o a permanent address, and I’m not sure how to get the address on the iPhone.

Guess I’m out of luck for LTE then?

Also I’m not sure why that one IP address is trying to connect to port 80. I tried to visit that URL and nothing shows up. Is that an error on Plex’s end, because I’m not sure how that port populated– I never specified port 80 anywhere.

If I replace 80 with 32400, it connects to Plex. Could that be why?

Update: Logging into this IP address on my Mac PMS then adding it to the customer server URL (with the new port 32400) seems to allow it to work on LTE remotely. I’ll test this for a while and let you know if it continues to hold. Thanks for your help!

https://100-113-203-20.4d052f8bf1a345f2a23b47ef210a25e9.plex.direct:32400/

1 Like

Yup :laughing:

Glad you got it working!

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.