• 0 Posts
  • 11 Comments
Joined 2 years ago
cake
Cake day: July 9th, 2023

help-circle

  • There are two types connection in this scenario

    1. Direct - no additional cost to Plex, using the port forwarding instructions you mentioned. No limit on bandwidth - the best (and most common) option
    2. Relay - for whatever reason your client cannot reach the server (CGNAT / port forwarding not possible / firewall on client side etc), Plex will act like a man in the middle & limit the connection to 2mbit. (Yup, megaBIT).

    I switched away from Plex last year because they wouldn’t let me connect with my box in Hetzner. I’m now using Emby, ironically I’m also paying for Emby’s monthly subscription. Not because I believe I need to, but because I want the developer to continue to work on it.










  • If you use NGINX proxy manager you’ll also be able to use a FQDN with SSL for your local services without them being exposed to the internet. It means your local users won’t see the scary insecure page when they access services.

    You can even set your public dns records to have Plex.yourdomain.tld point to the local IP of NGINX - removing the need for local dns entirely. That way if you do need to access a service outside with tailscale; their subnet router feature will just work out of the box.

    Porkbun are still offering a free .dev or .app domain if you don’t already have one: https://porkbun.com/event/freeappdevdomain