Skip to content

Disabling TLS 1.0 and 1.1 on cPanel — the careful plan

A 14-day plan for retiring TLS 1.0 and 1.1 on a cPanel server, including the client audit step that prevents surprise customer outages.

Every PCI scan flags TLS 1.0 and 1.1. Every operator wants to turn them off. What stops the change is the fear of breaking the one customer running Windows XP, or the payment terminal in a depot somewhere that has not been updated since 2014. The careful plan replaces fear with evidence.

What’s happening

cPanel’s defaults still allow TLS 1.0 and 1.1 on most installs. Modern browsers refuse to use them anyway, but some embedded clients, legacy POS devices, and old desktop email clients (Outlook 2007, anything pre-IE8) negotiate down to 1.0 if the server allows. Disabling 1.0 and 1.1 will be invisible to 99% of traffic and break the remaining 1% loudly.

How to verify

grep -E "(SSLProtocol|SSL_protocol)" /etc/apache2/conf/httpd.conf
grep -r "TLSv1" /usr/local/cpanel/Whostmgr/Cpanel/Apache/SSL.pm 2>/dev/null
awk '/access_log/ {gsub(/.*"|".*/,"",$0); print}' /etc/apache2/logs/access_log 2>/dev/null | head
ssh-keyscan -p 443 example.com 2>&1
nmap --script ssl-enum-ciphers -p 443 example.com 2>&1 | grep -E "TLSv1\.[01]"

The harder data comes from access logs. If your Apache logs the negotiated protocol (custom log format), you can count how many TLS 1.0/1.1 connections you serve in a week.

The fix

  1. Day 1: instrument logging. Add the negotiated protocol to the access log: LogFormat "%h %l %u %t \"%r\" %>s %b %{SSL_PROTOCOL}x" and reload Apache. Wait one week.
  2. Day 7: audit. Count TLS 1.0 and 1.1 connections per day, per User-Agent, per source IP. Identify whether it is junk traffic (bots) or real customers (consistent IPs, identifiable UAs).
  3. Day 7–10: notify real users. If you identified specific customer endpoints (a payment terminal, a partner integration), email them with the deprecation timeline. Generic bot traffic does not need notification.
  4. Day 10: disable TLS 1.0. WHM > Apache Configuration > Global Configuration > SSL/TLS Protocols set to TLSv1.1 TLSv1.2 TLSv1.3 (drop TLSv1). Rebuild and restart.
  5. Day 13: disable TLS 1.1. Set to TLSv1.2 TLSv1.3. Rebuild and restart.
  6. Day 14: confirm. Re-run nmap --script ssl-enum-ciphers. No TLSv1.0 or TLSv1.1 lines should appear.
  7. Communicate: most customers will not notice. The few who do should already have been warned in step 3.

Stack Harbor handles TLS retirements as part of cPanel/WHM management.