Email images don't display when using custom port #945

New Issue

Closed

opened 2026-02-04 23:25:10 +03:00 by OVERLORD · 2 comments

OVERLORD commented 2026-02-04 23:25:10 +03:00

Owner

Copy Link

Originally created by @JOHLC on GitHub (Feb 20, 2021).

Subject of the issue

Email images don't display when using custom port

Your environment

• Bitwarden_rs version: 1.19.0

• Install method: Docker

• Clients used: Any

• Reverse proxy and version: Nginx

• Version of mysql/postgresql: Unknown
  

• Other relevant information:

Possible workarounds:
-- Use Base64 encoding so the image doesn't need to call a local resource


-- Allow user to specify port for static content like that
-- Serve the content from an online source instead of locally

Steps to reproduce

Set custom https port number
Setup SMTP email
Receive email from Bitwarden RS
Notice issue

Expected behavior

Images should display in the emails from Bitwarden

Actual behavior

Images broken in the email - in my case this is because I use a custom port and the email is hardcoded to default https port
Correct image url https://mydomain.com:5448/bwrs_static/logo-gray.png
Url used in the html email: https://mydomain.com/bwrs_static/logo-gray.png

Relevant logs

Originally created by @JOHLC on GitHub (Feb 20, 2021). <!-- # ### NOTE: Please update to the latest version of bitwarden_rs before reporting an issue! This saves you and us a lot of time and troubleshooting. See: https://github.com/dani-garcia/bitwarden_rs/issues/1180 # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/obfuscate personal and confidential information, such as names, global IP/DNS addresses and especially passwords, if necessary. --> ### Subject of the issue Email images don't display when using custom port ### Your environment <!-- The version number, obtained from the logs or the admin diagnostics page --> <!-- Remember to check your issue on the latest version first! --> * Bitwarden_rs version: 1.19.0 <!-- How the server was installed: Docker image / package / built from source --> * Install method: Docker * Clients used: Any * Reverse proxy and version: Nginx * Version of mysql/postgresql: Unknown  * Other relevant information: Possible workarounds: -- Use Base64 encoding so the image doesn't need to call a local resource   -- Allow user to specify port for static content like that -- Serve the content from an online source instead of locally ### Steps to reproduce Set custom https port number Setup SMTP email Receive email from Bitwarden RS Notice issue <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start bitwarden_rs? --> ### Expected behavior Images should display in the emails from Bitwarden  ### Actual behavior Images broken in the email - in my case this is because I use a custom port and the email is hardcoded to default https port Correct image url https://mydomain.com:5448/bwrs_static/logo-gray.png Url used in the html email: https://mydomain.com/bwrs_static/logo-gray.png  ### Relevant logs <!-- Share some logfiles, screenshots or output of relevant programs with us. -->

OVERLORD closed this issue 2026-02-04 23:25:11 +03:00

OVERLORD commented 2026-02-04 23:25:18 +03:00

Author

Owner

Copy Link

@JOHLC commented on GitHub (Feb 20, 2021):

Neverminded I was able to resolve this by setting domain url with the port number in the admin panel

@JOHLC commented on GitHub (Feb 20, 2021): Neverminded I was able to resolve this by setting domain url with the port number in the admin panel  

OVERLORD commented 2026-02-04 23:25:25 +03:00

Author

Owner

Copy Link

@BlackDex commented on GitHub (Feb 20, 2021):

As the screenshot already tells you, your domain configuration is not correct. If you run bitwarden an other port, you also need to configure that as as DOMAIN, So include the :5684

@BlackDex commented on GitHub (Feb 20, 2021): As the screenshot already tells you, your domain configuration is not correct. If you run bitwarden an other port, you also need to configure that as as `DOMAIN`, So include the `:5684`

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

cached-config-operations

test_dylint

1.35.2

1.35.1

1.35.0

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear labels

SSO

Third party

better for forum

bug

bug

documentation

duplicate

enhancement

future Vault

future Vault

future Vault

good first issue

help wanted

low priority

notes

pull-request

Mirrored from GitHub Pull Request

question

troubleshooting

wontfix

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

OVERLORD

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#945