Microsoft Edge returns ERR_ADDRESS_UNREACHABLE on specific website - Other browsers have no problems

ERR_ADDRESS_UNREACHABLE in Microsoft Edge when other browsers work usually indicates a network, DNS, or filtering issue that affects Edge’s traffic path specifically, not a permanent site block in Edge’s pop‑up or permissions settings.

Based on the available guidance, try the following Edge- and network-focused steps:

1. Confirm the site is not being blocked by Edge itself
   • In Edge, go to Settings and more (⋯) > Settings > Privacy, search, and services.
   • Under Site permissions > All permissions, review any categories that might affect the site (for example, Pop-ups and redirects if the site opens in a new window).
   • If the site needs pop‑ups, add it explicitly:
     1. Go to Site permissions > Pop-ups and redirects.
     2. Under Allowed to send pop-ups and use redirects, select Add site.
     3. Enter the full URL starting with https:// and select Add.
   • Test the site again.
2. Check for DNS issues that might affect Edge The error can be triggered by DNS problems. One supported workaround is to switch to a known working DNS and flush the DNS cache:
   1. Open Control Panel > Network and Internet > Network Connections.
   2. Right‑click the active network connection > Properties.
   3. Select Internet Protocol Version 4 (TCP/IPv4) > Properties.
   4. Choose Use the following DNS server addresses and set:
      • Preferred DNS server: 8.8.8.8
      • Alternate DNS server: 8.8.4.4
   5. Open Command Prompt as administrator and run:

            ipconfig /flushdns
      

   6. Close and reopen Edge and try the site again.
3. Ensure Edge can reach its required endpoints (especially in managed or filtered networks) If a firewall, proxy, or security product is filtering traffic differently per application, Edge may be blocked while other browsers are not.
   • Make sure the environment allows the documented Edge endpoints, especially if using SSL inspection or app‑based rules. For updates and downloads, the following must be reachable:
     • https://msedge.api.cdp.microsoft.com
     • *.dl.delivery.mp.microsoft.com
   • If the site in question is behind similar filtering, ensure the same rules that allow Chrome/Firefox also explicitly allow Edge.
4. Reinstall or repair Edge If the problem persists only in Edge and follows the profile or machine, reinstalling Edge on top of the existing installation can clear corrupted components without removing Windows:
   1. Open any working browser.
   2. Go to the official Edge download page referenced in the guidance and download the installer.
   3. Run the installer to reinstall Edge over the current installation.
   4. Test the problematic site again.
5. If the issue is intermittent or tied to large downloads or complex TLS/proxy setups
   • In corporate or proxy environments, intermittent failures can be related to TLS session handling and proxy reauthentication. In that case, work with the network/proxy administrator to review TLS and session reuse settings, and confirm Edge traffic is treated the same as other browsers.

If the error continues after these steps, collect details such as whether the issue occurs on other networks or user accounts, and whether disabling security software or VPN/proxy temporarily changes the behavior; then provide those details in a follow‑up so the investigation can focus on network path vs. Edge configuration.

References:

• Block pop-ups in Microsoft Edge
• Troubleshooting tips for downloading, installing, and updating Microsoft Edge
• Microsoft Edge will not start. - Microsoft Q&A
• Downloads fail intermittently in Microsoft Edge due to corporate proxy reauthentication and TLS session reuse failure - Microsoft Q&A