Sign-in goes through Jellyfin’s normal username/password endpoint (AuthenticateByName) plus Quick Connect, which is the same path the LDAP plugin hooks into, so LDAP logins generally work with a standard client like this, it shouldn’t be the blocker by itself. A few things worth trying: if your server has Quick Connect enabled, try that (it sidesteps the password path entirely and is a good way to isolate the problem); double-check the server URL has the scheme and port (e.g. host:8096); and a self-signed HTTPS cert can also cause a failure. If you can paste the exact error you’re seeing, I’ll dig in, and a GitHub issue is welcome.
Image/photo
i am using the linux Appimage, quick connect simply times out, no messages in console except :
I have jellyfin running on a domain with proper certs and jellyfin's official client works perfectly.
TraceApps@lemmy.world 1 day ago
Sorry about that. That message is a network timeout, so the Quick Connect request isn’t getting a response back within the window. Since you had to enter the server address to reach that screen, plain reachability and your cert are should be fine, so it’s something specific to the Quick Connect path.
Two things would help me narrow it down:
Does normal username/password sign-in work against the same server, or does that time out too? If password works and only Quick Connect hangs, that isolates it to the Quick Connect endpoints.
Is Jellyfin behind a reverse proxy (nginx/Caddy/Traefik), and which Jellyfin version?
interface looks nice! but playback stutters, with hardware acceleration on or off (makes no difference).
TraceApps@lemmy.world 1 day ago
Glad 10.11.11 fixed the login. Since it’s the same with hardware acceleration on or off, decoding isn’t the bottleneck, it’s likely delivery or frame timing. Two quick checks: in your Jellyfin dashboard, is that session Direct Play or Transcode? And does the same file play smoothly in plain mpv/VLC (Fathom uses libmpv underneath)? That’ll tell us if it’s server/network vs. something on the Fathom side.