Documentation Installation Guide
Requirements
Operating system
- CentOS/RHEL 6 and 7
- CloudLinux OS 6 and 7
- Ubuntu 16.04 LTS only
- Ubuntu 18.04
- CentOS 8 with Plesk
- CentOS 8 with DirectAdmin
- CentOS 8 as stand-alone
- CloudLinux OS 8 with DirectAdmin
- CloudLinux OS 8 as stand-alone
Virtualization
OpenVZ - works for Virtuozzo 7 with kernel 3.10.0-327.10.1.vz7.12.8 or newer.
Hardware
- RAM: 1Gb
- HDD: 20Gb available disk space
Supported hosting panels
- cPanel
- Plesk (Plesk 12.5 is not supported)
- DirectAdmin
- No hosting panel systems
Required browsers
- Safari version 10 or later
- Chrome version 39 or later
- Firefox version 28 or later
- Edge version 17 or later
Supported Web-servers
- Apache
- LiteSpeed
Side by side installation with another IDS
Compatible
| IDS name | Comment |
| LiteSpeed | Integrates with version 5.1 or higher. |
| EasyApache3 | Works only in cPanel. |
| EasyApache4 | Works only in cPanel. |
| CSF | Integrated with CSF, more details here. |
| CWAF Agent | No problems detected. |
| Patchman | No problems detected. |
| Suhosin | We are ignoring alerts by Suhosin. |
| Cloudflare | Imunify360 supports graylisting IP addresses behind Cloudflare. More details here. |
| CXS | Special actions required to use Imunify360 with CXS installed. |
| cPHulk | Imunify360 disables cPHulk during installation. However in case of enabling it back, Imunify360 integrates with it and shows cPHulk events in the incident screen. |
| OpenVZ | Works for Virtuozzo 7 with kernel 3.10.0-327.10.1.vz7.12.8 or later. |
| UptimeRobot | No problems detected. |
Incompatible
| IDS name | Comment |
| ASL (Atomicorp Secured Linux) | Possibly is not compatible (investigating). |
| fail2ban | Imunify360 disables fail2ban: the latter resets chains of iptables rules which causes inconsistency with Imunify360 |
Installation Instructions
Warning
On DirectAdmin, Imunify UI requires the proc_open PHP function to be enabled. If you are unable to open the Imunify UI, you might see a related message in the web server error log. If so, please remove it from the disable_functions list in php.ini.
Get your license key at https://www.imunify360.com/. You can purchase it or get a trial key from a received email.
Setup or install the prerequisites required for your environment if any.
Log in with root privileges to the server where Imunify360 should be installed.
Go to your home directory and run the commands:
wget https://repo.imunify360.cloudlinux.com/defence360/i360deploy.sh
bash i360deploy.sh --key YOUR_KEY
where YOUR_KEY is your license key. Replace YOUR_KEY with the actual key - trial or purchased at https://www.imunify360.com/ .
To install Imunify360 beta version add argument --beta . For example:
bash i360deploy.sh --key YOUR_KEY --beta
where YOUR_KEY is your license key. Replace YOUR_KEY with the actual key - trial or purchased at https://www.imunify360.com/.
If you have an IP-based license, run the same script with no arguments:
wget https://repo.imunify360.cloudlinux.com/defence360/i360deploy.sh
bash i360deploy.sh
To view available options for installation script run:
bash i360deploy.sh -h
Registering
In a case of registration key is passed later, then you can register an activation key via the Imunify360-agent command:
imunify360-agent register YOUR_KEY
Where YOUR_KEY is your activation key.
If you have IP-based license, you can use the following command:
imunify360-agent register IPL
SELinux support
If SELinux (Security-Enhanced Linux) is enabled on your server, you should install the Imunify360 SELinux policy module. Policy is shipped with Imunify360 package and is located in the /opt/alt/python35/share/imunify360/imunify360.te
To apply it, run the following commands:
checkmodule -M -m -o /var/imunify360/imunify360.mod /opt/alt/python35/share/imunify360/imunify360.te
semodule_package -o /var/imunify360/imunify360.pp -m /var/imunify360/imunify360.mod
semodule -i /var/imunify360/imunify360.pp
After that, restart imunify360 service. For CentOS6/CloudLinux6:
service imunify360 restart
For other systems:
systemctl restart imunify360
Update Instructions
Note
Starting from Imunify360 v.4.10, the updates are unconditionally enabled and the Imunify360 service starts during the package update.
To upgrade Imunify360, run the command:
yum update imunify360-firewall
To update Imunify360 beta version, run the command:
yum update imunify360-firewall --enablerepo=imunify360-testing
To update Imunify360 on Ubuntu, run the command:
apt-get update
apt-get install --only-upgrade imunify360-firewall
To update Imunify360 beta version on Ubuntu 16.04, run the command:
echo 'deb https://repo.imunify360.cloudlinux.com/imunify360/ubuntu-testing/16.04/ xenial main' > /etc/apt/sources.list.d/imunify360-testing.list
apt-get update
apt-get install --only-upgrade imunify360-firewall
To update Imunify360 beta version on Ubuntu 18.04, run the command:
echo 'deb https://repo.imunify360.cloudlinux.com/imunify360/ubuntu-testing/18.04/ bionic main' > /etc/apt/sources.list.d/imunify360-testing.list
apt-get update
apt-get install --only-upgrade imunify360-firewall
If you do not want to receive updates from beta, remove beta repository:
rm /etc/apt/sources.list.d/imunify360-testing.list
apt-get update
Gradual roll-out
New stable Imunify360 versions are scheduled for the gradual roll-out from our production repository and are available for all customers in about two weeks or less from the release.
If you do not want to wait for the gradual roll-out, you can update Imunify360 to the latest version by running the following commands:
wget https://repo.imunify360.cloudlinux.com/defence360/imunify-force-update.sh
bash imunify-force-update.sh
