When going to Fantastico De Luxe link in you cPanel under Paper Lantern theme, or some other theme you might get HTTP error 404 cPanel page shown, saying that requested page was not found.
Check your theme folder content for fantastico symlink
404 page will most likely be caused by the affected theme not having, a fantastico symlink, or symlink being misdirected.
Go to the folder of the theme, which in case of Paper Lantern theme will be /usr/local/cpanel/base/frontend/paper_lantern and check for file with name fantastico.
root@server [/usr/local/cpanel/base/frontend/paper_lantern]# ls -l | grep fantastico
root@server [/usr/local/cpanel/base/frontend/paper_lantern]#
Folder should have symlink in it, with name fantastico, pointing to /usr/local/cpanel/3rdparty/fantastico/, if the symlink is missing create one with ln -s command, also check if the file to which symlink is pointing is an existing file.
There is an issue with CentOS 7 containers on OpenVZ nodes, where NetworkManager service breaks the network, and only localhost 127.0.0.1 network interface is coming up.
When you try to check network interfaces, and IP address on the server, you will only see localhost interface.
When issuing service network restart you will and output like this:
Starting network (via systemctl): Job for network.service failed because the control process exited with error code. See "systemctl status network.service" and "journalctl -xe" for details.
[FAILED]
When you run journalctl -xe you will see errors like this:
-- Unit network.service has begun starting up.
Feb 16 05:16:40 server network[2262]: Bringing up loopback interface: Could not load file '/etc/sysconfig/network-scripts/ifcfg-Feb 16 05:16:40 server network[2262]: Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
Feb 16 05:16:40 server network[2262]: Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
Feb 16 05:16:40 server network[2262]: Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
Feb 16 05:16:40 server network[2262]: [ OK ]
Feb 16 05:16:40 server network[2262]: Bringing up interface venet0: Error: Connection activation failed: No suitable device founFeb 16 05:16:40 server network[2262]: [FAILED]
Feb 16 05:16:40 server network[2262]: RTNETLINK answers: File exists
Feb 16 05:16:40 server network[2262]: RTNETLINK answers: File exists
Feb 16 05:16:40 server network[2262]: RTNETLINK answers: File exists
Feb 16 05:16:40 server network[2262]: RTNETLINK answers: File exists
Feb 16 05:16:40 server network[2262]: RTNETLINK answers: File exists
Feb 16 05:16:40 server network[2262]: RTNETLINK answers: File exists
Feb 16 05:16:40 server network[2262]: RTNETLINK answers: File exists
Feb 16 05:16:40 server network[2262]: RTNETLINK answers: File exists
Feb 16 05:16:40 server network[2262]: RTNETLINK answers: File exists
Feb 16 05:16:40 server systemd[1]: network.service: control process exited, code=exited status=1
Feb 16 05:16:40 server systemd[1]: Failed to start LSB: Bring up/down networking.
-- Subject: Unit network.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit network.service has failed.
--
-- The result is failed.
Feb 16 05:16:40 server systemd[1]: Unit network.service entered failed state.
Feb 16 05:16:40 server systemd[1]: network.service failed.
Feb 16 05:16:40 server polkitd[226]: Unregistered Authentication Agent for unix-process:2257:65393 (system bus name :1.37, object
Issue can be resolved by stopping and disabling the NetworkManager service.
root@server [/]# service NetworkManager stop
Redirecting to /bin/systemctl stop NetworkManager.service
root@server [/]# chkconfig NetworkManager off
On most CentOS 7 machines you might be getting this type of warnings when restarting or updating ConfigServer Firewall (CSF), if you are missing certain commands or packages on your server.
*WARNING* Binary location for [CHATTR] [/usr/bin/chattr] in /etc/csf/csf.conf is either incorrect, is not installed or is not executable
*WARNING* Missing or incorrect binary locations will break csf and lfd functionality
*WARNING* URLGET set to use LWP but perl module is not installed, reverting to HTTP::Tiny
You also might be getting notifications in mail from your Cron Daemon with subject /usr/sbin/csf -u and following message:
*WARNING* URLGET set to use LWP but perl module is not installed, reverting to HTTP::Tiny
This warnings are showing because of missing packages not being installed on the server, and chattr command doesn’t exist.
[root@server ~]# type chattr
-bash: type: chattr: not found
To resolve CHATTR warning, you need to install e2fsprogs with
yum -y install e2fsprogs
To resolve URLGET warning you need to install perl-libwww-perl with
yum -y install perl-libwww-perl with
If you are getting following warning by mail notifications, or when running csf -u, you are missing perl-LWP-Protocol-https package.
[root@server ~]# csf -u
Oops: Unable to download: Protocol scheme 'https' is not supported (LWP::Protocol::https not installed)
Install perl-LWP-Protocol-https with:
yum -y install perl-LWP-Protocol-https
You might also be getting a following warning, if you don’t have host or unzip commands installed on your server.
*WARNING* Binary location for [UNZIP] [/usr/bin/unzip] in /etc/csf/csf.conf is either incorrect, is not installed or is not executable
*WARNING* Binary location for [HOST] [/usr/bin/host] in /etc/csf/csf.conf is either incorrect, is not installed or is not executable
To resolve HOST warning, you needs to install bind-utils package with
yum -y install bind-utils
To resolve UNZIP warning you need to install unzip package with
yum -y install unzip
tl;dr required packages for CSF
If you are getting any kind of warnings when doing csf -r on CentOS 7 server make sure you have following packages installed.
When running yum update on CentOS 7 OpenVZ container you might get a following error:
--> Processing Conflict: systemd-219-19.el7.x86_64 conflicts initscripts < 9.49.28-1
--> Finished Dependency Resolution
Error: systemd conflicts with initscripts-9.49.17-1.el7.x86_64
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Exact version I was running on this server is CentOS Linux release 7.1.1503 (Core), and updates were failing due to them requiring a newer systemd version, which required a newer version, v9.49.28 at least, of initscripts installed.
Reason why systemd was conflicting with current version of initscripts, instead of just updating them to newer version, was that initscripts were excluded from update in yum.conf file.
There are no default exclude packages in default CentOS/RHEL installs, and it wasn’t put there by me, so question is why was initscripts excluded from updates.
Issues with initscripts v9.49.24 in CentOS 7 OpenVZ containers
It turns out there were some issues with initscripts v9.49.24, which seemed to introduce problems with network connectivity on CentOS 7 OpenVZ VPS machines.
If you make an SMTP test on http://mxtoolbox.com you might be getting a following error shown in the test results “Reverse DNS does not match SMTP Banner”.
This error is showing because your SMTP greeting message is not matching the PTR records for the IP of the SMTP server used in test.
Following files need to be used and configured properly, for SMTP banner to match reverse DNS records.
Go to WHM to Home »Service Configuration »Exim Configuration Manager and in Basic Editor on Domains and IPs tab set following settings:
Send mail from account’s dedicated IP address: OFF Reference /etc/mailhelo for outgoing SMTP HELO: ON Reference /etc/mailips for outgoing SMTP connections: ON
Configure necessary values in configuration files
Edit or create /etc/mail_reverse_dnsfile and set the following in it for needed IPs.
x.x.x.x: rdns of the IP x.x.x.x
y.y.y.y: rdns of IP y.y.y.y
Edit or create /etc/mailhelo file and set following in it for the domains that you want to setup SMTP banner for.
example.com: reverse dns of the IP used for example.com domain
*: default SMTP HELO for unconfigured domains
Edit or create /etc/mailips file and set following in it:
example.com: x.x.x.x #x.x.x.x is the IP used for outgoing mail for domain example.com
*: y.y.y.y #y.y.y.y is the default IP that will be used for unconfigured domains
Configure exim.conf to use correct SMTP Banner
Following values need to be configured in exim.conf for SMTP Banner to be set to rDNS values set in /etc/mail_reverse_dns.
smtp_banner will probably look like this on your cPanel server.
"${primary_hostname} ESMTP Exim ${version_number} \#${compile_number} ${tod_full} \n We do not authorize the use of this system to transport unsolicited, \n and/or bulk e-mail."
Configure values in exim.conf over shell
Locate the line smtp_banner and change its value so it looks like following: