1 Topic by mvandekorput

  • mvandekorput
  • Member
  • Offline
  • From: The Netherlands
  • Registered: 2022-11-23
  • Posts: 5

Topic: Upgrade from 1.7.1 to 1.7.2 fail2ban_banned_db script (error 404)

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release):
- Deployed with iRedMail Easy or the downloadable installer?
- Linux/BSD distribution name and version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
Hi,

I followed the instructions to upgrade my 1.7.1 installation to 1.7.2. All good except for the "Fixed: incorrect sql column name in Fail2ban script" part. When I launch the command to get the corrected fail2ban_banned_db script I get a 404 error. Where can I find this updated script?

Thanks in advance for your help!

Kind regards,
Marty

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by mvandekorput

  • mvandekorput
  • Member
  • Offline
  • From: The Netherlands
  • Registered: 2022-11-23
  • Posts: 5

Re: Upgrade from 1.7.1 to 1.7.2 fail2ban_banned_db script (error 404)

<UPDATE>

I found the file on github in the following path:
/iredmail/iRedMail/blob/master/samples/fail2ban/bin/fail2ban_banned_db

But when I use that script, I get the following error messages (every minute):
/usr/local/bin/fail2ban_banned_db: line 7: syntax error near unexpected token `newline'
/usr/local/bin/fail2ban_banned_db: line 7: `<!DOCTYPE html>'

mvandekorput wrote:

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release):
- Deployed with iRedMail Easy or the downloadable installer?
- Linux/BSD distribution name and version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
Hi,

I followed the instructions to upgrade my 1.7.1 installation to 1.7.2. All good except for the "Fixed: incorrect sql column name in Fail2ban script" part. When I launch the command to get the corrected fail2ban_banned_db script I get a 404 error. Where can I find this updated script?

Thanks in advance for your help!

Kind regards,
Marty

3 Reply by dice

  • dice
  • Member
  • Offline
  • Registered: 2024-08-04
  • Posts: 2

Re: Upgrade from 1.7.1 to 1.7.2 fail2ban_banned_db script (error 404)

I also had this issue and came to the same conclusion and also nginx didnt like "host not found in "PH_PORT_HTTP" of the "listen" directive in /etc/nginx/sites-enabled/00-defaults.conf:7" and nginx refused to start on my Debian 12 server (I should've read the new contents instead of blindly copy pasting, easy 2 second fix at least).

4 Reply by Neovana (edited by Neovana Today 07:44:08)

  • Neovana
  • Member
  • Offline
  • Registered: 2023-05-10
  • Posts: 26

Re: Upgrade from 1.7.1 to 1.7.2 fail2ban_banned_db script (error 404)

This link worked for me:

https://raw.githubusercontent.com/iredm … _banned_db

Except fail2ban fails to load with errors on OpenBSD 7.6. See my other thread in this section with other issues.

I'd avoid upgrading to 1.7.2 until it is official.

5 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,163

Re: Upgrade from 1.7.1 to 1.7.2 fail2ban_banned_db script (error 404)

I didn't announce iRedMail-1.7.2 yet, you guys are ahead of me. sad

dice wrote:

I also had this issue and came to the same conclusion and also nginx didnt like "host not found in "PH_PORT_HTTP" of the "listen" directive in /etc/nginx/sites-enabled/00-defaults.conf:7" and nginx refused to start on my Debian 12 server (I should've read the new contents instead of blindly copy pasting, easy 2 second fix at least).

Fixed the doc moment ago. Please replace "PH_PORT_HTTP" by "80" (without quotes) in /etc/nginx/sites-enabled/00-default.conf, then restart nginx service.

6 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,163

Re: Upgrade from 1.7.1 to 1.7.2 fail2ban_banned_db script (error 404)

Neovana wrote:

Except fail2ban fails to load with errors on OpenBSD 7.6. See my other thread in this section with other issues.

Fail2ban has a critical issue on OpenBSD 7.6, could you help test it on a amd64 box?
https://github.com/fail2ban/fail2ban/issues/3923

7 Reply by Neovana

  • Neovana
  • Member
  • Offline
  • Registered: 2023-05-10
  • Posts: 26

Re: Upgrade from 1.7.1 to 1.7.2 fail2ban_banned_db script (error 404)

ZhangHuangbin wrote:
Neovana wrote:

Except fail2ban fails to load with errors on OpenBSD 7.6. See my other thread in this section with other issues.

Fail2ban has a critical issue on OpenBSD 7.6, could you help test it on a amd64 box?
https://github.com/fail2ban/fail2ban/issues/3923

My iRedMail install is running on OpenBSD 7.6 in a proxmox vm on a cluster of Intel N100 PCs ✅

Please let me know what you'd like for me to do to test it.

8 Reply by Neovana (edited by Neovana Today 09:16:14)

  • Neovana
  • Member
  • Offline
  • Registered: 2023-05-10
  • Posts: 26

Re: Upgrade from 1.7.1 to 1.7.2 fail2ban_banned_db script (error 404)

ZhangHuangbin wrote:

I didn't announce iRedMail-1.7.2 yet, you guys are ahead of me. sad

We are beta testing for you! smile

9 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,163

Re: Upgrade from 1.7.1 to 1.7.2 fail2ban_banned_db script (error 404)

Neovana wrote:

My iRedMail install is running on OpenBSD 7.6 in a proxmox vm on a cluster of Intel N100 PCs ✅
Please let me know what you'd like for me to do to test it.

Cool.

I reported the Fail2ban issue upstream:
https://github.com/fail2ban/fail2ban/issues/3923

The issue is, if i start fail2ban service on OpenBSD 7.6 (arm64) with "rcctl start fail2ban", it starts fail2ban itself but not any jails. If i start it with "fail2ban-client -x start", it starts itself and all jails, but the result is not always same, it may not start any jails too.

In /etc/rc.d/fail2ban, fail2ban is ran by "fail2ban-client -x start" too, so i don't see any difference between 2 commands myself.

I wonder whether it occurs on OpenBSD 7.6 AMD64 / x86_64 too. The steps are simple:

1) Download the latest iRedMail git version and install it on a fresh OpenBSD 7.6 (amd64) box:
https://github.com/iredmail/iRedMail/ar … master.zip

2) Check whether fail2ban starts itself and all jails after system reboot.
3) If not, run "fail2ban-client -x start" to check whether it starts fail2ban daemon and all jails.

It behaves inconsistent, i'm so confused and cannot finish the unit tests.