Fail2ban won't start after update

(Lorne Gaetz) #34

Repeated attempts to repro this have been unsuccessful for me, but I did have hands on a system just now where fail2ban wouldn’t start. I don’t know the cause but it appears to be related to System Admin module - fail2ban fails to start - fail2ban starts like normal

You can get .66 from the stable repo with:

fwconsole ma upgrade sysadmin

confirm sysadmin version with:

fwconsole ma list | grep sysadmin

start fail2ban

systemctl start fail2ban.service

Confirm it’s running with

systemctl status fail2ban.service

Fail2ban wont start
(Yois) #35


Thanks for this, there’s a typo in the source code (that doesn’t affect functionality)


I have .66 and it still won’t start. unfortunately I can’t reboot the phone system right now as the office is open. I’ll try tonight.

(Jared Busch) #37

So @lgaetz what can be done to fix this? Because until this is fixed, Firewall is a commercial product. No matter what this says…

| firewall  |  | Enabled and up to date   | AGPLv3+     |

(Yois) #38

@sorvani - I’m also slightly frustrated by this fact, but like I said earlier, the ability to do root tasks from the GUI requires some sanity checking and file verification. If you want to make this completely open, it’s only possible if the open-source community can agree on one signing authority… Once we do that why can’t it just be Sangoma?

If anyone wants to create an open-source fork of the firewall module, it’s easy enough to just create a new incron folder that processes the hook files without signature verification, and to drop hook files in that location… But don’t say I didn’t warn you that this is insecure.

(Yois) #39

(Jared Busch) #40

Of course it can be Sangoma. But it has to be done in something that can be installed on all systems, unlike SysAdmin.

(Simon Telephonics) #41

Access control doesn’t have to be done in the kernel.

(Yois) #42

Care to explain? Both iptables and fail2ban require root.

(Simon Telephonics) #43

I’m talking about using ACL functionality in Asterisk. It’s not a drop-in replacement to iptables but it fits better within the paradigm of FreePBX working with asterisk configuration as the asterisk user. Maybe a direction to consider for FreePBX 17.


(Ron) #45

Wanted to add to this thread. Same issue with the GUI indicating Fail2Ban not running, same error codes when attempting to start the service. Same Apache error - ‘filter.d/apache-api’ under /etc/fail2ban ERROR Unable to read the filter ERROR Errors in jail ‘apache-api’. Skipping…

Solution that worked for me on 4 FreePBX 15 was ashcortech in the last update.
Manually running


I’m not trying to be disruptive, but can someone qualify exactly what version of Fail2ban is being deployed? and who wrote the systemd fail2ban.service that is apparently being used to start it?

Last mention of 0.8 is ‘quite a long time ago’


@yois Yes, all current for all modules & OS, all activated, and nothing I do changes the behavior, a few boxes are doing it and others are not.



Note: PBX is 100% Current for OS & Modules
Running: FreePBX
Running: fail2ban-fpbx-0.8.14-76.sng7.noarch
Reboot does nothing to resolve.

First here is a video showing how the GUI reacts:

Error trying to start the server image:

Oput from status was provided above.


If there is an official Sangoma person that would like to remote in to see it for themselves I can work with you to connect to one of the PBX’s with this issue.

(Jared Busch) #50

New system I setup last week. Nothing done yet but testing some export/import stuff in bulk import. Clean install of FreePBX 15 on Vultr, then registered to a PBXact license.

[jbusch@uc-90XXXXXX ~]$ sudo yum list fail2ban
[sudo] password for jbusch: 
Loaded plugins: fastestmirror, versionlock
Loading mirror speeds from cached hostfile
Available Packages
fail2ban.noarch                                              0.11.1-9.el7.2                                               sng-epel
[jbusch@uc-90XXXXXX ~]$ 


Then let’s first make sure first that everyone is on that same page , Fail2ban 0.8 is long gone, 0.11 has it’s own included systemd service file that you can deploy, a cavetae is that it might not behave nicely with any particular ‘firewall’

(Jared Busch) #52

The firewall adds to fail2ban jails.

(Yois) #53

@VoIPTek - Try running