Chrome ERR_ADDRESS_UNREACHABLE — Server Cannot Be Reached

Chrome ERR_ADDRESS_UNREACHABLE indicates the browser cannot establish a network connection to the server's IP address. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.

Here are the key things to understand: DNS resolution succeeded but the IP address is not reachable. Different from ERR_NAME_NOT_RESOLVED (DNS failure). Can indicate the server is down, IP is wrong, or network path is broken. Common with sites that recently changed hosting providers. Also appears when trying to reach internal/private IP addresses from external networks. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.

The most common reasons this occurs include: The website's server is completely down. DNS cache returning a stale/wrong IP address. Firewall blocking outbound connections to that IP range. The website moved to a new IP but DNS TTL has not expired. Network routing issue between your ISP and the hosting provider. Identifying the root cause is the first step toward finding the right solution.

To resolve this, follow these recommended steps: Check if the site is down for everyone: use downdetector.com or isitdown.site. Flush DNS cache: chrome://net-internals/#dns > Clear host cache. Also flush OS DNS: ipconfig /flushdns (Windows) or sudo dscacheutil -flushcache (Mac). Try accessing by IP directly (if known) to bypass DNS. Disable VPN or proxy if active and retry. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.

This article is part of our Browser Errors collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.