404 Not Found after moving a website to this server

For hosting customers · Updated 2026-10-29

On this page
  1. Symptoms
  2. Causes
  3. Fix
  4. Still not working?

After a move, a 404 almost always means the web server looks in a different place than where the files are, or the rewrite rules that turn pretty URLs into pages are not in effect yet.

Symptoms

  • Every page, or every page except the home page, shows 404 Not Found or a page titled 404 — Page not found ("The page you are looking for does not exist or has moved.").
  • Pictures or downloads that worked on the old server are missing.
  • Visitors (section Advanced) lists the URLs under Pages not found (this month).

Causes

Most likely first:

  1. The files are not in the website's folder — for example in the home folder, or in a subfolder of public_html.
  2. The .htaccess file with the rewrite rules is missing, or it was just uploaded and is not applied yet.
  3. File names differ in upper and lower case — Logo.PNG is not logo.png on this server.
  4. The application still uses the old address or folder (WordPress, Joomla and others store it).
  5. The domain's document root is different from the one you expect (addon domains and subdomains have their own folder).

Fix

1. Put the files in the website's folder

  1. Open Domains (section Domains). The Document root column shows the folder of each website, relative to your home folder. The main domain uses public_html.
  2. Open File Manager (section Files) and check that index.php or index.html is directly in that folder, not one level deeper (for example public_html/mysite/index.php).
  3. If they are one level too deep, select everything in the subfolder, click Move and move it up.

2. Rewrite rules (.htaccess)

Applications with pretty URLs (WordPress permalinks, Laravel, most shops) need the .htaccess file from the old server in the website's folder. It starts with a dot, so some FTP programs do not copy it.

  • Upload it again into the website's folder.
  • A new, changed or deleted .htaccess file is applied within a minute. Wait a minute before testing again.
  • For WordPress, you can also open Settings → Permalinks in the WordPress dashboard and click Save Changes; WordPress writes the file again.
Note: on servers that use Nginx instead of OpenLiteSpeed as web server, .htaccess files are ignored. Ask your host which web server your plan uses if rewrite rules have no effect at all.

3. Upper and lower case

Linux servers treat Image.jpg and image.jpg as two different files. Rename the files in File Manager (Rename) to match the links exactly, or change the links. This often shows up when a site comes from a Windows server.

4. The application's stored address

If the home page works but links point to the old domain, a temporary address or another folder, change the site address in the application's settings. For WordPress these are WordPress Address (URL) and Site Address (URL) under Settings → General. A database copied from elsewhere also keeps the old address in posts and menus.

5. The domain uses another folder

An addon domain or subdomain shows the files of its own Document root, for example public_html/another-site.com. Upload that site there, not into public_html.

Still not working?

  • Open Site Check (section Advanced), choose the website and click Check. Address in DNS must say (this server); if not, visitors still reach the old server. See Website not working after changing nameservers.
  • If a 404 page shows "There is no website at this address yet", the domain is not set up on this server: see Website shows the default page.
  • If your host has turned on the AI assistant, click Fix with the assistant on Site Check.
Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.