Comment

Comment on That's all folks, Plex is starting to charge for sharing

You can still just forward a port. Just expose the web ui port to the world, the same way Jellyfin does. That’s not recommended though, it has potential security issues. The recommended way would require a reverse proxy or tailscale. Then you’re right back to the same issues no matter the service you’re using.

source

Sort:hotnew top

EncryptKeeper@lemmy.world ⁨1⁩ ⁨week⁩ ago

You can still just forward a port. Just expose the web ui port to the world, the same way Jellyfin does.

You can if you pay. I’m not sure what about this is so difficult for you to understand.

source
- Revilo62@lemmy.world ⁨1⁩ ⁨week⁩ ago
  You can if you don’t pay. The only thing they’re blocking is traffic through their servers. If you expose the port to your local instance, they have no control over it. I’m not sure what about this is so difficult for you to understand.
  
  source
  - EncryptKeeper@lemmy.world ⁨1⁩ ⁨week⁩ ago
    
    You can if you don’t pay.
    
    No, you can’t.
    
    The only thing they’re blocking is traffic through their servers. If you expose the port to your local instance, they have no control over it.
    
    Once again, this is wrong. They are blocking traffic to your server even if you don’t go through theirs, unless you pay.
    
    You cannot do what you’re suggesting if you don’t pay.
    
    source
    Revilo62@lemmy.world ⁨1⁩ ⁨week⁩ ago
    Yes you can. If you know what you’re doing with networking, the Plex instance will have no idea whether you’re remote or not. You can make every remote user look like they’re internal to your network. Plex would have no way to stop that. They could incorporate more intense DRM, requiring things like same GPS location, but even that could likely be spoofed.
    
    source
    -> View More Comments