-
Notifications
You must be signed in to change notification settings - Fork 35
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Steps To Reproduce
- Run on standard RKE2 cluster (for example) which comes with NGINX ingress by default
- Complete helm installation
- Access bitwarden ingress endpoint
Expected Result
BitWarden login page is shown
Actual Result
NGINX 404 Error
Screenshots or Videos
No response
Additional Context
To enable REGEX paths, an annotation should be set on the ingress resource. See: https://kubernetes.github.io/ingress-nginx/user-guide/ingress-path-matching/
Chart Version
self-host-1.1.6
Environment Details
RKE2 with NGINX Ingress
Issue Tracking Info
- I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working