mirror of
https://github.com/jellyfin/jellyfin.org.git
synced 2026-09-03 04:20:03 +03:00
Merge pull request #1525 from jellyfin/BotBlake-update_url
update url to full relative path
This commit is contained in:
Niels van Velzen
@@ -19,7 +19,7 @@ Make sure to restart your Jellyfin-Server to complete the plugin installation.
|
||||
DLNA is based on UPnP.
|
||||
Therefore it will make use of its **Service Discovery** (SSDP) running on Port 1900 UDP.
|
||||
Since UPnP is a standard Protocol expected to be on UDP port 1900, its not possible to configure this.
|
||||
Make sure to open this port to your local network. You will find more information about how to do this in the [Firewall guide](./#firewall--port-forwarding).
|
||||
Make sure to open this port to your local network. You will find more information about how to do this in the [Firewall guide](./index.md#firewall--port-forwarding).
|
||||
|
||||
DLNA discovery works by sending a broadcast to the current subnet and waiting for DLNA Servers to respond.
|
||||
This means that Clients will not be abled to find your server if it is not in the same subnet.
|
||||
|
||||
@@ -74,7 +74,7 @@ sudo a2enmod proxy proxy_http ssl proxy_wstunnel remoteip http2 headers
|
||||
|
||||
When connecting to server from a client application, enter `http(s)://DOMAIN_NAME/jellyfin` in the address field.
|
||||
|
||||
Set the [base URL](../#base-url) field in the Jellyfin server. This can be done by navigating to the Admin Dashboard -> Networking -> Base URL in the web client. Fill in this box with `/jellyfin` and click Save. The server will need to be restarted before this change takes effect.
|
||||
Set the [base URL](../index.md#base-url) field in the Jellyfin server. This can be done by navigating to the Admin Dashboard -> Networking -> Base URL in the web client. Fill in this box with `/jellyfin` and click Save. The server will need to be restarted before this change takes effect.
|
||||
|
||||
:::caution
|
||||
|
||||
|
||||
@@ -19,7 +19,7 @@ Important things to note when using Jellyfin behind a reverse proxy.
|
||||
|
||||
Be careful when logging requests with your reverse proxy. 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.
|
||||
We recommend that you either protect your logfiles or do not log full request URLs or censor sensitive data from the logfile.
|
||||
Our [proxy guides](./#guides) include examples on how to censor sensitive information from a logfile.
|
||||
Our [proxy guides](./index.md#guides) include examples on how to censor sensitive information from a logfile.
|
||||
|
||||
### Forwarded-For Headers
|
||||
|
||||
@@ -43,14 +43,14 @@ We recommend using [Caddy](https://caddyserver.com/) for its ease of use, especi
|
||||
|
||||
If you do not want to use Caddy, some other popular options for reverse proxy systems are [Nginx](https://www.nginx.com), [Traefik](https://traefik.io), [Haproxy](https://www.haproxy.com) and [Apache](https://httpd.apache.org). Note that these have a greater learning curve than the recommended reverse proxy Caddy. You can find respective guides here:
|
||||
|
||||
- [Nginx](./nginx)
|
||||
- [Traefik](./traefik)
|
||||
- [HAProxy](./haproxy)
|
||||
- [Apache](./apache)
|
||||
- [Nginx](./nginx.md)
|
||||
- [Traefik](./traefik.md)
|
||||
- [HAProxy](./haproxy.md)
|
||||
- [Apache](./apache.md)
|
||||
|
||||
While not a reverse proxy, Let's Encrypt can be used independently or with a reverse proxy to provide SSL certificates.
|
||||
|
||||
- [Let's Encrypt](../advanced/letsencrypt)
|
||||
- [Let's Encrypt](../9_advanced/letsencrypt.md)
|
||||
|
||||
When following these guides, be sure to replace the following variables with your information.
|
||||
|
||||
|
||||
@@ -30,4 +30,4 @@ Jellyfin can make [Prometheus](https://prometheus.io/) metrics available at `/me
|
||||
<EnableMetrics>false</EnableMetrics>
|
||||
```
|
||||
|
||||
If you have a [reverse proxy](../reverse-proxy/) configured, you can configure it to block access to the `/metrics` endpoint except for your internal network.
|
||||
If you have a [reverse proxy](../8_reverse-proxy/index.md) configured, you can configure it to block access to the `/metrics` endpoint except for your internal network.
|
||||
|
||||
@@ -116,7 +116,7 @@ There are multiple ways of exposing Jellyfin to the outside - the most common on
|
||||
- using a VPN connection to enter the Network
|
||||
- use a VPS to Reverse Proxy to your home network
|
||||
|
||||
Learn more about reverse proxies in our dedicated [Reverse Proxy guide](./reverse-proxy/).
|
||||
Learn more about reverse proxies in our dedicated [Reverse Proxy guide](./8_reverse-proxy/index.md).
|
||||
|
||||
### SSL / https
|
||||
|
||||
@@ -124,7 +124,7 @@ Using https to access the Server is recommended.
|
||||
By default, HTTPS is disabled because it requires an SSL certificate.
|
||||
|
||||
SSL Certificates are usually issued by a third party and verify that the Server and URL are assigned to another.
|
||||
Please use a trusted certificate authority such as [Let's Encrypt](./advanced/letsencrypt) when using https.
|
||||
Please use a trusted certificate authority such as [Let's Encrypt](./9_advanced/letsencrypt.md) when using https.
|
||||
|
||||
:::caution
|
||||
|
||||
@@ -132,7 +132,7 @@ Self-signed certificates pose security and compatibility issues and are strongly
|
||||
|
||||
:::
|
||||
|
||||
While Jellyfin supports HTTPS, it is strongly recommended to handle HTTPS termination separately on a reverse proxy. You can find more info on how to set this up on our [Reverse Proxy](./reverse-proxy/) page.
|
||||
While Jellyfin supports HTTPS, it is strongly recommended to handle HTTPS termination separately on a reverse proxy. You can find more info on how to set this up on our [Reverse Proxy](./8_reverse-proxy/index.md) page.
|
||||
|
||||
**It's strongly recommend that you check your SSL strength and server security at [SSLLabs](https://www.ssllabs.com/ssltest/analyze.html) if you are exposing these services to the internet.**
|
||||
|
||||
@@ -142,7 +142,7 @@ Running Jellyfin with a path (e.g. `https://example.com/jellyfin`) is supported.
|
||||
|
||||
:::caution
|
||||
|
||||
Base URL is known to break HDHomeRun, the [DLNA plugin](./dlna/), Sonarr, Radarr, and MrMC.
|
||||
Base URL is known to break HDHomeRun, the [DLNA plugin](./3_dlna.md), Sonarr, Radarr, and MrMC.
|
||||
|
||||
:::
|
||||
|
||||
|
||||
@@ -41,7 +41,7 @@ Some basic options for networking can be set on this page. For most users, it is
|
||||
|
||||
You have finished the setup wizard. Below is a list of items you should configure in order to get the best experience:
|
||||
|
||||
- [Setup remote access to use Jellyfin when you are not at home](./networking)
|
||||
- [Setup hardware acceleration to improve performance and/or save power](./transcoding/hardware-acceleration/)
|
||||
- [Setup remote access to use Jellyfin when you are not at home](./networking/index.md#external-access)
|
||||
- [Setup hardware acceleration to improve performance and/or save power](./transcoding/hardware-acceleration/index.md)
|
||||
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ title: AMD GPU
|
||||
|
||||
# HWA Tutorial On AMD GPU
|
||||
|
||||
This tutorial guides you on setting up full video hardware acceleration on AMD integrated GPU and discrete GPU via AMF or VA-API. If you are on macOS, please use [VideoToolbox](./apple) instead.
|
||||
This tutorial guides you on setting up full video hardware acceleration on AMD integrated GPU and discrete GPU via AMF or VA-API. If you are on macOS, please use [VideoToolbox](./apple.md) instead.
|
||||
|
||||
## Acceleration Methods
|
||||
|
||||
@@ -117,7 +117,7 @@ Windows 10 64-bit and newer is recommeded. **AMF is not available in Windows Doc
|
||||
|
||||
### Known Issues And Limitations On Windows
|
||||
|
||||
Please refer to [this section](./known-issues#amd-on-windows) for known issues and limitations.
|
||||
Please refer to [this section](./known-issues.md#amd-on-windows) for known issues and limitations.
|
||||
|
||||
### Configure On Windows Host
|
||||
|
||||
@@ -175,7 +175,7 @@ A 64-bit Linux distribution is required. **The supported GPU varies by kernel an
|
||||
|
||||
### Known Issues And Limitations On Linux
|
||||
|
||||
Please refer to [this section](./known-issues#amd-on-linux) for known issues and limitations.
|
||||
Please refer to [this section](./known-issues.md#amd-on-linux) for known issues and limitations.
|
||||
|
||||
### Configure On Linux Host
|
||||
|
||||
@@ -294,7 +294,7 @@ Root permission is required.
|
||||
|
||||
Linux Mint uses Ubuntu as its package base.
|
||||
|
||||
You can follow the configuration steps of [Debian And Ubuntu Linux](./amd#debian-and-ubuntu-linux) but install all Jellyfin packages `jellyfin-server`, `jellyfin-web` and `jellyfin-ffmpeg7` manually from the [Jellyfin Server Releases Page](https://repo.jellyfin.org/releases/server/). Also make sure you choose the correct codename by following the [official version maps](https://linuxmint.com/download_all.php).
|
||||
You can follow the configuration steps of [Debian And Ubuntu Linux](./amd.md#debian-and-ubuntu-linux) but install all Jellyfin packages `jellyfin-server`, `jellyfin-web` and `jellyfin-ffmpeg7` manually from the [Jellyfin Server Releases Page](https://repo.jellyfin.org/releases/server/). Also make sure you choose the correct codename by following the [official version maps](https://linuxmint.com/download_all.php).
|
||||
|
||||
#### Arch Linux
|
||||
|
||||
@@ -333,7 +333,7 @@ Root permission is required.
|
||||
sudo /usr/lib/jellyfin-ffmpeg/ffmpeg -v debug -init_hw_device drm=dr:/dev/dri/renderD128 -init_hw_device vulkan@dr
|
||||
```
|
||||
|
||||
5. Check to the remaining parts of [Debian And Ubuntu Linux](./amd#debian-and-ubuntu-linux).
|
||||
5. Check to the remaining parts of [Debian And Ubuntu Linux](./amd.md#debian-and-ubuntu-linux).
|
||||
|
||||
#### Other Distros
|
||||
|
||||
@@ -471,7 +471,7 @@ The paths of Jellyfin config and data folders in the official and LSIO Docker im
|
||||
|
||||
Other Virtualizations are not verified and may or may not work on AMD GPU.
|
||||
|
||||
Refer to the [HWA Tutorial On Intel GPU - Configure With Linux Virtualization](./intel#configure-with-linux-virtualization) for more information.
|
||||
Refer to the [HWA Tutorial On Intel GPU - Configure With Linux Virtualization](./intel.md#configure-with-linux-virtualization) for more information.
|
||||
|
||||
### Verify On Linux
|
||||
|
||||
|
||||
@@ -9,7 +9,7 @@ This tutorial guides you on setting up full video hardware acceleration on Apple
|
||||
|
||||
## Acceleration Methods
|
||||
|
||||
[VideoToolbox](https://developer.apple.com/documentation/videotoolbox) is the only available method on macOS. Please look at our guides for [Intel](./intel) or [AMD](./amd) if you have installed Windows or Linux on your Intel Mac.
|
||||
[VideoToolbox](https://developer.apple.com/documentation/videotoolbox) is the only available method on macOS. Please look at our guides for [Intel](./intel.md) or [AMD](./amd.md) if you have installed Windows or Linux on your Intel Mac.
|
||||
|
||||
To achieve full acceleration, [Metal](https://developer.apple.com/metal/) is required.
|
||||
|
||||
|
||||
@@ -101,11 +101,11 @@ See the table below to pick the best hardware acceleration method for your hardw
|
||||
|
||||
| GPU Vendor | Windows | macOS | Linux |
|
||||
| ---------- | ------------------------------------------ | -------------------------- | -------------------------------------- |
|
||||
| AMD | [AMF (Windows)](./amd#windows-setups) | [VideoToolbox](./apple.md) | [VAAPI (AMD)](./amd#linux-setups) |
|
||||
| AMD | [AMF (Windows)](./amd.md#windows-setups) | [VideoToolbox](./apple.md) | [VAAPI (AMD)](./amd.md#linux-setups) |
|
||||
| Apple | N/A | [VideoToolbox](./apple.md) | N/A |
|
||||
| Intel | [QSV (Windows)](./intel#windows-setups) | [VideoToolbox](./apple.md) | [QSV (Linux)](./intel#linux-setups) |
|
||||
| Nvidia | [NVENC (Windows)](./nvidia#windows-setups) | N/A | [NVENC (Linux)](./nvidia#linux-setups) |
|
||||
| Rockchip | N/A | N/A | [RKMPP](./rockchip) |
|
||||
| Intel | [QSV (Windows)](./intel.md#windows-setups) | [VideoToolbox](./apple.md) | [QSV (Linux)](./intel.md#linux-setups) |
|
||||
| Nvidia | [NVENC (Windows)](./nvidia.md#windows-setups) | N/A | [NVENC (Linux)](./nvidia.md#linux-setups) |
|
||||
| Rockchip | N/A | N/A | [RKMPP](./rockchip.md) |
|
||||
|
||||
## Remote Hardware Acceleration
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ title: Intel GPU
|
||||
|
||||
# HWA Tutorial On Intel GPU
|
||||
|
||||
This tutorial guides you on setting up full video hardware acceleration on Intel integrated GPUs and ARC discrete GPUs via QSV and VA-API. If you are on macOS, please use [VideoToolbox](./apple) instead.
|
||||
This tutorial guides you on setting up full video hardware acceleration on Intel integrated GPUs and ARC discrete GPUs via QSV and VA-API. If you are on macOS, please use [VideoToolbox](./apple.md) instead.
|
||||
|
||||
## Acceleration Methods
|
||||
|
||||
@@ -193,7 +193,7 @@ Intel supports OneVPL on Gen 12+ graphics (11th Gen Core and newer processor, na
|
||||
|
||||
Jellyfin server support Intel ARC **Alchemist/A-series** discrete GPU on both Windows and Linux **6.2+**. For using ARC **Battlemage/B-series** discrete GPU on Linux, kernel version **6.12+** is required. Windows is also supported, just install the GPU driver.
|
||||
|
||||
You only need to follow the [Windows Setups](./intel#windows-setups) and [Linux Setups](./intel#linux-setups) to configure and verify it.
|
||||
You only need to follow the [Windows Setups](./intel.md#windows-setups) and [Linux Setups](./intel.md#linux-setups) to configure and verify it.
|
||||
|
||||
:::tip
|
||||
|
||||
@@ -390,7 +390,7 @@ Root permission is required.
|
||||
|
||||
Linux Mint uses Ubuntu as its package base.
|
||||
|
||||
You can follow the configuration steps of [Debian And Ubuntu Linux](./intel#debian-and-ubuntu-linux) but install all Jellyfin packages `jellyfin-server`, `jellyfin-web` and `jellyfin-ffmpeg7` manually from the [Jellyfin Server Releases Page](https://repo.jellyfin.org/releases/server/). Also make sure you choose the correct codename by following the [official version maps](https://linuxmint.com/download_all.php).
|
||||
You can follow the configuration steps of [Debian And Ubuntu Linux](./intel.md#debian-and-ubuntu-linux) but install all Jellyfin packages `jellyfin-server`, `jellyfin-web` and `jellyfin-ffmpeg7` manually from the [Jellyfin Server Releases Page](https://repo.jellyfin.org/releases/server/). Also make sure you choose the correct codename by following the [official version maps](https://linuxmint.com/download_all.php).
|
||||
|
||||
#### Arch Linux
|
||||
|
||||
@@ -426,7 +426,7 @@ Root permission is required.
|
||||
sudo /usr/lib/jellyfin-ffmpeg/ffmpeg -v verbose -init_hw_device vaapi=va:/dev/dri/renderD128 -init_hw_device opencl@va
|
||||
```
|
||||
|
||||
4. Check to the remaining parts of [Debian And Ubuntu Linux](./intel#debian-and-ubuntu-linux).
|
||||
4. Check to the remaining parts of [Debian And Ubuntu Linux](./intel.md#debian-and-ubuntu-linux).
|
||||
|
||||
#### Other Distros
|
||||
|
||||
|
||||
@@ -39,7 +39,7 @@ This page lists all known issues and limitations of hardware acceleration with J
|
||||
|
||||
## Intel on Linux
|
||||
|
||||
1. Intel Gen 11 [**Jasper Lake**](https://ark.intel.com/content/www/us/en/ark/products/codename/128823/products-formerly-jasper-lake.html) and [**Elkhart Lake**](https://ark.intel.com/content/www/us/en/ark/products/codename/128825/products-formerly-elkhart-lake.html) platforms (e.g. N5095, N5105, N6005, J6412) have quirks when using video encoders on Linux. The [Low-Power Encoding](./intel#low-power-encoding) mode MUST be configured and enabled for correct VBR and CBR bitrate control that is required by Jellyfin.
|
||||
1. Intel Gen 11 [**Jasper Lake**](https://ark.intel.com/content/www/us/en/ark/products/codename/128823/products-formerly-jasper-lake.html) and [**Elkhart Lake**](https://ark.intel.com/content/www/us/en/ark/products/codename/128825/products-formerly-elkhart-lake.html) platforms (e.g. N5095, N5105, N6005, J6412) have quirks when using video encoders on Linux. The [Low-Power Encoding](./intel.md#low-power-encoding) mode MUST be configured and enabled for correct VBR and CBR bitrate control that is required by Jellyfin.
|
||||
|
||||
- Ticket: [https://gitlab.freedesktop.org/drm/intel/-/issues/8080](https://gitlab.freedesktop.org/drm/intel/-/issues/8080)
|
||||
|
||||
|
||||
@@ -15,7 +15,7 @@ On Windows and Linux **NVENC** is the only available method.
|
||||
|
||||
The NVENC/NVDEC are the proprietary video codec APIs of NVIDIA GPUs, which can be used with CUDA to achieve full hardware acceleration.
|
||||
|
||||
Please refer to [this section](./known-issues#nvidia) for known issues and limitations.
|
||||
Please refer to [this section](./known-issues.md#nvidia) for known issues and limitations.
|
||||
|
||||
:::note
|
||||
|
||||
@@ -127,7 +127,7 @@ Windows 10 64-bit and newer is recommeded. **In Jellyfin 10.10 the minimum requi
|
||||
|
||||
NVIDIA Windows driver provides access to the NVENC/NVDEC and CUDA in Windows WSL2 and Docker.
|
||||
|
||||
Refer to [Configure On Linux Host](./nvidia#configure-on-linux-host) and [Configure With Linux Virtualization](./nvidia#configure-with-linux-virtualization).
|
||||
Refer to [Configure On Linux Host](./nvidia.md#configure-on-linux-host) and [Configure With Linux Virtualization](./nvidia.md#configure-with-linux-virtualization).
|
||||
|
||||
### Verify On Windows
|
||||
|
||||
@@ -220,7 +220,7 @@ Root permission is required.
|
||||
|
||||
Linux Mint uses Ubuntu as its package base.
|
||||
|
||||
You can follow the configuration steps of [Debian and Ubuntu Linux](./nvidia#debian-and-ubuntu-linux) but install all Jellyfin packages `jellyfin-server`, `jellyfin-web` and `jellyfin-ffmpeg7` manually from the [Jellyfin Server Releases Page](https://repo.jellyfin.org/releases/server/). Also make sure you choose the correct codename by following the [official version maps](https://linuxmint.com/download_all.php).
|
||||
You can follow the configuration steps of [Debian and Ubuntu Linux](./nvidia.md#debian-and-ubuntu-linux) but install all Jellyfin packages `jellyfin-server`, `jellyfin-web` and `jellyfin-ffmpeg7` manually from the [Jellyfin Server Releases Page](https://repo.jellyfin.org/releases/server/). Also make sure you choose the correct codename by following the [official version maps](https://linuxmint.com/download_all.php).
|
||||
|
||||
#### Arch Linux
|
||||
|
||||
@@ -519,7 +519,7 @@ The paths of Jellyfin config and data folders in the official and LSIO Docker im
|
||||
|
||||
Other Virtualizations are not verified and may or may not work on NVIDIA GPU.
|
||||
|
||||
Refer to the [HWA Tutorial On Intel GPU - Configure With Linux Virtualization](./intel#configure-with-linux-virtualization) for more information.
|
||||
Refer to the [HWA Tutorial On Intel GPU - Configure With Linux Virtualization](./intel.md#configure-with-linux-virtualization) for more information.
|
||||
|
||||
### Verify On Linux
|
||||
|
||||
|
||||
@@ -15,7 +15,7 @@ The output resolution is determined by input resolution, input framerate, target
|
||||
|
||||
## Hardware Acceleration
|
||||
|
||||
If your hardware supports this you can enable [hardware acceleration](./hardware-acceleration) for much faster transcoding. Jellyfin
|
||||
If your hardware supports this you can enable [hardware acceleration](./hardware-acceleration/index.md) for much faster transcoding. Jellyfin
|
||||
supports hardware accelerated transcoding on all modern GPUs from Intel, AMD, Nvidia, Apple and Rockchip
|
||||
if the required hardware is available.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user