Category: Common Fixes

In recent updates, cPanel has modified some of the notification settings for their control panel. As a result, you may find that the priority of certain notification types have changed and you may begin to receive notifications that you previously had not encountered. In particular, the notification options for Security Advisor changed with the release of WHM 56 on April 26, 2016.

Are you unable to connect to your cPanel based VPS server  or dedicated server to send or receive email, log into cPanel or WHM, or make an FTP or SSH connection? Are you able to view your website in your browser? If not, and the connection simply times out, it's possible that your IP address has been blocked by the dedicated server’s firewall. Typically, this is the result of too many failed logins (through cPanel, SSH, FTP, email, etc.) in too short a period of time.

As you might expect, most support requests on managed cPanel servers fall into a few basic categories. What you might be surprised to discover is that many common problems can be resolved by following a few simple steps.

CSF (or Config Server Firewall) offers several advantages over the APF (Advanced Policy Firewall), including more robust protection against Denial of Service, SYN flood and other common attacks. One of its most appealing features is its plugin for WebHost Manager that allows you to quickly access firewall settings and common tasks through a graphical interface.

Should you discover (or suspect) that a client or customer’s IP address has been blocked in the firewall, or you just need to open (or close) a port on your cPanel server, you may be able to quickly resolve the issue yourself if you have access to WebHost Manager and the ConfigServer Firewall (CSF).

Solving the Error: 500 OOPS: priv_sock_get_cmd issue

This error may occur when attempting to connect to a VsFTPD FTP server. You simply need to add one line to the configuration file, which this article assumes is in the default location of /etc/vsftpd/vsftpd.conf.

• These instructions are intended specifically for solving the error: Failed to connect to ‘127.0.0.1:7199’: Connection refused.
• I’ll be working from both Liquid Web Core Managed CentOS 6 and CentOS 7 servers, and I’ll be logged in as root.

• These instructions are intended specifically for solving the error: (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
• I’ll be working from both Liquid Web Core Managed Ubuntu 12.04 LTS and 14.04 LTS servers, and I’ll be logged in as root.

• These instructions are intended specifically for solving the error: /usr/sbin/ifconfig: No such file or directory
• I’ll be working from a Liquid Web Self Managed CentOS 7 server, and I’ll be logged in as root.

One component of Liquid Web’s Server Secure service is an Apache module called Mod Security (often shortened to just “modsec”). Modsec monitors all incoming HTTP requests for malicious behavior and does not complete requests that meet certain criteria. These criteria are spelled out in what are called “rules” or “rulesets”.