Getting an Error 500 may sound like there is something wrong with the server, but this is actually an error in the WordPress code base – either in the plug-ins, in core, or in the theme. To find out where exactly the error is you can follow any of the steps below. Via...
Troubleshooting
Litespeed application node won’t restart
If you are seeing the same errors as above when trying to restart your Litespeed application node, follow the steps below: 1. On the AppServer level, click on the wrench icon to access Config. Then, navigate to...
How to determine what directories or files are consuming disk space
1. On the AppServer level, open up Web SSH. 2. Start at the root by entering cd / and run the following command (this will return the 5 largest directories): du -hs * | sort -rh | head -5 Note: You may get a bunch of errors if you don't have permissions...
Forgot LiteSpeed WebAdmin Console credentials
1. (For standalone) Click on the Settings icon of the AppServer, hover over Admin Panel, and click on Reset Password to reset your password for phpMyAdmin. 2. A new password will be sent to your registered email address. 3. (For cluster environments) Click on the...
Forgot phpMyAdmin credentials
If you forgot the login credentials to your database, you can easily retrieve it from your wp-config.php file. For both standalone & cluster environment: 1. To access wp-config.php, go to the Config of your Application Server by clicking on the wrench icon. 2....
How do I resolve 403 errors with Litespeed?
There are three main causes of 403 errors on your site: Web application firewall First turn WAF off as quick troubleshooting step. If 403 persists, the error is not due to the firewall. If it disappears, turn the firewall back on then follow the steps here to identify...
Why isn’t my database replicating properly across nodes?
If you're experiencing any strange behavior - missing posts, content that appears to be cached despite having cleared and turned off caches, etc - it's possible that the storage engine of your database may be to blame. When MightyBox creates a new site, it does so...
Resolving resources stuck in “restarting” status
Occasionally a node, application layer, or entire environment can get stuck with a status of "restarting" in the control panel. This is usually due to a miscommunication between the platform and the container itself and not because the container has failed...
My clustered environment is reporting 404 errors for the entire site
Occasionally during start up or restart of a clustered environment a conflict will occur during boot time that results in a 404 error across the entire site. This happens when the storage node is not fully booted and available before the application layer starts. The...
I’m getting an error “This site can’t be reached”
In a clustered install, if you're intermittently receiving an error "This site can’t be reached. Domain.com took too long to respond." but all nodes/DNS/etc appear to be configured correctly, it's possible that your load balancer layer has run out of disk space. ...