Vaultwarden not starting successfully since updating beyond1.27.0

Help
1

Hi All,

I’ve been using Vaultwarden since int was bitwarden_rs and after the initial setup in docker compose, it’s been fine… until the releases following 1.27.0.

I noticed last week that I couldn’t save logins and then couldn’t login via the iOS app after logging out. Anyway, it turns out that the two releases following 1.27.0 won’t work with my previous setup. I did notice that I was using an older SMTP_EXPLICIT_TLS entry but after changing that, the container still wouldn’t start correctly. I managed to get things working again by specifying v1.27.0 in the compose file.

The output of the log I receive when trying to use the latest release (and the one prior) is below:

|                        Starting Vaultwarden                        |
|                           Version 1.28.1                           |
|--------------------------------------------------------------------|
| This is an *unofficial* Bitwarden implementation, DO NOT use the   |
| official channels to report bugs/features, regardless of client.   |
| Send usage/configuration questions or feature requests to:         |
|   https://github.com/dani-garcia/vaultwarden/discussions or        |
|   https://vaultwarden.discourse.group/                             |
| Report suspected bugs/issues in the software itself at:            |
|   https://github.com/dani-garcia/vaultwarden/issues/new            |
\--------------------------------------------------------------------/
[INFO] Using saved config from `data/config.json` for configuration.
[WARNING] The following environment variables are being overriden by the config.json file.
[WARNING] Please use the admin panel to make changes to them:
[WARNING] DOMAIN, SIGNUPS_ALLOWED, ADMIN_TOKEN, SMTP_HOST, SMTP_PORT, SMTP_FROM, SMTP_USERNAME, SMTP_PASSWORD
[DEPRECATED]: `SMTP_SSL` or `SMTP_EXPLICIT_TLS` is set. Please use `SMTP_SECURITY` instead.
Error loading config:
  Unable to write to log file. /data/logs/bitwarden.log

I’d like to stay on the latest version but am not sure what the issue could be, given that things worked perfectly previously.

Here’s the redacted part of my compose file for clarity:

# bitwarden docker-compose.yml
version: '2'

services:
  vaultwarden:
    image: vaultwarden/server:latest
    container_name: bitwarden
    restart: unless-stopped
    volumes:
      - /volume1/docker/appdata/bitwarden:/data
      - /etc/localtime:/etc/localtime:ro
    ports: 
      - 32022:3012
      - 32180:80
    environment:
      WEBSOCKET_ENABLED: 'true' # Required to use websockets
      LOG_FILE: /data/logs/bitwarden.log
      EXTENDED_LOGGING: 'true'
      LOG_LEVEL: 'warn'
      SIGNUPS_ALLOWED: 'false'
      SMTP_HOST: smtp.gmail.com
      SMTP_FROM: bitwarden@XXXXX.co.uk
      SMTP_PORT: '587'
      SMTP_EXPLICIT_TLS: 'true'
      SMTP_USERNAME: bitwarden@XXXXX.co.uk
      SMTP_PASSWORD: XXXXX
      DOMAIN: https://bitwarden.XXXXX.co.uk
      ADMIN_TOKEN: 'XXXXX'

I’m doing this on a Synology but that shouldn’t make any difference in terms of how Docker works.

Any pointers would be appreciated.

2

Make sure the logs directory exists and is accessable.

3

That sounded simple and sensible… and worked!

Thanks @BlackDex

1 Like