Jellyseerr: Beginner’s Guide for Home Media Management

If you’re using Jellyfin, you already know it’s excellent for hosting and streaming your media collection. However, some parts can be problematic, such as managing requests. This is where Jellyseerr comes in. 

Offering ease of use and advanced features, Jellyseerr can take your media library to the next level. This guide walks you through the whats and how to ensure a seamless integration for your setup.

Table of Contents

1. What is Jellyseerr?
2. How to Install Jellyseerr
3. Jellyseerr Basic Setup Walkthrough
4. Advanced Configuration
5. Optimizing Jellyseer Performance
6. Troubleshooting Common Issues
7. Frequently Asked Questions
8. Final Thoughts

1. What is Jellyseerr?

Jellyseerr is an open-source tool that can make media requests easier for you to manage on your Jellyfin server. It works like a middleman between the media server, automation tools, and users. The main things it handles are requests, approval, and media tracking.

While it’s primarily designed for Jellyfin, Jellyseerr can work with other media servers like Plex and Emby. However, the devs have cautioned that some features may differ on other platforms.

• Customizable Request Management: Advanced features for requesting media with an easy review and approval system.
• Automation Handling: The app can trigger popular tools like Radarr, Sonarr, and Prowlarr when necessary.
• Notifications: Provides real-time updates on the status of each request. 

Also Read: 

• Jellyfin Vs Plex – Battle of the Media Managers
• The Top 7 Plex Alternatives

b. Installation Prerequisites

Before installing Jellyseerr, ensure the following:

• Media Server: Jellyfin is installed and running.
• Automation Tools: Radarr, Sonarr, and Prowlarr (for indexers).
• Database: SQLite (You can also use PostgreSQL)
• Hosting Environment: NAS / Home Server / Seedbox

2. How to Install Jellyseerr

Jellyseerr can run on all platforms that support Jellfin. While the combinations are extensive, we’ll focus primarily on those supporting Docker since it’s the most reliable way to manage the setup. 

If you’re unfamiliar with Docker, read the RapidSeedbox Beginner’s Guide to Docker.

a. Option 1: For NAS Users

Access your Docker container on your NAS and pull the Jellyseerr Image. You can do this by navigating to the “Registry” tab, searching for Jellyseer, and downloading the image.

Next, create a Container:

Go to “Container” and click “Create” to start a new Jellyseer container.

• Set the following parameters: 

Volume Mapping:

• Port Mapping:

Map a local port (e.g., 3000) to container port 3000.

• Environment Variables:

• Start the container.

Now you can access Jellyseerr by opening your browser and going to http://<NAS-IP>:3000.

Also Read: Best 8 Synology NAS for Multimedia and File Sync

b. Option 2: For Seedbox / Linux Home Servers

Ensure your seedbox supports Docker (most providers do) and use SSH to log in. Next, run the Jellyseerr container with the following:

Note: Replace /path/to/config with your seedbox storage directory.

You can now use your seedbox’s domain or IP and the port (e.g. http://<seedbox-domain>:3000) to access Jellyseerr. 

If you’re running a Windows home server, you can use this same set of commands. Only the installation process for Docker will change.

Also Read:

• Should You Use a Seedbox?
• What Does a Seedbox Do?

Try RapidSeedbox Today!

3. Jellyseerr Basic Setup Walkthrough

To fully utilize Jellyseerr, link it to your Jellyfin server. This allows Jellyseerr to manage media requests and add approved content directly to your library.

Open your browser and navigate to http://<server-ip>:3000 (or the equivalent URL for your platform). Use the default admin credentials created during setup. If prompted, create a strong password for the admin account.

Access the Settings Page:

• Once logged in, click on the settings gear icon in the Jellyseerr interface.
• Navigate to the Media Server section.

Add Jellyfin Details:

• Host/IP: Enter the IP address or domain name of your Jellyfin server (e.g., 192.168.1.100 or https://myjellyfinserver.com).
• Port: Use the default port (8096 for HTTP or 8920 for HTTPS).
• API Key: Obtain this from Jellyfin by logging into Jellyfin, going to User Settings > API Keys, and creating a new key for Jellyseerr.
• Click Save to apply the settings.

Test the Connection:

Jellyseerr provides a “Test Connection” button to confirm successful integration. Click it to verify the server is accessible.

a. Adding Radarr, Sonarr, and Prowlarr

Jellyseerr integrates with automation tools like Radarr, Sonarr, and Prowlarr to handle the download and organization of requested media. In the Jellyseerr settings, find and open the Integrations tab.

Add Radarr With the Following Details:

• Host/IP: The IP address or domain of your Radarr server (e.g., http://localhost:7878 or http://192.168.1.100:7878).
• API Key: Retrieve this from Radarr under Settings > General > Security.
• Click Save and Test Connection to ensure the setup is correct.

Add Sonarr:

Repeat the process above, but use its respective port (default: 8989) and API key from Settings > General > Security.

Add Prowlarr (Optional):

If you use Prowlarr to manage indexers, click Add Integration and select Prowlarr.

Enter the IP, port (default: 9696), and API key from Settings > General > Security in Prowlarr.

Also Read:

• Radarr Full Guide – How to Install, Use & More
• Sonarr Guide – Setup, How to Use & More
• Prowlarr Guide: How to Install, Set Up, and Use it

4. Advanced Configuration

Customize the setup to match your preferences once Jellyseerr is integrated with Jellyfin and your automation tools.

a. Set User Roles and Permissions

• Go to User Management in the settings.
• Create user accounts for individuals who will make requests or manage approvals.
• Assign roles

b. Set Default Quality Preferences

In the Integrations section, configure Radarr and Sonarr to prioritize specific qualities. For example, you can set Radarr to download movies in 4K or Sonarr to prefer HDTV-1080p releases for TV shows.

c. Enable Tags and Filtering

Use tags to organize or prioritize specific requests. For instance, assign a “Kids” tag to children’s content or “4K” for high-quality movies. It’s better to configure filters to prioritize requests with specific tags automatically.

d. Secure Your Setup (Important!)

If your server or Jellyseerr is accessible from the internet, secure it by enabling HTTPS.

Use a reverse proxy like Nginx or Traefik to handle SSL certificates and provide a custom domain (e.g., https://jellyseer.mydomain.com).

Also Read: 

• Nginx Proxy Manager: How to Setup and Use
• Traefik vs NGINX: Design and Purpose Comparison

5. Optimizing Jellyseerr Performance

Although Jellyseerr is relatively lightweight, we run it in generally low-resource environments. Because of that, it can become slow or unresponsive, crash under heavy usage, or fail to process requests efficiently.

The root cause often lies in system resource limitations or database inefficiencies. Here’s how you can optimize it to maximize performance:

a. Identify Resource Constraints

Limited CPU, RAM, or storage can cause delays or crashes. Allocate additional system resources to Jellyseerr by increasing the Docker container’s CPU and memory limits:

b. Optimize the Database

Jellyseerr uses SQLite by default, which works well for small setups but can become a bottleneck as your media library and user base grow. To mitigate this, you can migrate to PostgreSQL, which is more robust and scalable.

• Install PostgreSQL on your server or use a cloud-based PostgreSQL service.
• Update Jellyseerr’s configuration to use PostgreSQL by setting DB_TYPE=postgresql and providing connection details.
• Migrate existing data from SQLite to PostgreSQL using a migration tool or Jellyseerr’s documentation.

c. Restart the Docker Container Periodically

Over time, temporary resource usage within the Docker container can accumulate, leading to degraded performance. Address this with periodic restarts of the Jellyseerr Docker container to clear temporary resource usage:

docker restart jellyseerr

To ensure regular maintenance, you can automate this process with a cron job or Windows Task Scheduler.

d. Optimize Notifications and Updates

Frequent notifications or status updates can cause unnecessary load on the server, especially in multi-user environments.

• Reduce the frequency of status updates in Jellyseerr settings.
• Limit notifications to essential events (e.g., request approval or media addition) to avoid excessive background activity.

e. Minimize Unnecessary Plugins or Features

Running additional plugins or enabling unused features can strain Jellyseerr’s performance unnecessarily.

• Disable features or integrations that you don’t actively use.
• Audit your Jellyseerr settings and integrations to streamline the workflow.

6. Troubleshooting Common Issues

Even with a well-configured setup, you might encounter issues while using Jellyseerr. Below are common problems, their potential causes, and detailed solutions to help you resolve them effectively.

a. Jellyseerr Cannot Connect to Jellyfin

If Jellyseerr cannot connect to your Jellyfin server, you may notice that requests fail to process or media details cannot be retrieved. 

This issue is typically caused by incorrect server details entered in Jellyseerr, such as an invalid IP address, port number, or API key. Network restrictions, such as a firewall blocking communication between Jellyseerr and Jellyfin, can also be the culprit.

Possible Solutions:

• Double-check the Jellyfin IP address or domain, port (8096 for HTTP or 8920 for HTTPS), and API key in Jellyseerr’s settings.
• Regenerate the API key in Jellyfin under User Settings > API Keys if needed.
• Ensure there are no firewall rules blocking access. You can do this by testing the connection using a command like:

b. Requests Not Appearing in Radarr/Sonarr

When approved requests do not appear in Radarr or Sonarr, it’s often because of incorrect integration settings in Jellyseerr. This could include invalid URLs, wrong ports, or mismatched API keys. 

Another common cause is that the Jellyseerr server cannot reach Radarr or Sonarr due to network restrictions or misconfiguration.

Possible Solutions:

• Verify the URLs for Radarr and Sonarr in Jellyseerr settings. For example, use http://<radarr-ip>:7878 or http://<sonarr-ip>:8989.
• Confirm the API keys by retrieving them from Settings > General > Security in Radarr and Sonarr.
• Test the connection in Jellyseerr’s integrations tab to ensure everything is set up correctly.

c. Media Not Downloading

If approved requests appear in Radarr or Sonarr but downloads do not start, the issue often lies in the configuration of the download client or indexers. A misconfigured download client, such as qBittorrent or Transmission, might not be connected properly. 

Alternatively, missing or poorly configured indexers in Radarr or Sonarr could fail to find the requested content.

Possible Solutions:

• Ensure the download client is added correctly in Radarr/Sonarr with the proper IP address, port, and API key.
• Test the indexers in Radarr or Sonarr by manually searching the requested content.
• Check the logs in Radarr or Sonarr for any errors related to downloads or indexer connections.

d. Media Not Showing in Jellyfin

If downloaded content does not appear in your Jellyfin library, it is usually due to incorrect library paths or delayed library scans. The library paths in Jellyfin may not match the download location of Radarr or Sonarr, or Jellyfin may not be scanning the library frequently enough. 

Metadata mismatches can also result in content not being displayed correctly.

Possible Solutions:

• Verify that Jellyfin’s library paths are correctly configured to match the download directories used by Radarr and Sonarr.
• Manually trigger a library scan in Jellyfin by navigating to Dashboard > Libraries and selecting Scan Library Files.
• Use Jellyfin’s metadata manager to verify and update metadata for the missing media.

e. Jellyseerr Web Interface Not Loading

If you cannot access the Jellyseerr web interface, the container might not be running, or the port mapping in your Docker setup may be incorrect. This issue could also arise if a reverse proxy is misconfigured or SSL certificates are incorrectly set up for HTTPS access.

Possible Solutions:

• Check the status of the Jellyseerr Docker container using the command: 

• Restart the container if it’s stopped:

docker restart jellyseerr

• Ensure your Docker or NAS configuration maps the correct port (default: 3000).
• Verify the SSL certificate and proxy settings if you’re using HTTPS with a reverse proxy.

f. Notifications Not Working

When users don’t receive notifications about request updates, it’s often because notification settings in Jellyseerr haven’t been configured or the chosen notification service (e.g., email or push) is misconfigured. 

This can also occur if the notification service lacks proper credentials or connection settings.

Possible Solutions:

• Go to Settings > Notifications in Jellyseerr and configure the notification service (e.g., email or a push notification service).
• Test the notification system by triggering a request update.
• Check logs for errors related to the notification service configuration.

7. Frequently Asked Questions

8. Final Thoughts

If you haven’t already, now is the time to set up Jellyseerr and experience its benefits firsthand. Streamline your media management, enhance your Jellyfin experience, and keep your users happy with this ultimate media request tool.

Those new to managing a media collection should start learning to use Jellyseerr early. You won’t believe how quickly your collection can grow and get out of hand. 

Get RapidSeedbox Now!