Jellyfin Base URL Not Working: How to Change it

Changing the Jellyfin base URL is a straightforward process that allows you to access your media server through a subdirectory rather than the root domain. This configuration is essential for reverse proxy setups where multiple services share a single IP address or domain name. By adjusting this setting, you can ensure that web clients and remote connections route traffic correctly without conflicts.

Understanding the Base URL Configuration

The base URL in Jellyfin determines the path prefix used by the web interface and API endpoints. When set to an empty string, the server listens at the root of the domain (e.g., http://example.com). Changing it to a value like /jellyfin means all requests must include that prefix (e.g., http://example.com/jellyfin). This is particularly useful when running other applications on the same server, such as a blog or wiki, which might otherwise conflict with Jellyfin's root routes. It is important to note that modifying this setting affects how the server communicates with external proxies and mobile apps. If your reverse proxy is not configured to strip the base URL prefix before sending requests to Jellyfin, the application may fail to load assets or return errors. Therefore, this change should always be paired with proper reverse proxy configuration to ensure seamless operation.

Accessing the Administration Dashboard

To begin the configuration process, you need administrative access to the Jellyfin web interface. Navigate to your Jellyfin server's address using a modern web browser. If you have not already done so, log in with an account that has administrator privileges. Once logged in, locate the user menu icon, typically found in the top-right corner of the screen. Click on this icon to reveal a dropdown menu containing various options. From the dropdown menu, select "Dashboard" or "Control Panel." This action redirects you to the main administration hub where system-wide settings are managed. The dashboard provides a centralized location for configuring network settings, library management, and user permissions. Ensure that you have a stable internet connection during this process, as any interruption could lead to configuration inconsistencies.

Navigating to General Settings

Once inside the Dashboard, look for the left-hand navigation sidebar. Click on the "General" tab to access core system configurations. This section contains fundamental settings that affect the entire Jellyfin instance. Within the General panel, scroll down until you find the "Base URL" field. It is usually located near the top of the list under the "Network" or "Web Interface" subsections, depending on your version. If you do not see the field immediately, check for expandable sections labeled "Advanced" or "Security." Some versions of Jellyfin hide sensitive network configurations behind these toggles. Make sure to click any necessary arrows or icons to reveal the hidden input fields. The Base URL field will appear as a simple text box, ready for you to enter the desired path.

Setting the New Base URL Path

Enter the new base URL into the text field provided. For example, if you want your server to be accessible via /media, type exactly that into the box. Do not include trailing slashes unless specifically required by your proxy setup; Jellyfin generally handles this automatically. Leave the field empty if you wish to revert to the root domain access. After entering the path, scroll to the bottom of the page and click the "Save" button. The system will apply the changes and may prompt you to restart the service or refresh the browser. Follow any on-screen instructions to finalize the update. If the change is successful, you will be redirected to the login page under the new path. Verify that you can still access the dashboard by navigating to the new URL manually.

Configuring Your Reverse Proxy

Changing the base URL in Jellyfin is only half the equation. You must also configure your reverse proxy (such as Nginx, Apache, or Traefik) to forward requests to the correct location. If you set the Jellyfin base URL to /jellyfin, your proxy must recognize this prefix and pass the request to the backend service. Failure to do so will result in 404 errors or broken asset loading. For Nginx users, ensure your location block matches the base URL. Use the proxy_pass directive to send traffic to the internal Jellyfin port. Remember to update any WebSocket configurations if you plan to use features like live TV or real-time notifications. These features rely on persistent connections that may break if the proxy does not handle headers correctly.

Troubleshooting Common Issues

After applying the new base URL, you might encounter issues with mobile apps or third-party clients. These applications often cache the old URL or require manual reconfiguration. Check the settings within each app to ensure they point to the new base path. If you experience intermittent connectivity, verify that your firewall rules allow traffic on the specified ports. Additionally, clear your browser cache and cookies after changing the base URL. Stale session data can cause authentication failures or redirect loops. If problems persist, consult the Jellyfin logs for detailed error messages. Look for entries related to routing or proxy headers to identify misconfigurations.

Frequently Asked Questions

Can I change the base URL while the server is running?

Yes, you can change the base URL dynamically without stopping the service. However, existing client connections may drop temporarily until they reconnect to the new path. It is best to perform this change during a maintenance window to minimize disruption for active users.

Do I need to restart Jellyfin after changing the base URL?

A full restart is not strictly necessary, but refreshing the web interface is recommended. The system applies the new routing rules immediately upon saving. Restarting ensures that all background services and cached configurations align with the new path.

How does this affect my mobile apps?

Mobile apps store the server address locally. You must manually update the server URL in the app settings to include the new base path. Failing to do so will prevent the app from connecting to your media library.

What happens if I leave the base URL empty?

An empty base URL sets the server to listen at the root of the domain. This is the default behavior and works well if no other web services are sharing the same IP address. It simplifies access but limits your ability to host multiple sites on one server.

Why am I getting 404 errors after changing the base URL?

This usually indicates a mismatch between the Jellyfin base URL and your reverse proxy configuration. Ensure that the proxy is correctly forwarding requests to the Jellyfin backend with the appropriate path prefix. Check your proxy logs for specific error details to pinpoint the issue.