Issue with SMTP_TLS in .env

dadatuputi / bitwarden_gcloud

Bitwarden installation optimized for Google Cloud's 'always free' e2-micro compute instance

https://bradford.la/2020/self-host-bitwarden-on-google-cloud/

MIT License

344 stars 79 forks source link

Issue with SMTP_TLS in .env #74

Closed ghost closed 1 year ago

ghost commented 1 year ago

When starting/stopping the container with docker-compose, I see this message: The SMTP_TLS variable is not set. Defaulting to a blank string.

What is the use of SMTP_TLS and what should be its value if any?

dadatuputi commented 1 year ago

Hi, I'm unable to duplicate this, even if I comment out SMTP_TLS or set it to an empty string. Some questions for you:

Is yours set to YES or NO as in the instructions?
Do you otherwise have SMTP settings filled out?
Was this working before?
Do you have the latest files (git pull and docker-compose pull)?

ghost commented 1 year ago

SMTP_TLS is commented out
The rest of the SMTP settings are filled out
I am able to get the fail2ban smtp to work without setting this variable
I do have the latest files

I don't think this is a critical issue as smtp is working as intended with fail2ban.

dadatuputi commented 1 year ago

I've made some changes to the SMTP settings for fail2ban in 3373765b388576ddccbe6f5caf165967712db447. If your issue returns, try pulling the latest source and docker images and re-open.