Jellyfin is a Free and Open Source Media System forked from Emby's 3.5.2 and ported to the .NET Core framework to enable full cross-platform support. It is slowly becoming one of the great alternatives to closed sourced solutions such as Plex, Emby, and Kodi to serve media from our slots to you via multiple apps.
For more information about this app, you may visit this link.
In this section, we will detail the initial configuration of Jellyfin. This assumes that you have the following:
We provide two pre-created folders for you to populate your content. The default names of Movies and Shows with the locations of ~/media/Movies/ and ~/media/TV Shows/, respectively.
super-embed:
<p class="callout warning"> It is not recommended to use NON SSL connections as these are far less secure then SSL, which will function in nearly all cases.
</p>
super-embed:
<p class="callout info">Client connection details explained:<br>
<b>Username</b>: The username you chose when registering your Ultra.cc account<br>
<b>Servername</b>: The name of the server your Ultra.cc service is deployed on. e.g <code>spica</code>, <code>mimas</code>, <code>yukon</code>, etc.
</p>
URL: username.servername.usbx.me
Username: Your slot's username that you entered during signup
Password: Password set for JellyFin as visible in the Control Panel.
Path: /jellyfin
Port: blank
HTTPS: Auto
URL: servername-direct.usbx.me:{jellyfin-port}/jellyfin
Example: myles-direct.usbx.me:1112/jellyfin
Servername: (e.g., myles)
URL: <https://username.servername.usbx.me/jellyfin>
Port: Leave blank
Username: Your slot's username that you entered during signup
Servername: (e.g., myles)
URL: servername-direct.usbx.me
Port: JellyFin Port Under Applications -> Jellyfin
Username: Your slot's username that you entered during signup
Servername: (e.g., myles)
super-embed:
<p class="callout warning">
Before proceeding to upgrade Jellyfin, you should backup your existing instance.
</p>
Jellyfin can be upgraded via the User Control Panel or SSH. To upgrade via SSH, please follow the below instructions.
zip -r jellyfin-backup.zip ~/.apps/jellyfin
app-jellyfin upgrade -v latest
If you are experiencing slow or buffering streams, try the following steps:
1. Run a speed test
Download one of the test files below to check the network speed between your device and the server region your service is deployed on:
If the download speed is significantly lower than expected, the issue is likely network-related between your location and the server.
2. Check disk IO utilization
High disk IO can cause degraded streaming performance. Follow the instructions in our SSH Troubleshooting Information guide to check IO utilization. If the disk IO is high and you suspect that your activities are not the cause, please submit a support ticket so we can investigate.
3. Disable transcoding and subtitle burning
Transcoding is CPU-intensive and is often the main cause of buffering, and can even cause a breach of our Fair Usage Policy. Jellyfin does not provide a single global “off” switch, so you need to combine the methods below for a true Direct Play setup.
Disable transcoding per user
Go to Dashboard > Users > select your user > disable all playback options that allow video/audio transcoding. This forces Direct Play only.
Remove quality limits
Set playback quality to Original and avoid bitrate limits. Clients request transcoding when bandwidth or quality caps are set.
Avoid subtitle burning
Image-based subtitles force full video transcoding. Use SRT subtitles or disable burn-in options.
Use compatible formats (Direct Play)
Jellyfin only transcodes when the client cannot handle the file. Using widely supported codecs and containers prevents transcoding entirely.
If transcoding is fully disabled and a file is incompatible, playback will fail instead of converting the stream.
If you are unable to access the Jellyfin WebUI and are getting a 502 error, try the following steps:
1. Restart or repair the application
The most common fix for 502 errors is to restart or repair the application, or restart the webserver. The 502 error page will tell you where the problem is and what needs to be restarted.
app-nginx uninstall
app-nginx install
app-jellyfin repair
app-jellyfin restart
2. Check if migrations.xml is empty
A known issue can occur when the migrations.xml file is empty. To check and fix this:
app-jellyfin stop
nano ~/.apps/jellyfin/migrations.xml
<?xml version="1.0" encoding="utf-8"?>
<MigrationOptions>
</MigrationOptions>
Ctrl+X to exit, Y to save, then Enter to confirm.app-jellyfin restart
3. Check disk IO utilization
High disk IO can cause degraded streaming performance. Follow the instructions in our SSH Troubleshooting Information guide to check IO utilization. If the disk IO is high and you suspect that your activities are not the cause, please submit a support ticket so we can investigate.
4. Backup and reinstall
If none of the above steps resolve the issue, you can try backing up your Jellyfin configuration and reinstalling the application. Follow our Restore Application Backup guide to create a backup before reinstalling.
If the Jellyfin WebUI is loading but is slow or unresponsive:
Check disk IO utilization
High disk IO is the most common cause of a sluggish WebUI. Follow the instructions in our SSH Troubleshooting Information guide to check IO utilization. If the disk IO is high and you suspect that your activities are not the cause, please submit a support ticket so we can investigate.