LLDAP•6mo ago

HackinDoge - Anyone successfully using LLDAP wi...

Anyone successfully using LLDAP with Jellyfin? I cannot for the life of me get it to work

[16:14:36] [WRN] [44] Jellyfin.Plugin.LDAP_Auth.LdapAuthenticationProviderPlugin: Ldap Test Failed to Connect or Bind to server
2025-06-25 16:14:36.887558+00:00LdapException: Unable to connect to server lldap:3890 (91) Connect Error
2025-06-25 16:14:36.887585+00:00System.Net.Sockets.SocketException (111): Connection refused
2025-06-25 16:14:36.887604+00:00at Novell.Directory.Ldap.AsyncExtensions.WaitAndUnwrap(Task task, Int32 timeout)
2025-06-25 16:14:36.887687+00:00at Novell.Directory.Ldap.Connection.Connect(String host, Int32 port, Int32 semaphoreId)

[16:14:36] [WRN] [44] Jellyfin.Plugin.LDAP_Auth.LdapAuthenticationProviderPlugin: Ldap Test Failed to Connect or Bind to server
2025-06-25 16:14:36.887558+00:00LdapException: Unable to connect to server lldap:3890 (91) Connect Error
2025-06-25 16:14:36.887585+00:00System.Net.Sockets.SocketException (111): Connection refused
2025-06-25 16:14:36.887604+00:00at Novell.Directory.Ldap.AsyncExtensions.WaitAndUnwrap(Task task, Int32 timeout)
2025-06-25 16:14:36.887687+00:00at Novell.Directory.Ldap.Connection.Connect(String host, Int32 port, Int32 semaphoreId)

[16:14:36] [WRN] [44] Jellyfin.Plugin.LDAP_Auth.LdapAuthenticationProviderPlugin: Ldap Test Failed to Connect or Bind to server
2025-06-25 16:14:36.887558+00:00LdapException: Unable to connect to server lldap:3890 (91) Connect Error
2025-06-25 16:14:36.887585+00:00System.Net.Sockets.SocketException (111): Connection refused
2025-06-25 16:14:36.887604+00:00at Novell.Directory.Ldap.AsyncExtensions.WaitAndUnwrap(Task task, Int32 timeout)
2025-06-25 16:14:36.887687+00:00at Novell.Directory.Ldap.Connection.Connect(String host, Int32 port, Int32 semaphoreId)

[16:14:36] [WRN] [44] Jellyfin.Plugin.LDAP_Auth.LdapAuthenticationProviderPlugin: Ldap Test Failed to Connect or Bind to server
2025-06-25 16:14:36.887558+00:00LdapException: Unable to connect to server lldap:3890 (91) Connect Error
2025-06-25 16:14:36.887585+00:00System.Net.Sockets.SocketException (111): Connection refused
2025-06-25 16:14:36.887604+00:00at Novell.Directory.Ldap.AsyncExtensions.WaitAndUnwrap(Task task, Int32 timeout)
2025-06-25 16:14:36.887687+00:00at Novell.Directory.Ldap.Connection.Connect(String host, Int32 port, Int32 semaphoreId)

This is the error I get when running "Save and Test LDAP Server Settings" in Jellyfin. To me its not a container network issue because I can ping the lldap container from the jellyfin container...

What's weird is the exact same connection details I'm trying to use with Jellyfin work just fine with Open WebUI...

HackinDogeOP•6/25/25, 4:47 PM

Thanks for the response. I’ll check to see if the Jellyfin container even includes nmap

I did curl lldap:3890 from both the OpenWebUI and Jellyfin containers and both returned the same - “Empty response from server”, which I guess is to be expected without the right connections params

HackinDogeOP•6/25/25, 4:47 PM

I guess what I’m trying to determine is - is this a Jellyfin LDAP plugin issue, an LLDAP issue, or a skill issue?

nitnelave•6/25/25, 4:53 PM

Do you get a message in the LLDAP logs when you try to log in from jellyfin?

nitnelave•6/25/25, 4:56 PM

When you curl, check the http response code

nitnelave•6/25/25, 4:56 PM

You can also try ldapsearch

Nnitnelave Do you get a message in the LLDAP logs when you try to log in from jellyfin?

HackinDogeOP•6/25/25, 6:03 PM

I can’t tell, I think the OpenWebUI connection might be polluting the logs so will disconnect it first then try and see

HackinDogeOP•6/25/25, 6:03 PM

ldapsearch isn’t in the Jellyfin container sadly

HackinDogeOP•6/25/25, 6:04 PM

If I don’t get any logs when attempting to “test server connection” from Jellyfin, what could it be?? It’s weird bc I can ping the lldap container from the Jellyfin container so to me it isn’t a connectivity issue per se?

HackinDogeOP•6/25/25, 6:21 PM

Will do, appreciate both your replies and time

nitnelave•6/25/25, 6:53 PM

If you don't get logs, it means your query is not reaching LLDAP

nitnelave•6/25/25, 6:53 PM

Check that the port is correct, that the host is the right one, that they're on the same network and so on

HackinDogeOP•6/26/25, 8:03 AM

# ldapsearch -H ldap://lldap:3890 -D "uid=_readonly,ou=people,dc=idm,dc=redacted,dc=red" -b "ou=people,dc=idm,dc=redacted,dc=red" -W "(objectClass=user)"    
Enter LDAP Password: 
# extended LDIF
#
# LDAPv3
# base <ou=people,dc=idm,dc=redacted,dc=red> with scope subtree
# filter: (objectClass=user)
# requesting: ALL
#

# search result
search: 2
result: 0 Success
control: 1.2.840.113556.1.4.319 false MAUCAQAEAA==
pagedresults: cookie=

# numResponses: 1

# ldapsearch -H ldap://lldap:3890 -D "uid=_readonly,ou=people,dc=idm,dc=redacted,dc=red" -b "ou=people,dc=idm,dc=redacted,dc=red" -W "(objectClass=user)"    
Enter LDAP Password: 
# extended LDIF
#
# LDAPv3
# base <ou=people,dc=idm,dc=redacted,dc=red> with scope subtree
# filter: (objectClass=user)
# requesting: ALL
#

# search result
search: 2
result: 0 Success
control: 1.2.840.113556.1.4.319 false MAUCAQAEAA==
pagedresults: cookie=

# numResponses: 1

From within the jellyfin container...

nitnelave•6/26/25, 8:05 AM

How did you configure jellyfin, and are there any relevant logs?

HackinDogeOP•6/26/25, 4:14 PM

HackinDogeOP•6/26/25, 4:15 PM

Relevant Jellyfin log is at the beginning of the thread

nitnelave•6/26/25, 4:18 PM

Huh, well you've got me stumped... The ldapsearch command looks to do functionally the same thing as what you've configured jellyfin to do, so I'm not sure why one works but not the other...

HackinDogeOP•6/26/25, 4:19 PM

Glad I’m not totally crazy lmao

This is my first foray into LDAP so I barely know what I’m doing and wasn’t sure if I made a newbie mistake, or if there was a known issue people knew about

HackinDogeOP•6/26/25, 4:20 PM

The fact that these same connection details work with Open WebUI is also weird

nitnelave•6/26/25, 4:21 PM

And you ran ldapsearch from within the jellyfin container?

Nnitnelave And you ran ldapsearch from within the jellyfin container?

HackinDogeOP•6/26/25, 4:21 PM

Correct, had to apt-get it as per the advice in this thread

nitnelave•6/26/25, 4:23 PM

If it's docker, an IP address would be unwieldy, but I guess good for debugging

Nnitnelave If it's docker, an IP address would be unwieldy, but I guess good for debugging

HackinDogeOP•6/26/25, 4:23 PM

It’s Docker

I was thinking the same

HackinDogeOP•6/26/25, 4:23 PM

I can try though!!

nitnelave•6/26/25, 4:24 PM

Domain names are supposed to be the way to go with docker, but yeah...

Jjensen Yeah, but if nothing makes sense, rule out dns, has saved me countless times 🙂

HackinDogeOP•6/26/25, 4:27 PM

Hear hear

nitnelave•6/26/25, 4:27 PM

Did that work?!

HackinDogeOP•6/26/25, 4:28 PM

Oop sorry have yet to try it, was just agreeing with them

I’ll keep you posted, thanks all again for your eyes and time!

HackinDogeOP•6/26/25, 4:38 PM

I’LL BE DAMNED IT DID WORK LMAO

HackinDogeOP•6/26/25, 4:38 PM

So I guess… I should probably disable IPv6 on one or both ends…?

Definitely shouldn’t be hard coding or keeping track of Docker IPs I’d think

HackinDogeOP•6/26/25, 4:40 PM

Why would Open WebUI work with just the hostname?? Is it that it handles IPv6 better?

ie would love to know if this needs to be a bug report on the Jellyfin side, would love to be able to just plug n play like with Open WebUI

nitnelave•6/26/25, 4:56 PM

I think jellyfin will redirect you to their LDAP library, but it's worth a try

HackinDogeOP•6/26/25, 9:33 PM

Just to see, I recreated the container net with --ipv6=false--ipv6=false and lo and behold, Jellyfin connects with just the lldap container hostname now

HackinDogeOP•6/26/25, 9:33 PM

Now that I know root cause, I was able to search around and I guess this is a known issue? https://github.com/jellyfin/jellyfin-plugin-ldapauth/issues/125

GitHub

Error when using IPv6: System.Net.Sockets.SocketException (113): No...

I recently turned on IPv6 support in my docker setup, including the default network for my compose project (IPv4 addresses are still available), this resulted in the plugin being unable to connect ...

# ldapsearch -H ldap://lldap:3890 -D "uid=_readonly,ou=people,dc=idm,dc=redacted,dc=red" -b "ou=people,dc=idm,dc=redacted,dc=red" -W "(objectClass=user)" Enter LDAP Password: # extended LDIF # # LDAPv3 # base <ou=people,dc=idm,dc=redacted,dc=red> with scope subtree # filter: (objectClass=user) # requesting: ALL # # search result search: 2 result: 0 Success control: 1.2.840.113556.1.4.319 false MAUCAQAEAA== pagedresults: cookie= # numResponses: 1