-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Register Form tab is showing but Content is of Login in Sentry 24.11.1 #3466
Comments
Having the same issue here~ It seems like a duplicate of #2954 but it was unanswered there either. The 'Sentry -> Admin Settings -> Enable Registration' settings is not there any more. |
Hey @Kishan0330 does this solves the problem? #2954 (comment) |
@wendellli99 Hello, the settings is still there. Top left --> Admin --> Settings --> Enable Registration |
No this does not solve the probem |
This does not solve the problem either(it is already on that is why i am seeing the Register tab) |
I think it's better to keep the issue open if the problem isn't resolved, I have also encountered this issue, using last week's nightly build. edit update, |
For Information: I did not upgrade sentry. This is fresh Installation |
I also encountered this problem, has anyone found a solution? I encountered this when installing release 24.12.0, rolled back to 24.8.0 |
Hi everyone! I got into the same situation after upgrading Sentry from 24.11.1 to 24.12.0 - the "Register" tab doesn't open anymore, disregarding whether I enabled the registration or just sent the invite to the user. The console has such errors:
and
@aldy505 I also checked your recommendation from #2954 (comment) - I had everything set. |
Self-Hosted Version
24.11.1
CPU Architecture
x86_64
Docker Version
27.4.0
Docker Compose Version
2.27.0
Machine Specification
Steps to Reproduce
Expected Result
Actual Result
install-logs.txt
docker-compose-logs.txt
Image of login form --> Notice the URL
--> URL is set Register but form did not changed
Event ID
No response
The text was updated successfully, but these errors were encountered: