-
-
Notifications
You must be signed in to change notification settings - Fork 943
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
Unable to open the login page #9408
Comments
I have the same issue with the same setup/version, but my error is just slightly different towards the tail end. I also see the "something went wrong" page. Note that I upgraded from 2023.8 before running into this issue.
|
@swesner411 see #9402. |
Ok, I have narrowed down the problem further. It seems that the in-built source does not have a component. |
Having the same issue after updating. I'll be keeping an eye on this thread. Thanks! |
It appears to be related to the previous issue, as disabling "Plex" as a source fixed it for me. If you are receiving errors related to |
Same for me. I downgraded to 2024.2.3, tried to login but got an HTML issue when I was supposed to enter my 2FA code. Upgraded to 2024.4.0 again, reloaded the page and then got past the "Something went wrong" screen and could enter my 2FA code. I was then able to disable Plex as a source. Without it enabled, everything works fine. |
I have the same issue with Plex setup as a source, How do I get past the "Something Went Wrong" page to disable the sources? |
Switch to the container image In addition, 2024.4.1 will be released in a couple days |
My docker image updated a couple of hours ago and the issue is now resolved! Thanks!! |
Describe the bug
Going to the subdomain's root page (
/
) redirects me to/if/flow/default-authentication-flow/?next=%2F
with the message "Something went wrong! Please try again later."To Reproduce
Likely the same as #9402
Expected behavior
Login should work as expected
Screenshots
If applicable, add screenshots to help explain your problem.
Logs
Formatted:
Version and Deployment (please complete the following information):
gh-541becfe30a1b5534c37b0d3b16c3072974f09f1
)Additional context
N/A
The text was updated successfully, but these errors were encountered: