#Jellyfin LDAP - Connect (Success); Bind: Connect Error

1 messages · Page 1 of 1 (latest)

loud pier
#

Hi, I'm new to Authentik and as a first, I wanted to setup a connection between Authentik and my Jellyfin instance.
After some struggling the best I could manage was "Connect (Success); Bind: Connect Error.
All my services run as a container (docker). I also have a Traefik reverse proxy (also docker) working in front of everything.
From the error message I would imagine that it manages to reach Authentik on port 636 but can't go through the authentication ?

I don't really know where I could gather logs or more precise error messages.

If anyone could put me in the right direction It would be much appreciated.

hushed wadi
#

It would be nice to know whether you are using a self-signed certificate and what your setup options are. Jellyfin should provide you with logs.

Can you do a normal ldapsearch from the jellyfin machine you are trying to connect from?

loud pier
#

Thank you for your reply.
ldaps.domain.xyz gets a letsencrypt certificate through Traefik.
Same issue with ldapsearch on the host (both Jellyfin and Authentik are on the same host and the Authentik docker server as one common network with Jellyfin container, it tries for like 15 seconds then I get "ldap_result: Can't contact LDAP server (-1)" or "ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)" for ldaps.

In terms of Jellyfin logs I get those depending on if I try LDAP or LDAPs (attached)

Even though I don't see any port map when I'm checking docker container ps on the Authentik server container, I do see on my host that he's listenning on port 389 and 636. Unfortunately ping isn't installed on those images so I can't test pinging each other but I verified and they are in the same subnet so they should be able to.

📎 jellyfin_logs.txt
dim sorrel
#

Honestly that error looks like it was unable to find the ldap. This kinda looks like a routing issue. My guess would be Traefik without more details. I do want to point out that LDAP providers need an LDAP outpost.

loud pier
#

I think you might be right. I'm doing a bit of reading and I think I need to setup a middleware on Traefik for it to work.
I'll keep you posted.

dim sorrel
#

well if this is on the same host in docker. You should be able to ldapsearch the name of the docker container and bypass Traefik for now to make sure everything is working then return to it later.

loud pier
#

Same result unfortunately either with docker name or ip address.
For reference I've attached my authentik.yml config file.

📎 authentik-yml.txt
hushed wadi
#

can you ldapsearch via localhost? Normally the outpost should automatically expose the ports locally.

What does ss -tapln return on your linux host?

loud pier
#

Well the host doesn't seem like it's listening on ports 389 or 636 right now. Maybe I should explicitly expose those ports on Authentik container ?

hushed wadi
#

That would automatically happen with the outpost

#

Following the guide results in a working ldap connection