-
-
Notifications
You must be signed in to change notification settings - Fork 339
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
bug: connect button disabled - cannot connect to server #828
Comments
Turns out when I started my server it would login using the old connection. So I don't know if this is expected behavior and it checks in the background whether the server is online and then allows you to hit the button. |
I'm getting this on macOS as well. |
I had this problem a while back when updating jellyfin to the latest version - i think there was some kind of configuration mismatch between the old and new versions that caused it to struggle to find the old server details. Oddly, for me, i couldn't type in the connect input to enter the new details. Deleting all the config files fixed it for me. |
Same here - Windows 10. Reinstall the app did not help - but fixed it by deleting all Jellyfin-data in 'AppData' |
Four considerations:
%LOCALAPPDATA%\JellyfinMediaPlayer\logs
~/.local/share/jellyfinmediaplayer/logs/
~/.var/app/com.github.iwalton3.jellyfin-media-player/data/jellyfinmediaplayer/logs/
~/Library/Logs/Jellyfin Media Player/
Logs: JellyfinMediaPlayer.log
Describe the bug
A clear and concise description of what the bug is.
The
Connect
button under the host field is disabled, so I can't connect.To Reproduce
Steps to reproduce the behavior:
Start the program. I also repaired through the installer.
Expected behavior
Connect to the server
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
Might also be noteworthy, that I did nothing to disconnect in the first place. Just didn't use it for a couple months.
The text was updated successfully, but these errors were encountered: