-
-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add the ability to store access logs to a file #2080
Comments
Hi 👋. Thank you for submitting your first issue to Homarr. Please ensure that you've provided all nessesary information. You can use the three dots > Edit button to update your post with additional images and information. Depending on the current volume of requests, the team should get in conact with you shortly. |
Hello 👋, this issue has been open for 60 days without activity. We mark issues to help prioritise and close dead issues. Can you confirm that this issue is still relevant on the latest version? I'll remove the stale label as soon as there is further activity on this issue. Thank you 🙏 |
Would also really appreciate this feature! |
👍 |
Hello 👋, this issue has been open for 60 days without activity. We mark issues to help prioritise and close dead issues. Can you confirm that this issue is still relevant on the latest version? I'll remove the stale label as soon as there is further activity on this issue. Thank you 🙏 |
Description
Utilities like
fail2ban
could be using in conjunction with Homarr if it were possible to print failed login attempts in a log file.At the moment, failed login attempts are not even in the logs (unless I missconfigured my container) whereas successful login attempts are written to the logs.
So the idea would be
That way we don't have to use
docker log
and can easily configure a fail2ban filter and jail using the defined logfile.Strictly speaking, the logfile is not even necessary if docker is configured to output logs to
syslog
orjournald
. Having at least the failed login attempts inside the logs would be great for security.Please tick the boxes
The text was updated successfully, but these errors were encountered: