Skip to content
RU

ERR_ADDRESS_UNREACHABLE: Diagnosis

Key idea:

ERR_ADDRESS_UNREACHABLE — Chrome could not establish a TCP connection to the IP. Below the TLS layer. Causes: DNS returned wrong IP, routing issue (server down/no internet), firewall in the path, ISP blocks the range. Fix: ping/traceroute to diagnose.

This error blocks HTTPS access. Below: causes, fixes, working config, FAQ.

Check your host & ports →

Common Causes

  • DNS returned stale IP after server migration
  • Server fully down (hardware failure, DC outage)
  • Firewall (server-side or client-side) drops SYN
  • ISP-level block (regional censorship, .onion)
  • Routing issue: trace stops at an intermediate hop

Step-by-Step Fix

  1. Check resolution: nslookup example.com 1.1.1.1 — right IP?
  2. Ping: ping example.com — any reply?
  3. Traceroute: traceroute example.com — where does it die?
  4. Enterno Traceroute visualizes the chain
  5. Try via VPN — if it works = ISP block

Check reachability and ports →

Related SSL Errors

TL;DR: Understanding ERR_ADDRESS_UNREACHABLE

The ERR_ADDRESS_UNREACHABLE error indicates that the browser cannot connect to the server at the specified IP address. This typically arises from network configuration issues, firewall settings, or server unavailability. To troubleshoot, check your network connections, test the server's IP with ping, and verify DNS settings. If the server is unreachable, it may be down or misconfigured.

Common Causes of ERR_ADDRESS_UNREACHABLE

The ERR_ADDRESS_UNREACHABLE error can stem from several underlying issues. Understanding these causes is essential for effective troubleshooting:

  • Network Configuration: Incorrect network settings can prevent your device from reaching the desired server. Ensure that your IP configuration matches your network requirements.
  • Firewall Restrictions: Firewalls may block access to certain IP addresses or ports. Check your firewall settings to ensure the server's IP is whitelisted.
  • Server Downtime: If the server is temporarily offline or undergoing maintenance, you will encounter this error. Use monitoring tools to check server uptime.
  • DNS Issues: Misconfigured Domain Name System (DNS) settings can lead to address resolution failures. Ensure your DNS records are set up correctly.

Troubleshooting ERR_ADDRESS_UNREACHABLE: Practical Steps

To resolve the ERR_ADDRESS_UNREACHABLE error, follow these practical troubleshooting steps:

  1. Check Network Connectivity: Open a command prompt and use the ping command to test connectivity to the server:
ping [Server_IP_Address]

Replace [Server_IP_Address] with the actual IP address of the server. If you receive replies, your network is functioning correctly. If not, proceed to the next step.

  1. Verify Firewall Settings: Access your firewall configuration and ensure it allows outbound traffic to the server's IP. For example, on a Linux server, you might use:
sudo iptables -L

Look for any rules that might block access to the server. Adjust the rules as necessary.

  1. Check DNS Resolution: Use the nslookup command to verify that the domain name resolves to the correct IP address:
nslookup [Your_Domain]

If the IP is incorrect or not returned, you may need to update your DNS settings. Check your DNS provider's documentation for guidance.

  1. Test with a Different Network: If possible, connect to a different network (e.g., mobile hotspot) and attempt to access the server. If successful, the issue may reside within your original network.
  2. Contact Hosting Provider: If the server remains unreachable, reach out to your hosting provider for assistance. They can check server status and configuration on their end.

By systematically addressing these areas, you can effectively troubleshoot and resolve the ERR_ADDRESS_UNREACHABLE error.

ICMP PingHost availability and latency
Port ScannerOpen TCP port detection
LatencyResponse time in milliseconds
Packet LossPercentage of dropped packets

Why teams trust us

ICMP+TCP
check protocols
14
key ports scanned
2,014
checks in 30 days
3
regions

How it works

1

Enter IP or domain

2

ICMP packets sent

3

Latency & packet loss shown

How Do Ping and Port Scanning Work?

Ping sends ICMP packets to a host and measures response time. Port scanning checks which TCP ports are open and accepting connections — helping diagnose serviceavailability issues.

Configurable Ping

Choose packet count (3, 4, 6, 10). Stats: min/avg/max latency and packet loss.

Common Port Scanner

Check 14 key ports: HTTP, HTTPS, SSH, FTP, SMTP, MySQL, PostgreSQL, and more.

Cloud-Based Check

Testing from our server — see site availability from outside, not just your local network.

Uptime Monitoring

Need constant monitoring? Create a monitor — checks every minute with notifications.

Who uses this

DevOps

availability diagnosis

Network engineers

TCP port scanning

Developers

connection debugging

SRE

basic health check

Common Mistakes

ICMP blocked = server is downMany servers block ICMP. Ping fails but site works — check ports instead.
High ping = server problemLatency depends on geography. 150ms between continents is normal, not an error.
Closed ports — cause for alarmClosed ports of unused services are good. Unnecessary open ports are a risk.
One check = sufficientNetworks are unstable. A single timeout ≠ a problem. Check multiple times or set up monitoring.

Best Practices

Combine ping and port checksPing shows host availability, ports show specific service availability. Use both.
Check from different locationsThe problem may be local. A cloud test shows the real picture.
Close unused portsEvery open port is a potential attack vector. Keep only necessary ports open.
Set up monitoringManual checks do not scale. Set up automated monitoring with notifications.

Get more with a free account

Ping check history, host availability monitoring and downtime alerts.

Sign up free

Learn more

Frequently Asked Questions

How is it different from ERR_CONNECTION_REFUSED?

REFUSED = server sent RST (no listener). UNREACHABLE = IP does not respond at all (network issue).

Is the error only on my side?

Check via Enterno Ping from multiple regions. Only your network — your problem.

How long to recover?

Depends on cause. DC outage — hours. DNS propagation — 5-60 min. Hardware — more complex.

Error on mobile but not desktop?

Mobile carriers have different DNS/routing. Try 8.8.8.8 on phone.

Try the live tool that powered this guide

Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.