Bobcares

Litespeed web server 404 error: Easy solution

by | Mar 20, 2023

Let us learn more about the error litespeed web server 404 error. With the support of our Litespeed hosting support services at Bobcares we will now learn how to remove the error.

Error:Wrong Document Root: litespeed web server 404 error

This is due to a command error when creating the new vhost; the user enters the incorrect document root. In such instance, the web server will look for the files in a separate location and return Error 404 if they are not found.

When compared to Ngnix and Apache, LiteSpeed Web Server is the quickest.

We most likely planned to speed up the website by moving the web server from Apache to LiteSpeed Web Server, however switching from Apache to LiteSpeed Web Server got us into problems.

There is a potential that WordPress displays a “404 Not Found” error and that no page or post links operate save for the homepage and the WordPress admin panel.

404 Not found Error in WordPress using Litespeed Web Server

Error:Wrong Document Root: litespeed web server 404 error: Solution

  1. Log in to FTP or a file manager and navigate to the WordPress directory (which is usually under “public html”).
  2. Use the file manager’s edit feature to modify the.htaccess file.
  3. Look for the following code:

    litespeed web server 404 error

    We need to add “/” to the second line of code, or just copy/paste the code below into the.htaccess file.

    litespeed web server 404 error

  4. Restart LiteSpeed Web Server, and the website should be operational again.

LiteSpeed WordPress permalink structure:

Visit the OpenLiteSpeed “LiteSpeed WebAdmin Console” dashboard and choose Virtual Hosts from the navigation bar. In the Virtual Host List, look for the domain. Choose the Rewrite tab when we open it.

In the Rewrite Control box on the Virtual Host’s Rewrite tab, update Enable Rewrite and Auto Load from.htaccess to Yes for both fields. The configuration has changed. Please restart gracefully to implement the modifications.

Merely doing this may not result in the permalink structure we want; check again to see whether this has resolved the permalink issues. This is the next step in litespeed web server 404 error.

Now open.htaccess at the document root (not the server or virtual host root) – where the real WordPress files are placed – and insert the previous version’s.htaccess content.

Instead, for the sake of simplicity, here we can go through an example of htaccess content, which should work just fine for us. The contents of the IfModule mod rewrite.c is transferred to the htaccess file.

litespeed web server 404 error

That’s all there is to it.

[Need assistance with similar queries? We are here to help]

Conclusion

To sum up, we have now seen how to remove the litespeed web server 404 error. With the support of our Litespeed hosting support services at Bobcares we have now gone through the whole process of how to remove the error.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF