![]() The entered value on the configuration page will be normalized to include a leading / if this is missing. For instance, if you have a Jellyfin server at and access its main page setting a Base URL of /jellyfin will alter this main page to This can be useful if administrators want to access multiple Jellyfin instances under a single domain name, or if the Jellyfin instance lives only at a subpath to another domain with other services listening on /. In effect, it adds this URL fragment to the start of any URL path. The Base URL setting in the Networking page is an advanced setting used to specify the URL prefix that your Jellyfin instance can be accessed at. ) is supported by the Android and web clients.īase URL is known to break HDHomeRun, DLNA, Sonarr, Radarr, Chromecast, and MrMC. This is a comma separated list of IP addresses/hostnames of known proxies used when connecting to your Jellyfin instance and is required to make proper use of X-Forwarded-For headers. Known Proxies Īdd the IP address/hostname of your reverse proxy to the Known Proxies (under Admin Dashboard -> Networking). Ports 80 and 443 (pointing to the proxy server) need to be opened on your router and firewall. If you have a certificate from another source, change the SSL configuration from /etc/letsencrypt/DOMAIN_NAME/ to the location of your certificate and key. In addition, the examples are configured for use with Let's Encrypt certificates. SERVER_IP_ADDRESS: The IP address of your Jellyfin server (if the reverse proxy is on the same server use 127.0.0.1).: The domain name Jellyfin services will run under (e.g.DOMAIN_NAME: Your public domain name to access Jellyfin on (e.g.When following this guide, be sure to replace the following variables with your information. While not a reverse proxy, Let's Encrypt can be used independently or with a reverse proxy to provide SSL certificates. Some popular options for reverse proxy systems are Apache, Caddy, Haproxy, Nginx and Traefik. The nginx documentation below includes an example how to censor sensitive information from a logfile. We recommend that you either protect your logfiles or do not log full request URLs or censor sensitive data from the logfile. ![]() Jellyfin sometimes sends authentication information as part of the URL (e.g api_key parameter), so logging the full request path can expose secrets to your logfile. Self-Signed Certificate īe careful when logging requests with your reverse proxy. See monitoring for details on the monitoring endpoints that Jellyfin provides. The server will select an unused port on startup to connect to these tuner devices. Live TV devices will often use a random UDP port for HDHomeRun devices. A broadcast message to this port with Who is JellyfinServer? will get a JSON response that includes the server address, ID, and name. DLNA also uses this port and is required to be in the local subnet.Īllows clients to discover Jellyfin on the local network. Since client auto-discover would break if this option were configurable, you cannot change this in the settings at this time. This setting can also be modified from the Networking page to use a different port. You can modify this setting from the Networking page in the settings. The web frontend can be accessed here for debugging SSL certificate issues on your local network. 7359/udp is also used for auto-discovery.1900/udp is used for service auto-discovery.8920/tcp is used by default for HTTPS traffic.8096/tcp is used by default for HTTP traffic.This document aims to provide an administrator with knowledge on what ports Jellyfin binds to and what purpose they serve. Blocking 8.8.8.8 on your router is the easiest solution to this problem. In order for Chromecast to work on a non-public routable connection, 8.8.8.8 must be blocked on the Chromecast's Gateway.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |