OK, I had to go to the swag/fail2ban/jail.local and comment out these:
[vaultwarden]
enabled = true
port = 80,443,8086
filter = vaultwarden
#logpath = /config/log/vaultwarden/vaultwarden.log
[vaultwarden-admin]
enabled = true
port = 80,443,8086
filter = vaultwarden-admin
#logpath = /config/log/vaultwarden/vaultwarden.logI don't know if it's the right way to do this, but that error stopped showing up. If anyone has a better solution, please, be my guest.
How did you mount the vaultwarden logs into the swag/fail2ban container?
And did you configure file logging as per the vaultwarden docs: https://github.com/dani-garcia/vaultwarden/wiki/Logging
Yeah, I did it like this:
LOG_FILE=/data/log/vaultwarden.log
And volumes:
volumes:
- /MainPool/Documents/Containers/vaultwarden/vw-data/:/data/
You have to mount this inside the swag container.
I did it, but it still gives me that error. Plus, when I do it with ':ro' at the end it binds it to a local volume for some reason after deployment. How should I mount it?!
EDIT: my mistake at mounting. I fixed, it works now. Mounted it like this:
/my/path/vaultwarden/vw-data/log/vaultwarden.log:/config/log/vaultwarden/vaultwarden.log
the log file location on your host is something like /MainPool/Documents/Containers/vaultwarden/vw-data/log/vaultwarden.log
Check the docs if you have to mount /MainPool/Documents/Containers/vaultwarden/vw-data/log/vaultwarden.log:/vaultwarden/vaultwarden.log:ro
Don’t have an account yet? Register yourself now and be a part of our community!