You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Click on 'send email' next to "Verify your account's email address to unlock access to all features"
See "An error has occurred"
Expected Result
/api/accounts/verify-email is accessed successfully.
No errors are present in logs.
Actual Result
Error on screen
Error in log
Request reached the end of the middleware pipeline without being handled by application code. Request path: POST http://bitwarden/api/accounts/verify-email, Response status code: 404
Screenshots or Videos
Additional Context
I'm rejecting non-encrypted traffic. https is required for communication to my host. I set my globalSettings__baseServiceUri__api variable to use https; however, the log shows that it is attempting to communicate over via http instead of https. I confirmed this is the case with my loadbalancer. The result is a 404 because my load balancer is only handling https.
Build Version
self-host-2024.11.1
Environment
Self-Hosted
Environment Details
K8S
amd64
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.
The text was updated successfully, but these errors were encountered:
I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below.
Steps To Reproduce
Expected Result
/api/accounts/verify-email
is accessed successfully.Actual Result
Screenshots or Videos
Additional Context
I'm rejecting non-encrypted traffic.
https
is required for communication to my host. I set myglobalSettings__baseServiceUri__api
variable to usehttps
; however, the log shows that it is attempting to communicate over viahttp
instead of https. I confirmed this is the case with my loadbalancer. The result is a 404 because my load balancer is only handling https.Build Version
self-host-2024.11.1
Environment
Self-Hosted
Environment Details
Issue Tracking Info
The text was updated successfully, but these errors were encountered: