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

Links in emails are sent without custom port number #2553

Closed
1 task done
Tracked by #2480
karolszklarski opened this issue Jan 8, 2023 · 2 comments
Closed
1 task done
Tracked by #2480

Links in emails are sent without custom port number #2553

karolszklarski opened this issue Jan 8, 2023 · 2 comments
Labels
bug bw-unified-deploy An Issue related to Bitwarden unified deployment

Comments

@karolszklarski
Copy link

Steps To Reproduce

Configure bitwarden to listen on public ip on non-standard port, like https://host.name.com:12345/

Invoke any action that sends an email with confirmation link. Read the email.

Expected Result

The confirmation link in an email should begin with https://host.name.com:12345/

Actual Result

The confirmation link in an email begins with https://host.name.com/

Screenshots or Videos

No response

Additional Context

image: bitwarden/self-host:beta@sha256:7e586dc66c016360fd56dcbea462a4c92828ea65324a08012501b6ec99dec7fd

Githash Version

455d62e-dirty

Environment Details

settings.env
BW_ENABLE_SSL=true
BW_PORT_HTTPS=12345

docker-compose.yml
ports:
- 12345:12345

The edge router is forwarding external port 12345 to docker host machine port 12345.

Database Image

mariadb Ver 15.1 Distrib 10.5.18-MariaDB, for debian-linux-gnueabihf (armv8l) using EditLine wrapper

Issue-Link

#2480

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.
@karolszklarski karolszklarski added bug bw-unified-deploy An Issue related to Bitwarden unified deployment labels Jan 8, 2023
@kspearrin
Copy link
Member

You would need to update your service URL env vars to include the port. I think the default configuration assumes a standard port being access from the frontend.

Try setting the following env var:

globalSettings__baseServiceUri__vault=https://host.name.com:12345

@karolszklarski
Copy link
Author

It worked, thank you! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug bw-unified-deploy An Issue related to Bitwarden unified deployment
Projects
None yet
Development

No branches or pull requests

2 participants