Anubis site (default-anubis) has no /keel-health: HTTPS health returns 404 in cloud modes #7
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Keel-Linux/keel-web#7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found 2026-10-04 on three Keel Web nodes switched to cloud_advanced: with the anubis overlay enabled, the default site answers 200 but HTTPS /keel-health returns 404, because default-anubis has no /keel-health location. keel-default has it on 80 and 443. The manifest's nginx health check and any load balancer probe need it in both sites. Add the location (204, no auth, not challenged by Anubis, excluded from Coraza) to default-anubis on both schemes, with a test for both sites.