Skip to content

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 site's SSL →

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 SSL Certificate →

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.

CertificateExpiry, issuer, domains (SAN)
ChainIntermediate and root CA validation
TLS ProtocolTLS version and cipher suite
VulnerabilitiesHeartbleed, POODLE, weak ciphers

Why teams trust us

TLS 1.3
supported
Full
CA chain check
<2s
result
30/14/7
days-to-expiry alerts

How it works

1

Enter domain

2

TLS chain verified

3

Expiry date & vulnerabilities

What Does the SSL Check Cover?

SSL/TLS is the encryption protocol that protects data between the browser and server. Our tool analyzes the certificate, chain of trust, TLS version, and knownvulnerabilities.

Certificate Details

Issuer, validity period, signature algorithm, covered domains (SAN), and validation type (DV/OV/EV).

Chain of Trust

Full chain verification: from leaf certificate through intermediates to root CA.

TLS Analysis

Protocol version (TLS 1.2/1.3), cipher suites, Perfect Forward Secrecy (PFS) support.

Expiry Alerts

Set up a monitor — get Telegram and email alerts 30/14/7 days before expiration.

DV vs OV vs EV Certificates

DV (Domain Validation)
  • Confirms domain ownership only
  • Issued in minutes automatically
  • Free via Let's Encrypt
  • Suitable for most websites
  • Most common certificate type
OV / EV
  • Organization (OV) or Extended Validation (EV)
  • Issued in 1-5 business days
  • Costs $50 to $500/year
  • For finance, e-commerce, government sites
  • Increases user trust

Who uses this

DevOps

SSL certificate monitoring

Security

TLS config audit

SEO

HTTPS as ranking factor

E-commerce

customer trust

Common Mistakes

Expired certificateBrowsers block sites with expired SSL. Set up auto-renewal or monitoring.
Incomplete certificate chainWithout intermediate CA, some browsers and bots cannot verify the certificate.
Mixed content on HTTPS siteHTTP resources on an HTTPS page — the browser lock icon disappears, reducing trust.
Using TLS 1.0/1.1Legacy TLS versions have known vulnerabilities. Use TLS 1.2+ or 1.3.
Domain mismatch in certificateThe certificate must cover all site domains, including www and subdomains.

Best Practices

Set up auto-renewalLet's Encrypt + certbot with cron — certificate renews automatically every 60-90 days.
Enable HSTSStrict-Transport-Security header forces browsers to always use HTTPS.
Use TLS 1.3TLS 1.3 is faster (1-RTT handshake) and safer — legacy ciphers removed.
Monitor expiration datesCreate a monitor on Enterno.io — get notified well before expiration.
Verify chain after renewalAfter certificate renewal, confirm that intermediate certificates are installed.

Get more with a free account

SSL certificate monitoring, check history and alerts 30 days before expiry.

Sign up free

Learn more

Sources

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 <a href="/en/ping">Enterno Ping</a> 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.