Overview

A common issue after a website migration is that the website files are present on the server but the website does not load correctly because the application is looking in the wrong location.

Symptoms

• Website displays a blank page.
• Website loads a default page instead of the migrated site.
• Images or files are missing.
• Application reports missing files or directories.
• PHP errors referencing missing files.
• Website works from one path but not another.

Cause

Many applications store absolute paths in their configuration files.

After a migration, the website may be moved to a different location on the new server. If the application is still referencing the old path, it may be unable to locate required files.

Common examples:

• WordPress configuration includes.
• Custom PHP applications.
• Configuration files referencing old server paths.
• Hardcoded file or image locations.

Default Plesk Paths

Depending on the server configuration, websites are commonly located under:

• /var/www/vhosts/<domain>/
• /data/vhosts/<domain>/

A path that existed on the source server may not exist on the destination server.

What to Check

Verify that:

• Website files were uploaded to the correct subscription.
• The application is referencing the correct directory.
• Any configuration files containing file paths have been updated.
• Included files and libraries exist in the expected location.
• The document root matches the website location.

Resolution

Review the website configuration and verify that any file paths, includes, or references point to the correct location on the destination server.

For WordPress websites, path and URL issues are commonly caused by references stored in the database. In these cases, a search and replace may be required to update references to the old domain, staging URL, or server path.

Please refer to the WordPress Search and Replace guide for instructions on performing a search and replace operation.

After completing the search and replace, verify that:

• Pages load correctly.
• Images and media files are accessible.
• Themes and plugins function as expected.
• No references remain to the old server path or URL.

If the issue persists, review the website configuration files for any hardcoded paths that may need to be updated manually.