How to enable cPanel / WHM /webmail after enabling firewall in Virtuozzo
By default, cPanel’s and WHM’s ports are closed for Virtuozzo. We will need to open them using SSH.
As root, run the following commands:
/sbin/iptables -A VZ_INPUT -p tcp -m tcp –dport 2082 -j ACCEPT
/sbin/iptables -A VZ_INPUT -p tcp -m tcp –dport 2083 -j ACCEPT
/sbin/iptables -A VZ_INPUT -p tcp -m tcp –dport 2086 -j ACCEPT
/sbin/iptables -A VZ_INPUT -p tcp -m tcp –dport 2087 -j ACCEPT
/sbin/iptables -A VZ_INPUT -p tcp -m tcp –dport 2095 -j ACCEPT
/sbin/iptables -A VZ_INPUT -p tcp -m tcp –dport 2096 -j ACCEPT
This will opens cPanel with and without SSL, and WHM with and without SSL and webmail ports.
To save the firewall changes, use the following:
/etc/rc.d/init.d/iptables save
To see the firewall rules, type
cPanel VPS Account Creation [an error occurred while processing this directive]
Problem to create a new account on cPanel VPS server.
Create a new Account
[an error occurred while processing this directive] Notification => root@server.net via EMAIL [level => 3]
Account Creation
We need to find out what Cpanel error logs shows
#tail -f /usr/local/cpanel/logs/error_log
edquota: Cannot set quota for user 543 from kernel on /dev/vzfs: No such process
edquota: Can’t write quota for 543 on /dev/vzfs: No such process
To resolve this: We need to raise the quotagidlimit from the resource tab on the hardware node.
Building the Apache Configuration File in WHM
The build process begins by distilling and recording Apache’s current configuration. The build time options you configured during the EasyApache setup are used to begin building the configuration.
Option modules such as mod_security are installed, and their corresponding modifications are made to the new Apache configuration file.
A new, assumedly valid Apache configuration file will exist in the configuration directory.
Directives added to the final Apache configuration file as defaults have been removed at this point.
No VirtualHost entries exist in the configuration file at this point.
The new configuration is distilled in much the same way as before; however, this time the configuration is used as the basis for creating the server’s main Apache configuration template.
New directives and values are stored.
Any directives and values held over from the previous configuration will retain their values from that configuration.
The combination of the main template and data stores will be the basis for regenerating the final configuration file.
Finally, the new Apache configuration file is generated from the template and data stores and checked for syntactical correctness.
If the new file passes the test, the process is complete.
If the file fails the syntax check, the previous Apache configuration is restored.
Reference: http://cpanel.net
