Same problem here, and not fixed yet. Apparently this has been going on since at least early Friday morning (USA time). Cpanel works and all my files are where they are supposed to be. Redirecting my domain to the absolute path from the account root is only a partial solution, as my SMF forum is hosed unless I repath everything in it. I can understand people being out enjoying the holiday, but a little better communication on this issue would be nice. The last update on the status page seems to say that everything is resolved.
---------- Post added at 01:58 PM ---------- Previous post was at 03:44 AM ----------
Well, I seem to have dug myself into a deeper hole. I have an add-on domain that is registered with GoDaddy from when we had it on a different host for several years. The web site was moved to x10 about a year ago. Investigating my add-on domain setup in cPanel, I found that it had been mysteriously changed. My path for the add-on domain was public_html/THISFOLDER, it was changed to public_html/thisfoldersx, and an empty folder thisfoldersx has been added under public_html in the directory tree (hence the LiteSpeed 404 error). The original folder is still there with all my web site and forum files intact, and is accessible by using the absolute path, and is viewable via FTP and cPanel. Adding a redirect to the proper folder didn't work; it created a mod_rewrite in .htaccess in the new folder, but still 404.
So I'm thinking, "OK, I can fix this". Can't change the add-on domain path in cPanel, so I tried to remove the add-on and recreate it pointing to the correct location. This didn't work. I get the following error in cPanel when I try to recreate the add-on:
Using nameservers with the following IPs: 108.178.57.230,99.198.122.2 Sorry, the domain is already pointed to an IP address that does not appear to use DNS servers associated with this server. Please transfer the domain to this servers nameservers or have your administrator add one of its nameservers to /etc/ips.remotedns and make the proper A entries on that remote nameserver.
GoDaddy is pointing to nameservers NS1.X10HOSTING.COM and NS2.X10HOSTING.COM for my domain, which appear to be correct. This looks like a server side problem, and we may be out of luck until staff gets back from holiday to fix things.