mirror of
https://github.com/dani-garcia/bitwarden_rs
synced 2024-11-22 01:48:09 +01:00
Deleted old configuration examples
parent
f6e637754b
commit
0df60bbff9
@ -1,12 +1,3 @@
|
||||
> [!WARNING]
|
||||
> Vaultwarden version before v1.25.0 had a bug/mislabelled configuration setting regarding SSL and TLS.
|
||||
> This has been fixed in testing and newer released versions.
|
||||
> The old settings were `SMTP_SSL` and `SMTP_EXPLICIT_TLS`.
|
||||
> The new setting is `SMTP_SECURITY` which has the following options: `starttls`, `force_tls` and `off`.
|
||||
> `SMTP_SSL=true` equals `starttls`
|
||||
> `SMTP_EXPLICIT_TLS=true` equals `force_tls`
|
||||
---
|
||||
|
||||
You can configure vaultwarden to send emails via a SMTP agent:
|
||||
|
||||
```sh
|
||||
@ -150,29 +141,6 @@ Also, the quotes `'` and `"` could cause some issues, so lets enclose this passw
|
||||
To have the password above to work we need to type `'~^",a.%\\,\'}b&@|/c!1(#}'`, here you see that we escaped both the `\` and the `'` characters and used single quotes to surround the whole password.
|
||||
So: `~^",a.%\,'}b&@|/c!1(#}` becomes `'~^",a.%\\,\'}b&@|/c!1(#}'`
|
||||
|
||||
## Using deprecated SMTP environment variable `SMTP_SSL` and `SMTP_EXPLICIT_TLS` (for v1.24.0 and lower)
|
||||
|
||||
Use of `SMTP_SSL` and `SMTP_EXPLICIT_TLS` environment variables has been deprecated since v1.25.0.<br>
|
||||
if you are using v1.24.0 and lower, you can still use `SMTP_SSL` and `SMTP_EXPLICIT_TLS` environment variables:
|
||||
|
||||
```sh
|
||||
docker run -d --name vaultwarden \
|
||||
-e SMTP_HOST=<smtp.domain.tld> \
|
||||
-e SMTP_FROM=<vaultwarden@domain.tld> \
|
||||
-e SMTP_PORT=587 \
|
||||
-e SMTP_SSL=true \
|
||||
-e SMTP_USERNAME=<username> \
|
||||
-e SMTP_PASSWORD=<password> \
|
||||
-v /vw-data/:/data/ \
|
||||
-p 80:80 \
|
||||
vaultwarden/server:latest
|
||||
```
|
||||
|
||||
When `SMTP_SSL` is set to `true`(this is the default), only TLSv1.1 and TLSv1.2 protocols will be accepted and `SMTP_PORT` will default to `587` (equals `SMTP_SECURITY=starttls`). If set to `false`, `SMTP_PORT` will default to `25` and the opportunistic encryption will be tried (no encryption attempted with code prior to 3/12/2020)(equals `SMTP_SECURITY=off`). This can be very insecure, use this setting only if you know what you're doing. To run SMTP in implicit (forced TLS) mode, set `SMTP_EXPLICIT_TLS` to `true` (equals `SMTP_SECURITY=force_tls`). If you can send emails without logging in, you can simply not set `SMTP_USERNAME` and `SMTP_PASSWORD`.
|
||||
|
||||
> [!NOTE]
|
||||
> If you use these `SMTP_SSL` and `SMTP_EXPLICIT_TLS` settings on v1.25.0 and higher, vaultwarden will omit error for using deprecated setting.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
It often happens that people are having issues with connecting to there SMTP server from Vaultwarden.<br>
|
||||
|
Loading…
Reference in New Issue
Block a user