Check the phpinfo page of the problematic user account.$ sudo touch /usr/local/lsws/admin/tmp/.lsphp_restart.txtīefore engaging us for Premium Support service, you may like to try a few of these simple steps to see if you can fix the error yourself: Switch back to LiteSpeed Web Server, and keep reading! Even though it is not a server problem, we have provided the following troubleshooting documentation that we hope will help you to find the solution. If Apache experiences the same problems, then the issue is not a LiteSpeed Web Server issue. Please open a ticket from your client area or email and provide as many details as possible, so that we may assist you.

If the error could not be triggered under Apache, then the problem is likely to be a LiteSpeed server issue.

Repeat the steps that originally led to the issue.Īre you able to reproduce the error under Apache? NO ¶.

If your server is running on an Apache control panel, such as cPanel or Plesk, there is an easy way to determine whether an issue is caused by your LiteSpeed server:

It is rare for the web server to be the cause of a 503 error, but just to be safe, you should rule that out first thing by checking whether the error occurs with Apache as well. LiteSpeed Memcached LiteSpeed Memcachedĥ03 errors are often caused by a malfunction in PHP.LSCache Developers Guide LSCache Developers Guide.LSCache Without a Plugin LSCache Without a Plugin.WHM LiteSpeed Plugin WHM LiteSpeed Plugin.

External Applications External Applications.

LiteSpeed Web Server LiteSpeed Web Server.

Signal messenger 503 error