Skip to content

cPanel / WHM

Supporter Operating systems

  • Ubuntu
  • CloudLinux
  • RockyLinux

  • AlmaLinux OS

  • Matrix of supporter cPanel versions and Operating Systems Matrix

CloudLinux Integration

  • Allocates max processes, CPUs, RAM, bandwidth, IO, IOPS, inodes

  • Controls MySQL usage with MySQL Governor

  • Allows for more users per server

  • Provides greater stability

  • LVE Manage by going to WHM Home >> Server Configuration >> CloudLinux LVE Manager.

  • Server Profiles - WHM Home >> Server Configuration >> Server Profile.

Roles and Services

  1. Calendars and contacts - Module: CalendarContacts - Service: cpdavd
  2. DNS - Module: DNS Services: bind,named,nsd,pdns,powerdns,
  3. File Storage - Module: FileStorage , No service available
  4. FTP - Module: FTP , Service: ftpd, pureftp,proftp
  5. MySQL/MariaDB Module: MySQL , Service: mysql
  6. PostgreSQl Module: Postgres, Service postgresql
  7. Receive Mail Module: MailReceive , Service: cpanel_dovecot_solr, cpdavd, cpgreylistd, dovecot, imap, mailman, pop
  8. Relay Mail Module: MailRelay , Service: exim,exim-altport
  9. Send Mail Module: MailSend, exim,exim-altport
  10. Spam Filter Module: SpamFilter , Service: spamd
  11. Webmail , Module: Webmail , no service
  12. Web Disk , Module WebDisk, Service: cpdavd
  13. Web Server , Module WebServer , Service: httpd
  14. Local Mail , MailLocal , Service: exim, dovecot

File structure of /usr/local/cpanel

Important Directories

  • 3rdparty /usr/local/cpanel/perl
    • Holding Data files for 3rdparty applications
  • base /usr/local/cpanel/base
    • Holding base files for the main cpanel/whm URL 'http://url.com:2087'

  • bin - executables

  • /usr/local/cpanel/Cpanel and /usr/local/cpanel/Whostmgr

  • These folders store our back-end perl modules, mirroring the module names with the path.

  • Logs /usr/local/cpanel/logs/

  • /usr/local/cpanel/logs/error_log - cPanel error log

  • Same for access log in the same location

  • named logs /var/log/named/named.log.

File structure /var/cpanel

  • cpanel.config - Tweak Settings file

  • userdata folder - stores each accounts virtualhost information - VHOST /var/cpanel/userdata Virtual Host location

  • templates - stores apache and dovecot configuration tempaltes

  • databases - Within this folder are several files, primarily in JSON or YAML format. These store the database mapping data used to tie MySQL/MariaDB databases to specific accounts with specific permissions and grants.

Check ServiceD chkservd

  • Documentation DOC

  • Service manager and TailWatch - tailwatchd service

  • DOCS

Troubleshooting License issues

  • /usr/local/cpanel/cpkeyclt DOC

Clustering

DNS Clustering

  • Clusters must include at least two servers.

  • You must have at least one web server with cPanel & WHM installed.

  • A DNS cluster that includes multiple cPanel DNSOnly™ servers and cPanel & WHM servers is also acceptable.

  • All machines in the DNS cluster must have cPanel & WHM or cPanel DNSOnly version 11 or higher installed.

  • Some features may not work with older versions of cPanel & WHM

DNS CLUSTER

DNS Cluster GUIDEw

Brute Force Protection

Scope Of support

  • CloudLinux Support Range

What components of the CloudLinux product do we support as part of our CloudLinux Support?

  • Failure of any CL component to work as expected (stats not working, lvetop showing wrong data, lve not working, etc.)

  • Kernel not booting due to kernel installation/kernel installations

  • Server crashes

  • Bad performance issues (we investigate/see if it is CL-related or not, and if it can be handled by CL)

  • RPM conflicts

  • PHP Selector

  • If any module that we bundle with alt-php doesn't work, we would investigate it/fix it (if possible)

  • CageFS - If software works outside CageFS/doesn't work inside CageFS

Hacked Server Guidelines

Check compromised server via CSI script 

/usr/local/cpanel/3rdparty/bin/perl <(curl -s https://raw.githubusercontent.com/cPanelTechs/CSI/master/csi.pl)

## Ticket Handling

  1. Already assigned tickets if none are present Emergencies!
  2. Scheduled Tasks
  3. Ultra Priority (Priority: Urgent)
  4. Enterprise Priority (Priority: High)
  5. Priority (Priority: Normal)
  6. Standard (Priority: Low)
  7. Complimentary (Priority: Low)

cPanel Zendesk

Emergency Urgent

Ultra Priority High

Enterprise Priority Normal

Priority, Standard, Low Complimentary

Safety Protocols

SOURCE

Accessing Customers servers

Transfers & Escalations

  • ctrl + opt + m to enter the dropdown.

Product domains

Changes to the Product Domain field must be done before it closes:
A ticket becomes immutable once it is closed, so changes cannot be made then.

Account Administration

Backups

Databases

Developer Experience

Domain Management

Email

File Management

Hyperscalers

Internal DevOps Pipeline

Installations & Updates

Licensing & Billing

Operating Systems

Product Extensions

Security

Server Management

Site Performance Analytics

Transfers

User Experience

Web Servers and Applications

Hello, Thank you for contacting cPanel Technical Support . My name is Vladimir and I will be reviewing your request.

I see that you have imported your server information , however there seems to be an issue with the access to the server.

Each reply to the customer should include the following:

  1. An initial greeting
  2. Investigation steps and/or logs reviewed or a request for more information
  3. Steps to resolve the issue, if any
  4. Any follow-up information, such as links to documentation, deflection articles, defect articles, or JIRA cases
  5. Closure (Does the customer require any further assistance? Is the issue now resolved?)