core: Cannot connect to Jellyfin

The problem

Retrying setup: Cannot connect to Jellyfin server

This is the error which shows up when I connect Jellyfin, I can put the IP in my browser and it works. Both Jellyfin and Home Assistant are working on TrueNAS Core with Tailscale on both jails. If I use the local IP, I get the same error so this isn’t specific to using Tailscale.

What version of Home Assistant Core has the issue?

2022.11.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Core

Integration causing the issue

Jellyfin

Link to integration documentation on our website

https://www.home-assistant.io/integrations/jellyfin/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: JELLYFIN.jellyfin_apiclient_python.connection_manager
Source: components/jellyfin/client_wrapper.py:67
First occurred: 5:11:50 PM (19 occurrences)
Last logged: 5:38:56 PM

    connect_to_address http://[ip address]:8096 failed



### Additional information

_No response_

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 6
Comments: 35 (9 by maintainers)

Most upvoted comments

Faced the same issue. The requests to /system/info/public were answered with a http code 400. Took a look into the sent data with wireshark and found out, that the integration sends my home-assistant instance name in the header x-emby-authorization.

My Workaround was to rename the home-assistant instance name, as i was having non-ASCII characters in the name. I named my instance after the street i am living in. And in germany it’s not that unusual to have “Straße” with our weird “ß” as part of the street name.

julianlobe on Jan 22, 2023

I was about to look at the logs on both ends to debug this issue, but suddenly it connected.

I’m running HA version 2023.3.5 in docker Jellyfin version 10.8.9 in docker, but on a different host both in host network mode.

I tried with the same values as before, with no config changes. http://my.private.ip:port without trailing slash, same user+pw as before.

And it started working.

solazs on Mar 19, 2023

I’ve submitted a PR to resolve the issue when the Home Assistant instance name contains non-ascii characters.

@rwjack, your issue is a different one (media player entities not being removed when they no longer exist). Can you open a new issue for this? @TobbeJ, your issue probably has a different cause than the issue with non-ascii characters in the Home Assistant instance name. Can you also open a new issue for this?

j-stienstra on Feb 4, 2023