this post was submitted on 20 Jul 2025
8 points (78.6% liked)

Self Hosted - Self-hosting your services.

15386 readers
77 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules

Important

Cross-posting

If you see a rule-breaker please DM the mods!

founded 4 years ago
MODERATORS
 

Hello

Note that I am only interested in the technical details and I already have alternative for remote access.

As you may know Plex made some changes recently and remote access became a paid feature.

At first I thought that only people using plex.tv who will be impacted as they are using their relay feature. But I was surprised that accessing the server by its public IP is considered as a remote access (it make sense though).

So I thought that putting Plex behind a reverse proxy in the same network will solve the issue. Plex will see a local connection from the reverse proxy and treat it as a direct access. But still Plex detect that as a remote access. I even tweaked the host and headers passed by reverse proxy with no success.

Plex even consider accessing the server using a local domain as a remote access.

So I tested tailscale, I ran it on the server and tried to access Plex using the assigned IP but my access is considered a remote access. Now I ran tailscale on the client and accessing Plex from it is considered a direct access.

At first I thought Plex was checking the url but it doesn't seem to be the case.

Can someone explain me how does Plex detect remote vs local access?

you are viewing a single comment's thread
view the rest of the comments
[–] lordnikon@lemmy.world 3 points 3 weeks ago

its most likely using the ip space of the primary interface to establish the local network and any tun interfaces are scene as remote automatically.