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 403 error, but just to be safe, you should rule that out first thing by checking whether the error occurs with Apache as well. Have you checked your log files? They usually show you the cause of the error!Įrror 403 Forbidden can be triggered by many things, including permission issues, configuration restrictions, security settings, etc. LiteSpeed Memcached LiteSpeed Memcached. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |