In most cases this error is related to missing/misconfigured file or webpage. When the user request that file or webpage the Litespeed web server will return the information that there is something wrong and it cant find that file. Lets see what can trigger that error and how to resolve it.

Many templates include path to favicon.ico but not the actual icon and when you load your site you can see in the developer console line like:

 GET https://domain.com/favicon.ico 404 

In that case the error is not fatal but its a good practice to resolve that. To do that simple find the included path for that icon and put it there. You can use that method to resolve not only missing favicon but other files too.

This is the second most common reason for error 404. For example if you change permalink structure of your website but you did not put rewrite rules or redirects for that you will see the error. You can reverse the changes for permalinks or review your .htaccess file and put the right rules there.

If you put, for example redirect from your index page to home page, but the last one did not exist you will see again error 404. The same think can be apply if you put wrong rewrite rules. You can temp rename your .htaccess file from FTP client or with terminal command:

 mv .htaccess htaccess-wrong 

or you can reverse the latest changes to that file.

If you or your hosting provider change the web server for example to nginx in some cases you will see error 404. Some web server did not read the .htaccess file and you need to contact your hosting provider or you can manually make change to include the critical rules directly in the .conf/vconf file for that web server.

Depend on the server configuration in some cases when domain name is point to server but its not added there you can see the error. You can contact your hosting provider for additionally information or you can review the server if you have access.

This is a command mistake when the new vhost is created and the user put wrong document root. In that case the web server will search for the files in different directory and when they are not there you will see error 404.

If you change the Name Servers (NS) for a domain name before configurate the domain/webpage in the new location you can experience 404. Always change NS server after the domain/webpage is properly working on the new location.

If you migrate your page to new server, change the NS servers for the domain and delete the content on the old server its posable to see error 404. That is because most of the ISP (Internet service provider) has DNS cache and your page is still loading from the old location. Its a good practice to not delete the content from the old server for 3-4 days to avoid that.