Skip to content

Jellyfin app on LG webOS TV or Xbox shows error -27

TroubleshootingDeployrr v6.0+CurrentMediaTraefikAuthentication

You run Jellyfin behind Traefik with your own domain. The Jellyfin app on an LG webOS TV or an Xbox can’t connect, and you see this error:

-27

At the same time:

  • Jellyfin opens fine in a web browser on your phone or computer.
  • Jellyfin works on your local network and from outside.
  • Other Jellyfin apps connect without trouble.

The error shows up before the login page.

Traefik adds a security header called X-Frame-Options (set as SAMEORIGIN) to your apps. The LG webOS and Xbox apps don’t accept it. Browsers and most other apps do.

Deployrr sets this header in the file middlewares-secure-headers.yml. All Deployrr login chains use that file (chain-no-auth, chain-basic-auth, chain-authelia, chain-authentik, chain-oauth and chain-tinyauth), so every app behind Traefik gets the header.

To understand what this file does, watch Traefik middlewares and chains: Secure Headers middleware at 10:55 (manual Docker Compose setup; Deployrr creates the file for you).

  1. Open the file in your Docker folder:

    Terminal window
    sudo nano appdata/traefik3/rules/HOSTNAME/middlewares-secure-headers.yml

    Replace HOSTNAME with the host name of your server. It is the name of the folder inside appdata/traefik3/rules/.

  2. Find the customFrameOptionsValue line. The comment above it says Comment out customFrameOptionsValue if you're using Jellyfin on LG WebOS. Put a # in front of customFrameOptionsValue, after the spaces, so it becomes a comment:

    # customFrameOptionsValue: SAMEORIGIN
  3. Save the file.

  4. Traefik loads the change on its own, usually within seconds. If the TV still fails, restart Traefik:

    Terminal window
    sudo docker restart traefik

    With the Deployrr bash aliases: dcrestart traefik.

  5. On the TV, open the Jellyfin app and add your server again. Use your full address, for example https://jellyfin.YOUR_DOMAIN. Replace YOUR_DOMAIN with your own domain.

  6. If it still fails, try the address with https:// and without it. Also try it with :443 at the end and without it.

The TV app may get past the connection and then stop at a login step from Authelia, Authentik, TinyAuth, Google OAuth or Basic HTTP Auth. TV apps can’t show those login pages. Jellyfin has its own login, so you can switch Jellyfin to No Authentication in Traefik. For apps that can send a custom header, Auth Bypass is another way to skip the login page.

First check which chain Jellyfin uses. If Traefik was running when you installed Jellyfin, Deployrr asked you to Pick an Authentication Method and created app-jellyfin.yml in appdata/traefik3/rules/HOSTNAME/. Open that file and look for a chain name such as chain-authelia. If you skipped the question, Jellyfin uses chain-no-auth already.

To switch Jellyfin to chain-no-auth, use Security > Manage Auth (Pro license) or edit the file. Remove Authentik has the steps for both and a table of chains. Use chain-no-auth instead of the chain it suggests.

  1. Open the Jellyfin app on the TV or Xbox.
  2. Enter your server address.
  3. The app should show the Jellyfin login page, with no -27 error.