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

globalSettings__baseServiceUri__api Ignored for verify-email #5125

Open
1 task done
r351574nc3 opened this issue Dec 8, 2024 · 1 comment
Open
1 task done

globalSettings__baseServiceUri__api Ignored for verify-email #5125

r351574nc3 opened this issue Dec 8, 2024 · 1 comment
Labels

Comments

@r351574nc3
Copy link

Steps To Reproduce

  1. Login with unverified user
  2. Click on 'send email' next to "Verify your account's email address to unlock access to all features"
  3. 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

image

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.
@r351574nc3 r351574nc3 added the bug label Dec 8, 2024
@jtodddd
Copy link

jtodddd commented Dec 9, 2024

Hi there,

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.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants