-
Notifications
You must be signed in to change notification settings - Fork 61
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
log ip for failed logins #133
Comments
thanks! I'll try it as soon as the docker hub is updated |
I am not sure whether this is a problem of my setup (podman) or anything else, but the ip reportet is the internal ip of the virtual network device. Any idea on that? |
if you are connecting from the host on which docker is running, that is the case, try connecting from a different host |
Thanks for the reply. It was a different host, even in a completely different network. (I wanted to be sure that the router does no strange stuff when accessing it's own IP).
which should lead to the correct IP passed to the container. |
Taking a closer look, I think the problem might be that one needs some way to configure "which headers to hold the real client IP" or some logic for it. |
yes, I saw that, there has been some drama. I pushed a new version, you should set |
ah nice, thank you very much! |
just tried, it works now! |
It would be nice if the log would contain the ip for a failed login attempt, then it would be possible to write a simple fail2ban filter to harden the page a bit.
The text was updated successfully, but these errors were encountered: