Skip to content
This repository has been archived by the owner on Jan 26, 2022. It is now read-only.

Fail2Ban Issue #137

Open
lordvault opened this issue Dec 19, 2020 · 0 comments
Open

Fail2Ban Issue #137

lordvault opened this issue Dec 19, 2020 · 0 comments

Comments

@lordvault
Copy link

Hi first, thanks for share your work with us.
Im using thins vestacp on a host VM, but looking the /var/log/auth.log i saw a lot of failures from Chinesse and russian machiness trying to access to the machine through SSH. I enable the fail2ban service to try to ban those IP but at this moment the fail2ban has none ip banned. I was doing some research and after check the rules for fail2ban, i found that we have the Fail2Ban v0.9.3 version and the latest one is 0.11.2 and on the relese notes i saw some bennefits for use a more recent version, and maibe a fix for the posible issue that im having.
As i check the fail2ban is limited by the Ubuntu version https://packages.ubuntu.com/search?keywords=fail2ban .
At this moment the vestacp dockerfile depends on the docker-hostingbase and this depends on phusion/baseimage:0.10.2 that keeps using 16.04.

Why keep using the phusion/baseimage:0.10.2 and not use the latest one ?

Again thanks 4 your job, i hope this comments helps to make a great and more robust tool for the community.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant