Introduction

A hosting migration can move the site and account data successfully while Plesk or DirectAdmin logins still open the old server. Admins often spot this when the website works on the new host, but panel access through the server hostname, saved bookmark, or port-based URL still lands on legacy infrastructure.

Treat this as an admin-access routing problem instead of a general migration failure. Start by checking the exact hostname and port used for panel access, because Plesk and DirectAdmin logins often depend on a panel hostname or shortcut that was not updated during cutover.

Symptoms

  • Plesk or DirectAdmin login still opens the old server after migration
  • The site works on the new host, but panel access lands on legacy infrastructure
  • Port-based access such as :8443 or :2222 still reaches the previous server
  • The login page shows the old hostname, certificate, branding, or server details
  • Panel credentials appear wrong because the browser reached the wrong machine
  • The issue started after account transfer, server replacement, or hostname cutover

Common Causes

  • The panel hostname still resolves to the old server
  • A saved bookmark, branded shortcut, or control-panel link still points to the previous host
  • The old server still answers publicly on the panel port and looks valid from the outside
  • Website DNS was updated, but panel-hostname DNS was not
  • Redirects or login helpers still send administrators to the old server path
  • Migration validation focused on public traffic and skipped panel-access testing

Step-by-Step Fix

  1. Test the exact Plesk or DirectAdmin login URL you are using and note the hostname, port, certificate, and server response, because you need proof of which system is answering the panel request.
  2. Check DNS for the panel hostname behind that login URL, because admin access often relies on a different hostname than the public website.
  3. Review bookmarks, branded login shortcuts, and any portal links used by admins, because one stale shortcut can keep sending users to the previous server after migration.
  4. Compare the certificate and hostname shown on the live login page with the server you expect, because certificate details often expose that the browser is still reaching legacy infrastructure.
  5. Verify whether the old server is still publicly answering on ports 8443 or 2222, because a reachable legacy panel endpoint can mislead admins even after the account data has moved.
  6. Update the panel-hostname record, redirect, or shortcut that actually controls access, then retest with a clean browser session, because cached redirects and stored credentials can hide whether the route is fixed.
  7. Compare direct server-hostname access with any branded or portal-based login URL, because one path may already be correct while another still points to the old machine.
  8. Confirm that successful login actions occur on the intended new server rather than only showing the right splash page, because the real fix is authenticated access on the destination system.
  9. Document the final panel hostname, ports, and redirect path after recovery, because admin login URLs are easy to miss during future hosting migrations.