Proactive methods of securing servers include adding services like Imunify360.
It protects both Linux hosting providers and their customers from attackers.
However, sometimes it doesn’t work as we expect and may cause umask and permission errors in Cloudlinux servers.
At Bobcares, we often get requests from our customers to fix Imunify360 config errors as part of our Server Management Services.
Today, we’ll see how our Support Engineers fixed Imunify360 umask error in a CloudLinux server.
A word on imunify360
Imunify360 is the next-generation security solution that helps the server owners to protect the server from malicious attacks.
It has tremendous features to avoid security threats. Also, the features are manageable from a single interface.
Moreover, it provides complete security from threats, such as known and unknown malware, and distributed brute force attacks, the most common type of web server attack.
It has additional features such as Reputation Management and an Advanced Captcha system for checking website visitors.
The features of imunify360 include,
- It identifies the whole security threats by analyzing the web traffic that hits the servers and web application scripts.
- Machine learning technology and extensive, signature-based algorithms have used to identify abnormal behavior patterns.
- The Proactive Defense feature assures zero-day attacks.
- Automatically secures the kernel and older PHP versions.
Luckily, Imunify360 is a common multi-layered web server security platform used in cPanel, Plesk, and DirectAdmin. An Imunify360 integrated WHM panel shows up as:
What is umask?
Let’s now check more on umask.
Umask helps to create files or directory with a default set of permissions when the user creates a file or directory under Linux or UNIX.
Also, it allows controlling the default file permission for new files. Again, if a file has 666 permissions, it allows read and write permission to everyone.
To set the umask 077 type, we use the following command.
How we fixed Imunify360 umask related errors
At Bobcares, where we have more than a decade of expertise in managing servers, we see many customers face problems with the Imunify360 misconfiguration.
Now, let’s see the major reasons for the imunify360 related errors and how our Support Engineers fix this error.
1. Imunify360 umask broken
Recently, one of our customers had a problem with his imunify360 on CloudLinux servers. His WordPress didn’t work once he updated the Imunify360 on the server.
On checking, our Support Engineers found that the permission of files was incorrect. By further investigation, we found that the umask of new files created in WordPress gets wrong.
Unfortunately, the umask broke when the client updated the Imunify360.
Therefore, we had to remount cageFS by using the following command.
That’s it. We solved the error
2. Database connection failures
Similarly, many customers reported us with an issue with MySQL connections from various web scripts. The symptoms include slow loading websites, frequent HTTP 500 errors, and MySQL connection-related errors.
Then, our Support Engineers solved this issue by taking the below steps.
1. First, we logged into the backend command utility yum
yum clean all yum update imunify360-php-i360
2. After updating, we restarted Apache and PHP services.
3. Then we disabled the Proactive Defense feature of Imunify360 temporarily.
4. Finally, deactivated and activate cagefs.
/usr/sbin/cagefsctl --disable-all /usr/sbin/cagefsctl --enable-all
[Need assistance to fix imunify360 related errors? We’ll help you.]
In short, imunify360 is a common multi-layered web server security platform to protect the server from malicious attacks. Imunify360 umask broken can be fixed by remounting the cageFS on the server. Today, we saw how our Support Engineers fixed Imunify360 related errors.