-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sign in issues #138
Comments
Hi can you produce logs from the server of the failed login event? |
Unfortunately it is a server hosted by my friend so I don’t have the best
quality access to the logs haha but here is what he sent me. It looks like
the issue is the 6:40 log stating a username error. But I was able to use
the official Jellyfin client with the exact same login details.
…On Tue, Oct 29, 2024 at 22:10 Seven Rats ***@***.***> wrote:
Hi can you produce logs from the server of the failed login event?
—
Reply to this email directly, view it on GitHub
<#138 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BIRNZBJMJRZGTGV2TOFRTPDZ6A5XTAVCNFSM6AAAAABQ3DR4W2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBVGY3TEMRSHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Can you provide information about the OS, the Jellyflix and the Jellyfin version you are using? |
I'm encountering the same problem. There are no error logs in my Jellyfin instance, only these four info logs appear when I attempt to log in. jellyfin: 10.9.11 [10:33:51] [INF] [45] Jellyfin.Server.Implementations.Users.UserManager: Authentication request for <username> has succeeded.
[10:33:51] [INF] [45] Emby.Server.Implementations.Session.SessionManager: Current/Max sessions for user <username>: 2/0
[10:33:51] [INF] [45] Emby.Server.Implementations.Session.SessionManager: Logging out access token <token>
[10:33:51] [INF] [45] Emby.Server.Implementations.Session.SessionManager: Creating new access token for user <token> |
@navneetlal The macOS (dmg) 0.10.X version has an issue accessing the keychain. You can try using the latest prerelease version or the App Store version |
I have the same issue with the 0.10.0 release running on Debian Testing. My Jellyfin server logs similarly show me logging in:
But I get no visible change in the application state after hitting login. I see an error on the terminal: And note that when I run from a fresh git checkout, I have keyring issues (see #145 for details). Jellyfin version 10.9.10, running on a Debian Testing box on my LAN. |
Yep, same here. Just downloaded the app, input server and user details, clicked "Login"......aaaaaaand nothing. Even deleted the app and redownloaded, as the first time I'd selected "no" to the "allow app to access local networks" question. So the next time I selected "yes", but no difference. |
@jdk-21 this is getting kinda interesting actually. we now have keyring failure reports from all 3 platforms. somebody should probably dig into flutter secure storage when we have a sec i wonder if they dropped a bad version or maybe we missed an important change. edit actually I am jumping the gun on this. @nzerinto can you please open a new issue there is no evidence that your report is related to this bug report regarding keychain issues on macos and debian. @jdk-21 if you give me triage on this repo I will rename this to reflect its actual content. |
@sevenrats I just figured my issue mirrors exactly what @zooz89 experienced, in that I downloaded the app to connect to my Jellyfin server, and it doesn't do anything after inputting server/login details and hitting the "Login" button. |
yeah somebody is just going to have to dig in too. the macos reference is not from the OP so this issue is just in the weeds and is going to need a bunch of handholding. thats life I guess. |
I downloaded Jellyflix excited to try out its features but unfortunately was unable to sign in to my Server. Upon filling out the relevant information and pressing the sign in button I was met with nothing. No error messages, no loading screens, no login. I was able to log in using the default Jellyfin client using the same information, so it was not an error there. I look forward to trying your product in the future. I hope you are able to resolve this issie :)
The text was updated successfully, but these errors were encountered: