Self-hosting Plex the easy way

Self-hosting Plex the easy way

Yulei Chen - Content-Engineerin bei sliplane.ioYulei Chen
4 min

Plex is one of the most popular media server platforms out there. It organizes your movies, TV shows, music, and photos into a beautiful interface and streams them to almost any device. While Plex offers hosted features through Plex Pass, the real power comes from running your own server where you have full control over your media library.

Sliplane is a managed container platform that makes self-hosting painless. With one-click deployment, you can get Plex up and running in minutes with no server setup, no reverse proxy config, and no infrastructure to maintain.

Prerequisites

Before deploying, ensure you have a Sliplane account (free trial available).

You will also need a Plex account and a Plex Claim Token from plex.tv/claim. This token links the server to your account. Claim tokens expire after 4 minutes, so grab one right before you deploy.

Quick start

Sliplane provides one-click deployment with presets.

SliplaneDeploy Plex >
  1. Click the deploy button above
  2. Select a project
  3. Select a server. If you just signed up you get a 48-hour free trial server
  4. Click Deploy!

About the preset

The one-click deploy above uses Sliplane's Plex preset. Here is what it includes:

  • LinuxServer.io image (linuxserver/plex) for reliable, well-maintained builds
  • Specific version tag (1.43.1.10611-1e34174b1-ls301) pinned for stability
  • Persistent storage mounted to /config for Plex database, metadata, and settings
  • PLEX_CLAIM environment variable for linking the server to your Plex account
  • PUID and PGID set to 1000 for proper file permissions
  • Timezone set to Europe/Berlin by default (configurable via TZ env var)

Next steps

Once Plex is running on Sliplane, access it using the domain Sliplane provided (e.g. plex-xxxx.sliplane.app). You should see the Plex setup wizard where you can name your server and start adding libraries.

Claim token

The PLEX_CLAIM token is only needed for the initial setup. It links the server to your Plex account. Once the server is claimed, you can remove or leave the environment variable - it won't be used again. If you missed the window (tokens expire after 4 minutes), just generate a new one at plex.tv/claim and redeploy.

Adding media

The preset includes a persistent volume mounted at /config for Plex settings and metadata. To add media files, you can:

  • Upload files to a Docker volume mounted at /data or any custom path
  • Add additional volumes in the Sliplane dashboard for /movies, /tv, /music, etc.
  • Point Plex libraries to these paths in the Plex web interface under Settings > Libraries

Environment variables

Here are the key environment variables you might want to customize:

VariableDefaultDescription
PLEX_CLAIM(empty)Claim token from plex.tv/claim (initial setup only)
TZEurope/BerlinTimezone for the container
PUID1000User ID for file permissions
PGID1000Group ID for file permissions

Logging

Plex logs are available through Sliplane's built-in log viewer. For more detailed logs, Plex stores them inside the container at /config/Library/Application Support/Plex Media Server/Logs/. For general Docker logging tips, check out our post on how to use Docker logs.

Troubleshooting

If Plex is not showing up after deployment, double-check that your claim token was valid and not expired. You can also check the logs in Sliplane's dashboard for any startup errors. Common issues include:

  • Claim token expired: Generate a new one and redeploy
  • Permission issues: Make sure PUID and PGID match the owner of your media files
  • Slow startup: Plex needs a moment to initialize its database on first boot

Cost comparison

Of course you can also self-host Plex with other cloud providers. Here is a pricing comparison for the most common ones:

ProvidervCPU CoresRAMDiskEstimated Monthly CostNotes
Sliplane22 GB40 GB€9charge per server
Render12 GB40 GB~$35–$45VM Small
Fly.io22 GB40 GB~$20–$25VM + volume
Railway22 GB40 GB~$15–$66Usage-based

FAQ

Can Plex transcode on a small server?

It depends on your media and clients. Direct play (no transcoding) works great even on low-end hardware. If your clients support the original format, you won't need much CPU at all. For occasional transcoding of 1080p content, 2 vCPU cores can handle one stream. For multiple simultaneous transcodes or 4K content, consider a larger server.

How do I configure remote access?

When running Plex on Sliplane, remote access works automatically through the HTTPS domain Sliplane provides. You don't need to configure port forwarding or a reverse proxy. Just access your server via the Sliplane domain and Plex handles the rest.

How do I update Plex?

Change the image tag in your service settings to a newer version and redeploy. Check Docker Hub for the latest stable LinuxServer Plex tag. LinuxServer tags follow the format <plex-version>-ls<revision>.

Do I need Plex Pass?

No. The free tier of Plex covers the core media server features including library management, streaming to most devices, and remote access. Plex Pass adds extras like hardware transcoding, mobile sync, and live TV/DVR support. You can always upgrade later.

How do I add subtitles?

Place .srt or .ass subtitle files next to your media files with matching names (e.g. movie.srt alongside movie.mkv). Plex will pick them up automatically. You can also enable OpenSubtitles as a subtitle source in Settings > Languages inside the Plex web interface.

Self-host Plex now - It's easy!

Sliplane gives you everything you need to run your own Plex Media Server without the server hassle.