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

Add validation whether fail2ban is really running after install #2

Open
TrezorHannes opened this issue Jan 5, 2023 · 5 comments
Open

Add validation whether fail2ban is really running after install #2

TrezorHannes opened this issue Jan 5, 2023 · 5 comments
Assignees
@TrezorHannes
Labels
bug Something isn't working

Comments

@TrezorHannes
Copy link
Owner 

sudo systemctl status fail2ban.service 
sudo systemctl start fail2ban.service
@TrezorHannes TrezorHannes added the bug Something isn't working label Jan 5, 2023
@TrezorHannes TrezorHannes self-assigned this Jan 5, 2023
@AxelHamburch
Copy link

I think you have to enable the service first and then start the service or reboot the system!?

@TrezorHannes
Copy link
Owner Author

I'll verify that, don't think a restart is necessary.
Further reading

@AxelHamburch
Copy link

If you start the service by

sudo systemctl start fail2ban.service

the it is not necessary, thats true.

@AxelHamburch
Copy link

The standard is ok IMO.

image

@AxelHamburch
Copy link

I just set up a new VPS and used just apt install fail2ban and afterwarts checkt it with systemctl status fail2ban and it shows loaded but inactive (dead). Even after a reboot. I had to set systemctl enable fail2ban and systemctl start fail2ban to get it active.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@TrezorHannes TrezorHannes

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@TrezorHannes @AxelHamburch