Error configuring SMTP: SMTP_SECURITY is invalid. It needs to be one of the following options: starttls, force_tls or off #628

New Issue

OVERLORD · 2025-10-09T16:42:23+03:00

OVERLORD commented

2025-10-09 16:42:23 +03:00

Originally created by @mlopezcoria on GitHub.

Hello,

I'm getting this error message in the docker log:

Error loading config:
`SMTP_SECURITY` is invalid. It needs to be one of the following options: starttls, force_tls or off

But I read the documentation and the environment variables seem to be ok:

version: "3.8"

services:
  vaultwarden:
    image: vaultwarden/server:latest
    restart: always
    networks:
        - frontend
    volumes:
        - ./data:/data
    environment:
        - SMTP_HOST=mail.mydomain.com
        - SMTP_FROM=vaultwarden@mydomain.com
        - SMTP_PORT=587
        - SMTP_SECURITY=starttls
        - SMTP_USERNAME=no-reply@mydomain.com
        - SMTP_PASSWORD=areallysecretpassword

volumes:
  data:

networks:
  frontend:
    external: true

I tried changing SMTP_PORT=25 SMTP_SECURITY=off and also SMTP_PORT=465 SMTP_SECURITY=force_tls but log keeps showing the same error.

Am I doing anything wrong?

Originally created by @mlopezcoria on GitHub. Hello, I'm getting this error message in the docker log: ``` Error loading config: `SMTP_SECURITY` is invalid. It needs to be one of the following options: starttls, force_tls or off ``` But I read the documentation and the environment variables seem to be ok: ``` version: "3.8" services: vaultwarden: image: vaultwarden/server:latest restart: always networks: - frontend volumes: - ./data:/data environment: - SMTP_HOST=mail.mydomain.com - SMTP_FROM=vaultwarden@mydomain.com - SMTP_PORT=587 - SMTP_SECURITY=starttls - SMTP_USERNAME=no-reply@mydomain.com - SMTP_PASSWORD=areallysecretpassword volumes: data: networks: frontend: external: true ``` I tried changing `SMTP_PORT=25 SMTP_SECURITY=off` and also `SMTP_PORT=465 SMTP_SECURITY=force_tls` but log keeps showing the same error. Am I doing anything wrong?

OVERLORD closed this issue

2025-10-09 16:42:25 +03:00

OVERLORD commented

2025-10-09 16:42:27 +03:00

@mlopezcoria commented on GitHub:

I found the problem: I had to docker compose down && docker compose up -d

@mlopezcoria commented on GitHub: I found the problem: I had to `docker compose down && docker compose up -d`

OVERLORD referenced this issue

2025-10-09 17:40:18 +03:00

Issue "preflight response not successful" #1986

Sign in to join this conversation.