Search results

  1. S

    DocumentRoot/path problem

    Hmm.. it seems you are right. After adding an entry into the hosts file, everything seems to be working just fine. Must be something to do with the configuration because my other server running LiteSpeed can access accounts using IP/~accountname just fine. Not sure what the problem here is...
  2. S

    DocumentRoot/path problem

    Hi, I've just performed all the steps listed above and it still isn't working. Apache works fine but LiteSpeed doesn't. Strange because LiteSpeed should be reading Apache's conf file so there shouldn't be a problem. Would you like root access to the server?
  3. S

    DocumentRoot/path problem

    My LiteSpeed version is 4.0.20, which was what the WHM/cPanel plugin installed. The timestamp of lshttpd.4.0.20 is 1186384 Apr 18 20:22.
  4. S

    DocumentRoot/path problem

    Hi, you can test the phpinfo now. It works fine when you access that file. As for other accounts, they have the same errors. And could it be possible if you remove the live links to my server please? I just don't want it publicly displayed. Thank you!
  5. S

    DocumentRoot/path problem

    I've re-installed LiteSpeed again using that guide and the error is still the same. I've also tried uninstalling LiteSpeed + the WHM/cPanel plugin and re-installing again but it doesn't work either. I changed the port offset to 2000 and Apache works fine but LiteSpeed doesn't. You can check it...
  6. S

    DocumentRoot/path problem

    Hello, I've recently switched from Apache to LiteSpeed Web Server. However, after switching to LiteSpeed, my sites have stopped working. I'm using cPanel on CentOS 5.5. I checked the error logs and it seems as though my DocumentRoot has changed. The errors are similar to the one below...
Top