mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 09:46:00 +03:00
[GH-ISSUE #2284] Fail2ban stop working because no logs since updating to v1.24.0 #1213
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#1213
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @laurentftech on GitHub (Feb 2, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2284
Subject of the issue
Fail2ban is not working anymore with vaultwarden since updating to v1.24.0.
It seems that VW has stopped recording in log file.
Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
Install method:
Docker
Clients used:
Reverse proxy and version:
Caddy v2.4
MySQL/MariaDB or PostgreSQL version:
Other relevant details:
Steps to reproduce
Expected behaviour
Logs are recorded.
Actual behaviour
VW stopped recording logs. I tried to delete the vaulwarden.log file but it doesn't help.
Troubleshooting data
@BlackDex commented on GitHub (Feb 2, 2022):
Your log_file is set to null.
Try to set a filename.