-
-
Notifications
You must be signed in to change notification settings - Fork 945
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
Healthcheck endpoints returning 404 #9975
Comments
+1 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
not stale |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
not stale |
The only cause for this I can imagine is that your internal hostname contains an underscore, which docker compose v1 did (and I assume swarm inherits from that), which is not actually a valid DNS character and as such django throws an error. However that should result in a 500 or similar response. |
that sounds logical but nothing i can do about sadly |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Describe the bug
Expected behavior
get the 204 response
Version and Deployment (please complete the following information):
Additional context
When i query the full https domain through my proxy i get the 204.
i want to monitor authentik using uptimekuma and dont want to have the proxy in beetween for healthchecks
The text was updated successfully, but these errors were encountered: