News
Meet the redesigned Falconcloud control panel
SK
Stacy Kudryavtseva
November 6 2026
Updated November 6 2026

Why your website doesn’t open after moving to a new VPS

Why your website doesn’t open after moving to a new VPS

You’ve moved your website to a new VPS, copied the files, updated the DNS records — and the site still doesn’t open.

That doesn’t necessarily mean the migration failed. Moving a website involves several separate systems, and a problem with any one of them can make the site unavailable.

Here’s what to check before you start moving everything again.

Start with DNS

One of the most common problems after a VPS migration is DNS.

Your domain needs to point to the public IP address of the new server. If the A record still contains the old IP, visitors will continue to reach the previous VPS.

After changing DNS records, the update may not become visible everywhere immediately. DNS resolvers can continue using cached information until its TTL expires.

You can check the domain from different networks or use a DNS lookup tool to see which IP address it currently resolves to.

If you need to manage your domain records, Falconcloud offers a cloud DNS service for configuring and updating DNS settings.

Check whether the web server is running

Correct DNS records won’t help if there is nothing listening for web requests on the new VPS.

Check that your web server — for example, Nginx or Apache — is running and configured for the migrated website.

A common situation is that the server itself works, but the website configuration is missing, disabled, or still refers to paths used on the old machine.

Also make sure ports 80 and 443 are available for HTTP and HTTPS traffic.

Make sure the website files are in the right place

During migration, files can end up in a different directory from the one configured in the web server.

Check the document root and confirm that it points to the actual website files.

Permissions matter too. The files may exist, but the web server still needs permission to read them.

If the homepage returns a 403 or 404 error after migration, file paths and permissions are good places to start.

Check the database connection

A website may load its static files but fail as soon as it tries to connect to the database.

If the database was also moved, check its hostname, port, username, password, and database name. Applications often keep these settings in configuration files or environment variables.

Also confirm that the database service is running and that the application is allowed to connect to it.

This is especially important when the web application and database now run on separate servers.

Don’t forget about SSL

HTTPS can create another problem after migration.

An SSL certificate configured on the old server does not automatically appear on the new one. You may need to install or issue a certificate again and update the web server configuration.

If HTTP works but HTTPS doesn’t, check the certificate, port 443, and SSL settings first.

It is also worth checking whether the certificate covers the exact domain and subdomains you use.

Check the firewall

Sometimes everything is configured correctly inside the VPS, but incoming traffic is blocked.

Review firewall rules on the server and any network-level rules that apply to the VPS. HTTP and HTTPS traffic need to reach the appropriate ports.

Avoid simply disabling the firewall to solve the problem. It is better to identify which connections the website actually needs and allow them explicitly.

For more recommendations on protecting your server, see our VPS security checklist.

Clear local DNS cache

If the website works for other people but not for you, the problem may be closer to home.

Your computer, browser, router, or internet provider may still have the old DNS information cached.

Try another network or device and check which IP address your domain resolves to. This helps distinguish a local cache issue from a server-side problem.

Look at the logs

When the obvious checks don’t reveal the cause, logs usually provide more useful information than repeatedly changing settings.

Web server logs can show failed requests, configuration errors, permission problems, and application failures. Application and database logs can help narrow the issue down further.

Instead of asking only “Why is the website down?”, look at what happens when a request actually reaches the server.

Common problems after a VPS migration

If you're not sure where to start, use this table to narrow down the possible cause based on what you're seeing.

Problem Possible cause What to check
Website opens on the old server Outdated DNS records or cached DNS information Check the domain's A record and DNS resolution.
Connection timed out Firewall rules, network issues, or an unreachable web server Check the VPS public IP, ports 80 and 443, and web server status.
403 or 404 error Incorrect file permissions, document root, or website configuration Review file locations, permissions, and web server configuration.
Database connection error Incorrect credentials, database host, or unavailable service Verify database settings, service status, and connection permissions.
HTTPS doesn't work Missing SSL certificate or incorrect HTTPS configuration Check the certificate, domain coverage, and port 443.
Website works only on some devices Local DNS cache or different DNS resolution results Compare DNS results and test the website from another network.

Use a simple troubleshooting order

After moving a website, check the path from the visitor to the application:

Domain → DNS → VPS → firewall → web server → website → database

If the domain resolves to the wrong IP, fix DNS first. If it reaches the correct server but there is no response, check the firewall and web server. If the server responds with an error, move on to the application, files, database, and logs.

Following that order is usually faster than changing several things at once.

If you're planning another move, read our guide to migrating from shared hosting to a VPS for more advice on preparing your website and server environment.

Moving your website to Falconcloud

A Falconcloud VPS can be used to host websites and web applications with configurable CPU, RAM, and SSD resources.

After creating a new VPS, you can install the required web stack, transfer your website, point the domain to the new server, and test the project before completing the migration.

The important part is not just moving the files. DNS, web server configuration, databases, SSL, and network access all need to work together on the new infrastructure.

Conclusion

When a website doesn’t open after moving to a new VPS, the server itself is only one possible cause.

Start with DNS and the new IP address. Then check the web server, files, database connection, SSL, firewall, and logs.

Most migration problems become much easier to diagnose once you follow the request from the domain all the way to the application.

Ready to manage your website on a new server? Sign in to the Falconcloud control panel and manage your VPS infrastructure.

You might also like...

We use cookies to make your experience on the Falconcloud better. By continuing to browse our website, you agree to our
Use of Cookies and Privacy Policy.