GUI Fail2ban not working

VitalPBX Community Support General Discussion GUI Fail2ban not working

  • Post
    DannyLarsen
    Participant
    none

    Ver 2.0.0-5

    The Intrusion detection for the GUI login does not block access to the GUI 

    The fail2ban.log shows the incorrect login and the action of being block, the system also sends an email that the ip has been blocked

    However I can still login from the blocked IP 

    Firewall and Intrution Detection are both enabled

    Am I missing something?

    Thank you

    0
Viewing 12 replies - 16 through 27 (of 27 total)
  • Replies
    DannyLarsen
    Participant
    none
    Up
    0
    Down

    OK I have done those items

    The result is

    “No file is currently monitored”

    0
    Up
    0
    Down

    I just installed from scratch in a VPS , and is banning correctly.

    Did you install for scratch your VPS or did you upgrade from another version of VPBX?

    0
    DannyLarsen
    Participant
    none
    Up
    0
    Down

    I used this link from the forum on how to install on vps

    “”This is the script for install in a VPS

    https://goo.gl/GPmzFN

    Do you have any issue with the script above?””

     

    Then I updated using the update link on the gui

    0
    DannyLarsen
    Participant
    none
    Up
    0
    Down

    Here is some info from the fail2ban.log the firewall is blocking correctly just not fail2ban

    2018-03-15 10:47:06,559 fail2ban.actions [13977]: ERROR Failed to start jail ‘vitalpbx-gui’ action ‘firewallcmd-ipset’: Error starting action
    2018-03-15 10:47:06,867 fail2ban.action [13977]: ERROR ipset create fail2ban-asterisk-udp hash:ip timeout 600
    firewall-cmd –direct –add-rule ipv4 filter ombu_fail2ban 0 -m set –match-set fail2ban-asterisk-udp src -j REJECT –reject-with icmp-port-unreachable — stdout: ”
    2018-03-15 10:47:06,868 fail2ban.action [13977]: ERROR ipset create fail2ban-asterisk-udp hash:ip timeout 600
    firewall-cmd –direct –add-rule ipv4 filter ombu_fail2ban 0 -m set –match-set fail2ban-asterisk-udp src -j REJECT –reject-with icmp-port-unreachable — stderr: ‘ipset v6.29: Kernel error received: Operation not permittednx1b[91mError: COMMAND_FAILEDx1b[00mn’
    2018-03-15 10:47:06,869 fail2ban.action [13977]: ERROR ipset create fail2ban-asterisk-udp hash:ip timeout 600
    firewall-cmd –direct –add-rule ipv4 filter ombu_fail2ban 0 -m set –match-set fail2ban-asterisk-udp src -j REJECT –reject-with icmp-port-unreachable — returned 13
    2018-03-15 10:47:06,869 fail2ban.actions [13977]: ERROR Failed to start jail ‘asterisk’ action ‘firewallcmd-ipset-udp’: Error starting action
    2018-03-15 10:47:08,072 fail2ban.server [13977]: INFO Jail vitalpbx-gui is not a FileFilter instance

    0
    Up
    0
    Down

    Try the following

    yum update selinux-policy* systemd-python

    at the end, reinstall fail2ban

    yum reinstall fail2ban

    Post the output of the following command after made all the procedures:

    fail2ban-client get vitalpbx-gui logpath
    0
    DannyLarsen
    Participant
    none
    Up
    0
    Down

    “No file is currently monitored”

    It looks like SELinux is disabled

    setenforce 0 

    returns 

    setenforce: SELinux is disabled

     

    0
    Up
    0
    Down

    Well, maybe your VPS doesn’t support ipset.

    0
    DannyLarsen
    Participant
    none
    Up
    0
    Down

    Not sure 

    ipset version   returns

    ipset v6.29, protocol version: 6

    0
    Up
    0
    Down

    Are you using OpenVZ Linux VPS?

    0
    DannyLarsen
    Participant
    none
    Up
    0
    Down

    OpenVZ

    0
    Up
    0
    Down

    VitalPBX is not working with OpenVZ based VPS, please, use KVM based VPS.

    Due OpenVZ share the kernel and system files with the other users on the node and the host it’s self, you are not able to modify the Kernel in any possible way, so, some applications like fail2ban does will not work as expected.

    Sorry for the inconvenience.

    0
    DannyLarsen
    Participant
    none
    Up
    0
    Down

    OK sorry for the problem, thank you for all your help

    0
Viewing 12 replies - 16 through 27 (of 27 total)
  • You must be logged in to reply to this topic.