Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/chrisbenincasa/tunarr/llms.txt

Use this file to discover all available pages before exploring further.

While Tunarr is designed to work out of the box for most setups, a few common issues arise from environment differences, network configurations, or how your media client handles mixed HTTP/HTTPS connections. This page documents the most frequently reported problems and their proven solutions.
The hardware acceleration options listed on the FFmpeg Settings page are derived from the output generated by your configured ffmpeg executable. The command Tunarr uses to discover available hardware acceleration options is:
ffmpeg -hide_banner -hwaccels
If your desired hardware acceleration option (such as NVENC, VAAPI, or VideoToolbox) is not appearing in this list, there are a few common reasons. This is generally only an issue if you are running Tunarr outside of Docker, as Docker images include pre-built FFmpeg binaries with all necessary libraries already compiled in.Common causes:
  1. Wrong FFmpeg executable path — The ffmpeg binary Tunarr is configured to use may not be the same one your shell environment uses. Double-check the executable path configured in Tunarr’s settings against the one your system resolves: 
    which ffmpeg
    A concrete example of this is running on Ubuntu with both a snap-installed FFmpeg (at /snap/bin/ffmpeg) and an apt-installed FFmpeg (at /usr/bin/ffmpeg). These are different binaries and may have different compiled-in capabilities.
  2. FFmpeg not compiled with the required libraries — The ffmpeg binary you are using may not have the necessary hardware acceleration libraries compiled in. You can verify this with the same discovery command: 
    ffmpeg -hide_banner -hwaccels
    If your expected method (e.g., cuda, vaapi, videotoolbox) does not appear in the output, the binary lacks support for it regardless of what hardware is installed on your system.
If you’ve double-checked both of these things and are still experiencing missing options, open a new Q&A discussion topic on GitHub so the issue can be debugged further.
Channel icons configured in Tunarr may fail to appear in your media client — this is most commonly reported across various native Plex apps, but can potentially happen in any client.Root cause: The issue stems from not having Tunarr properly hosted via https. Plex native apps typically access Plex through Secure Server Connections. When Plex loads thumbnails and channel icons, it fetches them from your configured Tunarr host URL. If that URL uses http while the Plex app is accessed over https, many network stacks block the request as an unsafe downgrade from HTTPS to HTTP (mixed content).Workarounds:

Option 1: Host images externally over HTTPS

Upload or host the channel icon images you want to use on any externally accessible site that serves content over https. Use those https URLs as your icon sources in Tunarr.

Option 2: Put Tunarr behind HTTPS

Expose Tunarr itself via https, either through a reverse proxy (such as Nginx, Caddy, or Traefik) or a tunnel service. This makes Tunarr’s own icon URLs https-based, resolving the mixed-content issue entirely.

Option 3: Access your client over HTTP

Access the Plex client (or whichever client connects to Tunarr) via http instead of https. This avoids the mixed-content restriction. Note that this may not be possible with all Plex apps, particularly official mobile or TV apps that enforce secure connections.
Option 2 — placing Tunarr behind a reverse proxy with TLS — is the most robust long-term solution and has the added benefit of encrypting all traffic between your client and Tunarr.

Build docs developers (and LLMs) love

Get started for freeTalk to us