Skip to content
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

Does not allow Jellyfin login without password #31

Closed
russelg opened this issue Mar 27, 2022 · 3 comments · Fixed by #78
Closed

Does not allow Jellyfin login without password #31

russelg opened this issue Mar 27, 2022 · 3 comments · Fixed by #78
Labels

Comments

@russelg
Copy link

russelg commented Mar 27, 2022

Description

My Jellyfin account does not have a password, neither the UI for setup or the API allow me to provide an empty password.
Furthermore, http://jellyfin:8096/ is not a valid URL according to the setup.

Version

develop (:latest on docker)

Expected Behavior

I should be able to sign in to Jellyfin without a password. And the above URL should be valid.

Device

  • Platform: Desktop
  • Device: Macbook Pro
  • OS: macOS
  • Browser: Firefox 98.0.1
@Fallenbagel
Copy link
Owner

Furthermore, http://jellyfin:8096/ is not a valid URL according to the setup.

For the URL, jellyseerr would not be able to resolve the DNS, therefore change that to http://localhost:8096 or http://<ip address>:8096

My Jellyfin account does not have a password, neither the UI for setup or the API allow me to provide an empty password.

I have not tested without password but I will check to see if I can implement it. The current way it accesses your jellyfin, it requires a password as the field in the database cannot parse empty space (I'll look into this, however, for the time being the only workaround is to use a simple password)

@russelg
Copy link
Author

russelg commented Mar 27, 2022

For the URL, jellyseerr would not be able to resolve the DNS, therefore change that to http://localhost:8096 or http://<ip address>:8096

Yep, I used the host IP to allow the setup to progress, but my point is that should not be necessary. The setup can resolve my Sonarr and Radarr at http://sonarr:8989 and http://radarr:7878 respectively, so I see no reason why http://jellyfin:8096 could not resolve as well...

@Fallenbagel
Copy link
Owner

🎉 This issue has been resolved in version 1.0.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

Fallenbagel added a commit that referenced this issue May 28, 2022
feat:Remove Requirement for Jellyfin Passwords (#108 #31)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants