> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://copilhost.crisp.help/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Troubleshooting: Site inaccessible after migration

Sometimes, after a migration, your site may appear inaccessible from your location, even though the process is finished. You might see a **DNS Error screen**.

This is usually caused by **caching issues**, and we’re here to help you resolve them.

In most cases, your site has been successfully migrated and is live for the rest of the world, but your local device is still "remembering" the old version or location.

#### A simple solution...

The easiest way to fix this is simply to **wait**. 😊

Managing local cache can be tedious.
If you aren't in a hurry, we highly recommend waiting a few minutes to a few hours for the problematic cache to expire naturally.

To confirm it is indeed a cache issue, try these quick tests:
* **Switch browsers** (e.g., try Firefox if you usually use Chrome).
* **Switch networks** (switch from your Wi-Fi to your phone's 4G/5G data).
* **Switch devices** (check from another PC or your smartphone).

#### Clearing your Caches

If you need immediate access, you’ll need to clear various caches to identify the "culprit."

**1. Clear your Browser Cache**
Start by clearing the history and cache of your web browser (Chrome, Firefox, Safari, etc.).

**2. Flush your Local DNS Cache**
If the browser cache isn't enough, you can clear the DNS cache stored on your computer. This is done via a simple terminal command:
* **On Windows:** Search for "Terminal" or "Command Prompt" in your search bar, then copy and paste the following command: `ipconfig /flushdns` *Congratulations, your local DNS cache is now clear!* 🎉
* **On macOS:** Open the "Terminal" app and paste this command: `sudo killall -HUP mDNSResponder`

**3. ISP / Router Cache** 
If the site is still inaccessible after these steps, the cache is likely held by your **Internet Service Provider (ISP)** or your router.

**How to check:** Switch to your mobile's 4G/5G data. If the site works there, your router's DNS is the issue. 
**The fix:** This is more technical to clear manually, so we recommend simply waiting for the ISP cache to refresh on its own.