While login to webmail.domain.com or cpanel.domain.com sometime you may get an error in Litespeed servers:

“A network error occurred while sending your login request. Please try again. If this condition persists, contact your network service provider.”

The problem seems to be that Litespeed is not correctly proxying the https://cpanel.<domain> requests to thecpanelbackend. It is an issue between LiteSpeed and the latest version ofcPanel, preventing thehttpsbackendproxying from working correctly.

Temporary Fix

Comment out the HTTPS rewrite rules from /usr/local/apache/conf/httpd.conf

# RewriteCond %{HTTP_HOST}!^serverhostname$

# RewriteCond %{HTTP_HOST} ^cpanel\.

# RewriteCond %{HTTPS} on

# RewriteRule ^/(.*) https://127.0.0.1:2083/$1 [P]

# RewriteCond %{HTTP_HOST}!^serverhostname$

# RewriteCond %{HTTP_HOST} ^webmail\.

# RewriteCond %{HTTPS} on

# RewriteRule ^/(.*) https://127.0.0.1:2096/$1 [P]

# RewriteCond %{HTTP_HOST}!^serverhostname$

# RewriteCond %{HTTP_HOST} ^whm\.

# RewriteCond %{HTTPS} on

# RewriteRule ^/(.*) https://127.0.0.1:2087/$1 [P]

# RewriteCond %{HTTP_HOST}!^serverhostname$

# RewriteCond %{HTTP_HOST} ^webdisk\.

# RewriteCond %{HTTPS} on

# RewriteRule ^/(.*) https://127.0.0.1:2078/$1 [P]

If thehttpd.conffile is rebuilt, the changes will probably be gone. So whenever thehtppd.confis rebuilt you need to manually comment out the entries.

Permanent Fix

LiteSpeedhas fixed the bug without increasing the version number, so a manual reinstall of the latest version fixes the problem.

[your_litespeed_install_dir]admin/misc/lsup.sh -f

/usr/local/lsws/admin/misc/lsup.sh -f