Plex lets you stream your media anywhere, on any device.
We provide support for running a full instance (as opposed to shared) of Plex Media Server on a slot via a Docker container. The server has access to all of your media and enables streaming to other devices.
Table of contents
To set up Plex Media Server on your slot, please do the following:
- Register with www.plex.tv
- Get a claim code (note: a claim code is only valid for 5 minutes)
- Copy this claim code to the file ~/private/plex.claim or ~/private/plex.claim.txt
- Wait 1 minute for the system to find the claim code and install Plex tp ~/private/plex
- Check whether the installation was a success with the presence of the file install-was-a-success in the Plex folder. If it was unsuccessful you will see a similarly named file of the form install-description-of-error
Finally, visit the URL found in ~/private/plex/web.url in your browser to use Plex. You should not put any media inside ~/private/plex as the folder is treated as disposable.
Plex will see your slot under the path /data.
Starting, stopping, updating and restarting Plex
Once installed you can use control files to make changes to Plex's running state. Deleting files in the folder ~/private/plex/control-files will result in their named action i.e., deleting "restart" will trigger a restart. Actions take one minute to be executed by the system.
If Plex is running the following SSH command will restart Plex:
Use the following SSH command to update Plex:
If Plex is running the following SSH command will stop Plex:
If Plex is stopped the following SSH command will start Plex:
Control files can also be deleted using an SFTP or FTP client meaning SSH is not necessary.
For help using the software itself you should consult Plex's own support page first of all as it's likely that your question is covered there.
In Plex, your slot data can be found under the path
Moving from a userns install to a container install
Previous installations ran under your slot's userns an environment that uses namespaces to separate users. New installations (using claim codes) run using Plex's own Docker image. The Docker image can be considered as close to a standard environment as possible which will help Plex and Feral to both diagnose issues that may arise.
The userns installation will continue to work and will be restarted if ~/private/plex/usr exists. If you run into problems with the userns set up you should uninstall and then perform a new style installation. We recommend moving to this new set up as soon as possible even if you are not having experiencing issues.
To uninstall Plex and stop using the userns, run the following SSH command:
rm -r ~/private/plex
- You see the error "Your server is signed in to Plex, but is not reachable from outside your network".
By default Plex relies on upnp for remote access. This error message (or one similar to it) will appear if there is an issue with automatic port forwarding. The solution is to make Plex aware of the manual port forwarding that is already configured.
Visit "Settings" from the link in the top-right hand side, then in the menu panel that appears on the left you will find a page called "Remote Access". Make sure "Manually specify public port" is checked and then specify the port number in your URL (for example if you saw "http://server.feralhosting.com:port/web/index.html" you would use port) and press "RETRY". You may need to press "ENABLE REMOTE ACCESS" afterwards to re-enable access again.
The SSH command below will completely remove Plex binaries and its configuration.
rm -r ~/private/plex