[ASTPPCOM-509] Fail2ban Missing in v4.0 Created: 31/May/19  Updated: 03/Jan/22  Resolved: 03/Jan/22

Status: Done
Project: ASTPP Community
Component/s: None
Affects Version/s: None
Fix Version/s: v4.0.2

Type: New Feature
Reporter: baloeng Assignee: Palak Rami (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Hello,

After successful installation of v4.0, I noticed the fail2ban is missing in /etc directory even though the package is installed.

I went through the install script and I noticed the following;
`wget --no-check-certificate https://latest.astppbilling.org/fail2ban_Cent.tar.gz
tar xzvf fail2ban_Cent7.tar.gz
rm -rf /etc/fail2ban
cp -rf /usr/src/fail2ban /etc/fail2ban`

The problem here is that wget --no-check-certificate https://latest.astppbilling.org/fail2ban_Cent.tar.gz return connection refused while installing (and still does if you go to the URL), hence, no fail2ban_Cent7.tar.gz was downloaded and files in /etc/fail2ban were deleted.

 Comments   
Comment by redbehrend [ 09/Jun/19 ]

Get the Same error turns out their HTTPS doesn't work... I seriously curious if they even tested 4.0 install before release... maybe they aren't setup to handing debian using HTTPS...
this works though http://latest.astppbilling.org/fail2ban_Cent.tar.gz

Edit1: forgot to mention even when you fix the download they left the old extract so you gotta change
http://latest.astppbilling.org/fail2ban_Cent.tar.gz
tar xzvf fail2ban_Cent7.tar.gz
to tar xzvf fail2ban_Cent.tar.gz

http://latest.astppbilling.org/fail2ban_Deb.tar.gz
tar xzvf fail2ban_Deb8.tar.gz
to tar xzvf fail2ban_Deb.tar.gz

Edit2:
So I had to change a bunch of stuff in the install script you also have to change the loglevel to INFO in the /etc/fail2ban/fail2ban.conf file because they use integer in their package which is not supported on current stretch version though the new beta version will accept string and integer.

Also need to edit the /etc/fail2ban/jail.conf and change pam-generic port=anyport
From: port = anyport
To: #port = anyport

Someone at ASTPP really needs to go through the fail2ban package and make it up to standard.

Comment by Palak Rami (Inactive) [ 29/Nov/21 ]

Hello [~baloeng]

Please share the screenshot for the same, as we have not found any  similar error with version 4.

Thanks.

Comment by Palak Rami (Inactive) [ 03/Jan/22 ]

Hello [~baloeng],

We are closing this ticket for now as there is no response since many days from your end. Feel-free to re-eopen it again.

Regards,

Palak.

Generated at Sat Feb 10 07:17:48 CET 2024 using Jira 8.13.3#813003-sha1:22ebedbb75c99b147c66f14e031dd8a2d214753a.