Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Setting up fail2ban #135

Open
shalak opened this issue Dec 22, 2023 · 2 comments
Open

Setting up fail2ban #135

shalak opened this issue Dec 22, 2023 · 2 comments

Comments

@shalak
Copy link

shalak commented Dec 22, 2023

Hello!

Are there any guidelines on how to setup fail2ban for this deployment?

Unfortunatley, the apache log does not contain any 401 replies, and from the browser perspective, unsuccessful login attempt gets reply 200...
@NathanVaughn
Copy link
Owner

I don't I'm afraid. I've never used fail2ban with Apache before. I would suggest making your own image based on this one that installs and configures it, using a sidecar container like https://hub.docker.com/r/linuxserver/fail2ban or putting a reverse proxy in front of webtrees that has fail2ban.

@shalak
Copy link
Author

shalak commented Dec 24, 2023

fail2ban itself is not a problem, the issue is that apache does not produce "login failed" error.

The only idea that comes to my mind is a companion container, which will poll the db (via SELECT * FROM wt_log) and for matching log. Looks expensive :/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@shalak @NathanVaughn