Introduction

A hosting migration can move the files successfully while a WebDAV client still connects to the old hostname. Users may keep seeing certificate warnings, wrong folders, or failed logins because the client is reusing an older WebDAV endpoint that no longer matches the new host layout.

Treat this as a saved-endpoint problem instead of a generic file-access outage. Start by checking the exact WebDAV URL the client is trying to use, because migrated environments often work correctly while the desktop or mobile client still targets the previous hostname.

Symptoms

  • A WebDAV client still connects to the old hostname after migration
  • Users see certificate warnings or login prompts that reference the previous server
  • File access works through another path, but the saved WebDAV connection still fails
  • One newly configured client works while older clients still use the old endpoint
  • The issue started after account transfer, hostname cutover, or server replacement
  • The client reaches the wrong directory, wrong certificate, or wrong server branding

Common Causes

  • The WebDAV client still stores the old hostname or full endpoint URL
  • The destination server uses a different hostname or path for WebDAV than the previous host
  • A saved certificate trust decision is tied to the old endpoint
  • DNS for the old WebDAV hostname still reaches legacy infrastructure
  • Users kept an older imported connection profile after migration
  • Validation focused on file access through the control panel instead of through saved WebDAV clients

Step-by-Step Fix

  1. Open the failing WebDAV connection and record the exact URL, hostname, and path it uses, because you need to verify the real client endpoint before changing server settings.
  2. Compare the saved endpoint with the intended post-migration WebDAV URL, because many clients keep using the full previous path even after the hosting move is complete.
  3. Check the certificate and hostname presented by the live WebDAV endpoint, because TLS warnings often expose that the client is still reaching the old host rather than the migrated destination.
  4. Verify DNS for the hostname used by the WebDAV client, because a saved legacy hostname may still resolve even when the main site already moved.
  5. Test a brand-new WebDAV connection to the intended new endpoint, because that separates a stale client profile from a wider server-side WebDAV problem.
  6. Recreate or update the saved client profile only after confirming the correct new URL, because partial edits can leave old path or credential data behind.
  7. Compare one fixed client with one older imported client if behavior differs, because migration leftovers often survive inside reused connection profiles rather than in the server itself.
  8. Confirm the working client reaches the right directory and no longer shows the old certificate or hostname, because the real fix is correct authenticated access to the destination host.
  9. Document the final WebDAV URL and any shared client setup instructions after recovery, because saved file-access endpoints are easy to overlook during future hosting migrations.