[phpBB Debug] PHP Notice: in file [ROOT]/includes/functions_content.php on line 77: Array to string conversion
[phpBB Debug] PHP Notice: in file [ROOT]/includes/functions_content.php on line 77: Undefined variable: Array
[phpBB Debug] PHP Notice: in file [ROOT]/includes/functions_content.php on line 77: Array to string conversion
[phpBB Debug] PHP Notice: in file [ROOT]/includes/functions_content.php on line 77: Undefined variable: Array
[phpBB Debug] PHP Notice: in file [ROOT]/includes/functions_content.php on line 77: Array to string conversion
[phpBB Debug] PHP Notice: in file [ROOT]/includes/functions_content.php on line 77: Undefined variable: Array
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4781: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3907)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4783: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3907)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4784: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3907)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4785: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3907)
forum.blocklist.de • View topic - Fail2ban with the example-Config from blocklist

  • Advertisement

Fail2ban with the example-Config from blocklist

Fail2ban with the example-Config from blocklist

Postby Martin » 21. May 2011, 23:50

Mfg Martin
http://www.blocklist.de/de/ Fail2Ban Reporting Service
User avatar
Martin
 
Posts: 397
Joined: 14. Sep 2010, 11:54

Re: Fail2ban with the example-Config from blocklist

Postby krossekrabbe1 » 17. Sep 2015, 11:18

Now I have to reconfigure my fail2ban installation. You should put a

BIG FAT WARNING THAT fail2ban.config.tar.gz CONTAINS THE jail2ban.conf AND jail.conf, SO YOURS WILL GET OVERRIDDEN!
krossekrabbe1
 
Posts: 1
Joined: 17. Sep 2015, 11:15

Re: Fail2ban with the example-Config from blocklist

Postby Martin » 17. Sep 2015, 13:18

Hi,

yes, this howto is for the first installation.
Otherwise you can under step 2 before you copy all Files, the not needed files deleting.
Mfg Martin
http://www.blocklist.de/de/ Fail2Ban Reporting Service
User avatar
Martin
 
Posts: 397
Joined: 14. Sep 2010, 11:54

Re: Fail2ban with the example-Config from blocklist

Postby firefox1991 » 18. May 2016, 14:40

I have ubutu server 16.4, after i do all proceed and restart fail2ban it send me error
firefox1991
 
Posts: 2
Joined: 18. May 2016, 02:52

Re: Fail2ban with the example-Config from blocklist

Postby Martin » 18. May 2016, 14:52

Hello firefox1991, have set the Loglevel in /etc/fail2ban/fail2ban.conf up to level 4 (debug) and then, restart Fail2ban.
Which errors do you get from fail2ban? Can you paste it?
Mfg Martin
http://www.blocklist.de/de/ Fail2Ban Reporting Service
User avatar
Martin
 
Posts: 397
Joined: 14. Sep 2010, 11:54

Re: Fail2ban with the example-Config from blocklist

Postby firefox1991 » 31. May 2016, 05:15

root@server:/etc/fail2ban# sudo service fail2ban restart
Job for fail2ban.service failed because the control process exited with error code. See "systemctl status fail2ban.service" and "journalctl -xe" for details.
root@server:/etc/fail2ban#

● fail2ban.service - Fail2Ban Service
Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: exit-code) since lun 2016-05-30 23:16:45 EST; 2s ago
Docs: man:fail2ban(1)
Process: 3352 ExecStop=/usr/bin/fail2ban-client stop (code=exited, status=0/SUCCESS)
Process: 3565 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=255)
Main PID: 2839 (code=killed, signal=TERM)

may 30 23:16:44 server systemd[1]: fail2ban.service: Unit entered failed state.
may 30 23:16:44 server systemd[1]: fail2ban.service: Failed with result 'exit-code'.
may 30 23:16:45 server systemd[1]: fail2ban.service: Service hold-off time over, scheduling restart.
may 30 23:16:45 server systemd[1]: Stopped Fail2Ban Service.
may 30 23:16:45 server systemd[1]: fail2ban.service: Start request repeated too quickly.
may 30 23:16:45 server systemd[1]: Failed to start Fail2Ban Service.
root@server:/etc/fail2ban#
firefox1991
 
Posts: 2
Joined: 18. May 2016, 02:52

Re: Fail2ban with the example-Config from blocklist

Postby Martin » 17. Jun 2016, 13:26

Hi,

a workarround is to insert in the fail2ban-client.pl-Skript after stop a:
time.sleep()

1. File /usr/bin/fail2ban-client open in a Text-Editor.
2. Search for the Function "__processCMD()". Add a "time.sleep()" at start of the first while/loop.

viewtopic.php?p=174#p174
Mfg Martin
http://www.blocklist.de/de/ Fail2Ban Reporting Service
User avatar
Martin
 
Posts: 397
Joined: 14. Sep 2010, 11:54

Re: Fail2ban with the example-Config from blocklist

Postby Flashtek » 4. Mar 2017, 20:37

Is this still a valid way to configure fail2ban with blocklists.de in Debian given that there seems to be some config items in the shipped jail.conf to cater for blocklist.de ?

I had some issues when trying to use this config, as well as the Debian provided one (rather confused about that) to log things here.
Flashtek
 
Posts: 1
Joined: 4. Mar 2017, 17:28

Re: Fail2ban with the example-Config from blocklist

Postby Martin » 4. Mar 2017, 21:17

Hi @Flashtek,

in the latest Version, you have already a blocklist.de-Conf and can send the Attacks over the http-Api to us.
I think the fasted way is to use the source from fail2ban: https://github.com/fail2ban/fail2ban/releases

Then you need only to add:
blocklist_de_apikey = yourapi-key-from-blocklist.de-profile

and update the sender to the same-emailadresse which do you set in your blocklist.de-profile for the server.

And then, change:
action = %(action_)s
to:
action = %(action_blocklist_de)s

and restart.
Mfg Martin
http://www.blocklist.de/de/ Fail2Ban Reporting Service
User avatar
Martin
 
Posts: 397
Joined: 14. Sep 2010, 11:54


Return to Howtos

Who is online

Users browsing this forum: No registered users and 1 guest

  • Advertisement
cron
figurative