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

Healthcheck endpoints returning 404 #9975

Open
wuast94 opened this issue Jun 4, 2024 · 8 comments
Open

Healthcheck endpoints returning 404 #9975

wuast94 opened this issue Jun 4, 2024 · 8 comments
Labels
bug Something isn't working wontfix

Comments

@wuast94
Copy link

wuast94 commented Jun 4, 2024

Describe the bug

wget http://proxy_authentik-server:9000/-/health/live/
Connecting to proxy_authentik-server:9000 (10.0.17.8:9000)
wget: server returned error: HTTP/1.1 404 Not Found

Expected behavior
get the 204 response

Version and Deployment (please complete the following information):

  • authentik version: 2024.4.2
  • Deployment: swarm

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

@wuast94 wuast94 added the bug Something isn't working label Jun 4, 2024
@rpoovey
Copy link

rpoovey commented Jun 7, 2024

+1

@authentik-automation
Copy link
Contributor

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.

@wuast94
Copy link
Author

wuast94 commented Aug 8, 2024

not stale

@authentik-automation
Copy link
Contributor

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.

@wuast94
Copy link
Author

wuast94 commented Oct 8, 2024

not stale

@BeryJu
Copy link
Member

BeryJu commented Oct 8, 2024

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.

@wuast94
Copy link
Author

wuast94 commented Oct 8, 2024

that sounds logical but nothing i can do about sadly

@authentik-automation
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working wontfix
Projects
None yet
Development

No branches or pull requests

3 participants