Self Hosting Bitwarden, STMP Issues

Submitted ⁨⁨9⁩ ⁨months⁩ ago⁩ by ⁨tuff_wizard@aussie.zone⁩ to ⁨selfhosted@lemmy.world⁩

Hi guy, I’ve managed to get bitwarden up and running in a docker instance as per the instructions provided by bitwarden here.

Its up and available inside and outside the local network but I can’t figure out how to get it to connect to an email provider so it can send verification emails and invitations. I used my Microsoft hosted email, lets call it me@mydomain.com.au (domain provided by a 3rd party).

I’ve edited the global.override.env file to suit the values given by Microsoft and opened port 587 in my router, (unclear whether they want SSL or TLS but I’ve tried both)

I’ve also tried to connect with my gmail but no luck. When I try to verify my email I just get “An unhandled server error has occurred”

Bitwarden is also accessed through bitwarden.mydomain.com.au in this example.

Can anyone point me in the right direction, or even let me know where I might find relevant logs. the stuff in the /bwdata/ folder hasn’t been very helpful.

The only thing I can think of is that when I run “docker ps” in the terminal, none of the bitwarden related containers seem to be specifically passing port 587 through, but that was never mentioned in the guide, and I don’t know which container would need it.

Thanks

source

Comments

Sort:hotnew top

herrfrutti@lemmy.world ⁨9⁩ ⁨months⁩ ago
First, I think you can close that port. You don’t need incoming traffic on that port.

I myselfe use Vaultwarden. But looking on the documentation you need to configure the enviroment correctly.

source
- giddy@aussie.zone ⁨9⁩ ⁨months⁩ ago
  +1 for Vaultwarden. Much simpler to set up
  
  source
keyez@lemmy.world ⁨9⁩ ⁨months⁩ ago
As the other user commented you will need to ensure you have the right ENV vars configured for your SMTP domain. 587 is the incoming port for the SMTP service and none of the containers will have it open and it doesn’t need to be open on your router since bitwarden will only send outgoing to SMTP.

Have you tested sending SMTP via CLI or any other service? You will need auth, and an endpoint and your email setup to receive via that method it should all work.

For example I use mailgun.org to send emails from my homelab to my gmail, you cannot send directly to your email address.

source
- SheeEttin@lemmy.world ⁨9⁩ ⁨months⁩ ago
  I’ve definitely been able to send unauthenticated to my gmail address. The first few usually go to spam, but once I mark them not spam they arrive in my inbox.
  
  source
False@lemmy.world ⁨9⁩ ⁨months⁩ ago
A lot of ISPs and hosting providers block outbound email by default.

source
redcalcium@lemmy.institute ⁨9⁩ ⁨months⁩ ago
Port 587 is typically support TLS. You can confirm it using telnet (telnet 587) then type ehlo . If you see STARTTLS in response, then the server can use TLS.

source
Decronym@lemmy.decronym.xyz ⁨9⁩ ⁨months⁩ ago
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

Fewer Letters More Letters

SMTP Simple Mail Transfer Protocol

SSL Secure Sockets Layer, for transparent encryption

TLS Transport Layer Security, supersedes SSL

[Thread #126 for this sub, first seen 10th Sep 2023, 11:25] [FAQ] [Full list] [Contact] [Source code]

source

Fewer Letters	More Letters
SMTP	Simple Mail Transfer Protocol
SSL	Secure Sockets Layer, for transparent encryption
TLS	Transport Layer Security, supersedes SSL