Plex-ngrok

Plex-ngrok is a Docker container that tunnels a local Plex media server to a public ngrok URL and updates Plex's Custom Server Access URLs, enabling direct…

  • Cloud
  • Media Applications
  • Media Servers
  • Network Services
  • Tools & Utilities
Plex-ngrok is a Docker container that tunnels a local Plex media server to a public ngrok URL and updates Plex's Custom Server Access URLs, enabling direct remote access from any device even when the server sits behind carrier-grade or double NAT, which is useful on satellite and mobile connections.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

18/100 Low

Maintained
0GitHub repository is archived
Popular
144 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
502 GB minimum RAM

Availability: platform listings confirmed today, links checked 28 days ago

GitHub stars
4
Open issues
2
Last commit
2022-11-26
License
MIT
Activity
stale

Checked 9 days ago - source: GitHub (andriinuts/plex-ngrok-docker)

Resources & Compatibility

Minimum requirements: 2 GB RAM. ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Choose the right user IDs and first-run settings Set PLEX_UID and PLEX_GID (the user and group IDs the container runs as) to the owner of your media folders, and enter your first-run PLEX_CLAIM token plus ADVERTISE_IP if devices need to reach it by a fixed LAN address. If the IDs don't match, Plex may not be able to read your files, and if the claim or IP settings are wrong, apps can't sign in or find it. source
  • Save settings in /config and temp files in /transcode Map a host folder to /config for Plex's settings and library, and another host folder to /transcode for temporary video files. Without a persistent /config folder you can lose your setup, and without a proper /transcode location Plex's temporary files may clutter or slow down the container. source
  • Plex mainly uses port 32400 Make sure port 32400 is reachable when you need Plex to respond to web or app requests, because that is the port Plex uses for its web/API check and normal setup. If it is blocked, other devices may not be able to sign in, manage libraries, or stream from the server. source
  • Required environment variables Set NGROK_PORT to the Plex port (usually 32400), NGROK_AUTH to your Ngrok authtoken from the Ngrok dashboard, PLEX_TOKEN to your Plex auth token, PLEX_BASE_URL to your Plex server address, and NGROK_PROTOCOL to TCP; optionally expose TCP port 4040 for the Ngrok web interface. source
  • Environment variables and ports Set NGROK_PORT=32400, NGROK_AUTH, PLEX_TOKEN, PLEX_BASE_URL, and NGROK_PROTOCOL=TCP; open TCP 4040 in the Unraid ngrok web interface. source
  • Set the required environment variables and open port 4040 Set NGROK_PORT to 32400 and NGROK_PROTOCOL to TCP, provide NGROK_AUTH with your ngrok authtoken and PLEX_TOKEN with your Plex authentication token, and set PLEX_BASE_URL to your server address (for example http://192.168.0.21:32400). Open TCP port 4040 in your ngrok setup so the tunnel can reach the outside. source

Fetched 2 days ago - each note links to its source

Alternatives (12)

  • Fossorial Pangolin - Open-source identity-based remote access platform using WireGuard, offering unified management, tunneled connections, granular access contr…
  • Headscale - Headscale is an open-source, self-hosted implementation of the Tailscale control server.
  • LocaltoNet - Localtonet is a reverse-proxy tunneling service that securely exposes local HTTP, TCP, and UDP services on your network to a temporary publ…
  • NetBird - NetBird is an open-source Zero Trust networking platform that makes it easy for engineers to create fast, secure, and private networks with…
  • Seawise - Seawise is a Docker client that creates secure outbound connections to share self-hosted apps, such as Jellyfin, Plex, Immich, and Home Ass…
  • Serveo - Serveo exposes local servers to the internet using SSH tunneling.
  • Tailscale - Private networks made easy.
  • Twingate-Connector
  • WG Tunnel - This is an alternative Android Application for WireGuard and Amnezia VPN with added features.
  • ZeroTier - ZeroTier is an open-source, cross-platform virtual LAN/VPN service that connects your devices and servers into one private network, so you…
  • cloudflare-tunnel
  • sish - sish is a self-hosted SSH tunneling server that exposes local HTTP(S), WebSocket, and TCP services to the internet using standard SSH clien…

Checked 41 days ago - source: AlternativeTo

Common questions

Which variables do I need to set when running the Plex-ngrok container?

Set NGROK_PORT to the Plex port, usually 32400, NGROK_PROTOCOL to TCP, PLEX_BASE_URL to your Plex server address, and PLEX_TOKEN to your Plex authentication token. You also need NGROK_AUTH from your Ngrok account, and you can open TCP port 4040 for the Ngrok web interface.

Can it work when my home network is behind CGNAT or double NAT?

Yes, the project says it can work from behind Carrier Grade NAT or double NAT. It may also work through VPNs.

How does plex.tv reach my local Plex server after the container starts?

The container creates an Ngrok tunnel to the Plex server and uses the Plex API to update Plex's custom server access URLs with the new Ngrok URL. That lets plex.tv sign in and connect to the server through the tunnel.

Can I use a fixed custom Ngrok subdomain with it?

The underlying Ngrok image supports NGROK_SUBDOMAIN for a custom subdomain, but it requires NGROK_AUTH. The Plex-ngrok setup described here uses the random Ngrok URL instead.

Is it useful for Plex on a TV or console that cannot install a VPN app?

An Ngrok tunnel can be useful when Plex needs to run on devices that cannot install clients like Tailscale or ZeroTier. This includes TV or console scenarios where installing a VPN client is not possible.

Answers sourced from github.com, www.reddit.com

Community

Collected 48 days ago - public community threads