{"id":75125,"date":"2026-09-24T01:02:21","date_gmt":"2026-09-24T07:02:21","guid":{"rendered":"https:\/\/www.scalahosting.com\/blog\/?p=75125"},"modified":"2026-09-24T01:22:53","modified_gmt":"2026-09-24T07:22:53","slug":"this-site-cant-be-reached","status":"publish","type":"post","link":"https:\/\/www.scalahosting.com\/blog\/this-site-cant-be-reached\/","title":{"rendered":"This Site Can&#8217;t Be Reached: Complete Fix"},"content":{"rendered":"\n<div class=\"wp-block-group alert-green\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\">\n<p class=\"wp-block-paragraph\"><strong>TL;DR<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The error is Chrome and Edge&#8217;s generic &#8220;can&#8217;t connect&#8221; page. The gray sub-code beneath it names the real cause.<\/li>\n\n\n\n<li>Six usual causes: DNS error, server down, browser cache, firewall or security software, an SSL problem, and a wrong URL.<\/li>\n\n\n\n<li>The 10-second test: open the site on another device or network. If it loads there, this means it&#8217;s your device. If it fails everywhere, the reason is the server.<\/li>\n\n\n\n<li>Quick fixes on your side: flush your DNS cache, switch to a public DNS resolver (1.1.1.1 or 8.8.8.8), disable any VPN or proxy, and clear the cache.<\/li>\n\n\n\n<li>Site owners: confirm the server and its services are running, check DNS and SSL, and review the firewall.<\/li>\n<\/ul>\n<\/div><\/div>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>&#8220;This site can&#8217;t be reached&#8221;<\/strong> is the message Chrome and Edge show when your browser cannot open a page. It almost always comes down to one of six things: a DNS lookup that failed, a server that is down, stale browser cache, a firewall or security tool blocking the request, a broken SSL certificate, or a mistyped URL.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The fastest way to fix it is to read the gray sub-code printed under the error, then match it to the cause. If the page loads on another device, the problem is on your side. If it fails everywhere, the problem is the server. This guide walks through every fix, step by step, for Windows, Mac, mobile, and site owners.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What &#8220;This Site Can&#8217;t Be Reached&#8221; Actually Means<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Chrome and Edge both run on Chromium, so both show the same &#8220;This site can&#8217;t be reached&#8221; error message for several different failures. Safari and Firefox phrase it differently but mean the same thing: the browser requested a page and never received a usable response. The detail that matters is the gray sub-code printed underneath. That line tells you where to actually look.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Two \u201cfamilies\u201d cover almost every case:<\/p>\n\n\n\n<figure class=\"wp-block-table is-style-regular green-rows\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>DNS family<\/strong><\/th><th><strong>Connection family<\/strong><\/th><\/tr><\/thead><tbody><tr><td>DNS_PROBE_FINISHED_NXDOMAIN<br>ERR_NAME_NOT_RESOLVED<\/td><td>ERR_CONNECTION_TIMED_OUT<br>ERR_CONNECTION_REFUSED<br>ERR_CONNECTION_RESET<\/td><\/tr><tr><td>The domain never turned into an address. Look at DNS or the URL.<\/td><td>The address was found, but the connection failed. Look at the server or firewall.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Find Out Whose Problem It Is<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before you change a single setting, run one test. Open the same site on a different device or network, such as your phone over mobile data rather than Wi-Fi. <strong>If it loads, the problem is your device or connection. If it fails everywhere, the site&#8217;s server is the issue and only its owner can fix it.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That one check decides which half of this guide you need, and it takes about ten seconds.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large mpg-gallery\"><img decoding=\"async\" width=\"1140\" height=\"639\" src=\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/09\/visual-1-whose-problem-1140x639.webp\" alt=\"This Site Can&#8217;t Be Reached: Complete Fix, Find Out Whose Problem It Is\" class=\"wp-image-75127\" srcset=\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/09\/visual-1-whose-problem-1140x639.webp 1140w, https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/09\/visual-1-whose-problem-300x168.webp 300w, https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/09\/visual-1-whose-problem-767x430.webp 767w, https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/09\/visual-1-whose-problem.webp 1365w\" sizes=\"(max-width: 361px) 660px, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 910px, 1140px\" \/><figcaption class=\"wp-element-caption\"><em>The split test: one result sends you to the device fixes, the other to the server fixes.<\/em><\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>The 6 Most Common Causes and How to Fix Each<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Match your sub-code to the cause below, then run the short fix under it.&nbsp;<\/p>\n\n\n\n<figure class=\"wp-block-image size-large mpg-gallery\"><img decoding=\"async\" width=\"1140\" height=\"636\" src=\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/09\/visual-3-six-causes-1140x636.webp\" alt=\"This Site Can&#8217;t Be Reached: Complete Fix, The 6 Most Common Causes and How to Fix Each\" class=\"wp-image-75128\" srcset=\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/09\/visual-3-six-causes-1140x636.webp 1140w, https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/09\/visual-3-six-causes-300x167.webp 300w, https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/09\/visual-3-six-causes-767x428.webp 767w, https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/09\/visual-3-six-causes.webp 1425w\" sizes=\"(max-width: 361px) 660px, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 910px, 1140px\" \/><figcaption class=\"wp-element-caption\"><em>The six usual suspects behind a page that will not load.<\/em><\/figcaption><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>1. DNS Error<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A DNS error means your browser could not translate the domain name into an IP address, so it never reached the server. The sub-codes are <strong><\/strong><strong>DNS_PROBE_FINISHED_NXDOMAIN<\/strong> and <strong>ERR_NAME_NOT_RESOLVED<\/strong>.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Flush your DNS cache and renew the connection (exact commands are in the Windows and Mac sections below).<\/li>\n\n\n\n<li>Switch your device to a public DNS resolver, such as Cloudflare (1.1.1.1) or Google (8.8.8.8).<\/li>\n\n\n\n<li>Restart your router to clear its own DNS cache.<\/li>\n\n\n\n<li>If one site fails everywhere, its DNS records may be misconfigured, or the domain may have expired. That is the owner&#8217;s fix.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>2. Server Down<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If the domain resolves but the connection times out or is refused, the web server is likely down, overloaded, or not listening on the expected port. The sub-codes are <strong>ERR_CONNECTION_TIMED_OUT<\/strong> and <strong>ERR_CONNECTION_REFUSED<\/strong>.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Confirm it is the server by loading the site on another network, or by checking an &#8220;is it down&#8221; status tool.<\/li>\n\n\n\n<li>Wait a few minutes and retry. Transient overloads and service restarts often clear on their own.<\/li>\n\n\n\n<li>If the site is yours, check that the web server and database are running (see the server-side section).<\/li>\n\n\n\n<li>If it is not your site, there is no visitor-side fix. Contact the owner or wait for recovery.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>3. Browser Cache<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A stale cache, old cookies, or a corrupted browser profile can cause the error to persist even after the site is back online.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Hard-refresh the page (Ctrl+F5 on Windows, Cmd+Shift+R on Mac).<\/li>\n\n\n\n<li>Open the site in a private or incognito window to bypass the cache.<\/li>\n\n\n\n<li>Clear cached images, files, and cookies for that site.<\/li>\n\n\n\n<li>Disable recently added browser extensions one at a time, then reload.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>4. Firewall or Security Software<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A local firewall, antivirus, VPN, or proxy can silently block a connection and produce the error even when the site is perfectly healthy.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Turn off any VPN or proxy, then reload the page.<\/li>\n\n\n\n<li>Temporarily disable your antivirus or firewall web shield, test the site, then turn it back on right away. Do not leave protection off.<\/li>\n\n\n\n<li>Check your browser&#8217;s proxy settings and set them to automatic or off.<\/li>\n\n\n\n<li>On a work or school network, an administrator may be blocking the site, and there is no visitor-side fix for that.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>5. SSL Certificate Issue<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A broken, expired, or misconfigured SSL\/TLS certificate can stop the secure connection from completing. This more often shows as &#8220;<strong>Your connection is not private<\/strong>&#8221; or <strong>ERR_SSL_PROTOCOL_ERROR<\/strong>, but it belongs on the same checklist because it blocks the page the same way.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Check that your device&#8217;s date and time are correct. A wrong clock breaks certificate validation.<\/li>\n\n\n\n<li>Clear the SSL state or cached certificates, then reload.<\/li>\n\n\n\n<li>Try the site in another browser to rule out a local trust-store problem.<\/li>\n\n\n\n<li>If it is your site, renew or reissue the certificate (owners: see the server-side section).<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>6. Wrong or Mistyped URL<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The simplest cause is a typo. An address like .cmo instead of .com, a missing letter, or an old bookmarked link produces this error every time.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Re-read the address carefully, checking the domain extension and spelling.<\/li>\n\n\n\n<li>Search for the site by name and click through from the results instead of typing it.<\/li>\n\n\n\n<li>Remove anything after the domain if you are unsure of the exact path.<\/li>\n\n\n\n<li>Update old bookmarks that point to a page that has since moved.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>How to Fix \u201cThis Site Can\u2019t Be Reached\u201d on Windows<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">These steps clear the two most common Windows-side causes: a stale DNS cache and a stuck network stack.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Open the Start menu, type cmd, right-click Command Prompt, and choose Run as administrator.<\/li>\n\n\n\n<li>Run these commands one at a time, pressing Enter after each:<\/li>\n<\/ol>\n\n\n\n<p class=\"alert-orange wp-block-paragraph\">ipconfig \/flushdns<br>ipconfig \/release<br>ipconfig \/renew<br>netsh winsock reset<\/p>\n\n\n\n<ol start=\"3\" class=\"wp-block-list\">\n<li>Restart your computer so the network reset takes effect.<\/li>\n\n\n\n<li>If the error remains, set your DNS to 1.1.1.1 or 8.8.8.8 under Settings &gt; Network &amp; Internet &gt; your adapter &gt; Edit DNS.<\/li>\n\n\n\n<li>Disable any VPN, proxy, or third-party firewall, then reload the page.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>How to Fix \u201cThis Site Can\u2019t Be Reached\u201d on Mac<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">MacOS caches DNS separately, and renewing the network lease resolves most connection errors.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Open Terminal from Applications, Utilities, Terminal.<\/li>\n\n\n\n<li>Flush the DNS cache by running this, then enter your password when prompted:<\/li>\n<\/ol>\n\n\n\n<p class=\"alert-orange wp-block-paragraph\">sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder<\/p>\n\n\n\n<ol start=\"3\" class=\"wp-block-list\">\n<li>Open System Settings, Network, select your active connection, then renew the DHCP lease under Details, TCP\/IP, Renew DHCP Lease.<\/li>\n\n\n\n<li>To change DNS, add 1.1.1.1 or 8.8.8.8 under Details, DNS.<\/li>\n\n\n\n<li>Turn off any VPN or proxy in Network settings, then reload the page.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>How to Fix \u201cThis Site Can\u2019t Be Reached\u201d on Mobile (iPhone and Android)<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">On phones, the fix is usually to reset the network path rather than clear the cache via command.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>On iPhone:<\/strong><\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Toggle Airplane mode on for ten seconds, then off, to force a fresh connection.<\/li>\n\n\n\n<li>Switch between Wi-Fi and mobile data to test whether one network is the problem.<\/li>\n\n\n\n<li>In Safari, clear history and website data under Settings &gt; Safari &gt; Clear History and Website Data.<\/li>\n\n\n\n<li>If it persists, reset network settings under Settings &gt; General &gt; Transfer or Reset iPhone &gt; Reset &gt; Reset Network Settings.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>On Android:<\/strong><\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Toggle Airplane mode off and on, or restart the phone.<\/li>\n\n\n\n<li>Switch between Wi-Fi and mobile data to isolate the network.<\/li>\n\n\n\n<li>Clear the Chrome app cache under Settings &gt; Apps &gt; Chrome &gt; Storage &gt; Clear cache.<\/li>\n\n\n\n<li>Reset network settings under Settings &gt; System &gt; Reset options &gt; Reset Wi-Fi, mobile, and Bluetooth.<\/li>\n<\/ol>\n\n\n\n<p class=\"alert-blue wp-block-paragraph\"><strong>Hosting on ScalaHosting? Check your server status in the SPanel dashboard&nbsp; \u2192<\/strong><br>Confirm your web server, database, and mail services are running before you troubleshoot anything else. You can find the information in the dashboard of your Admin Area or by going to Server Information &gt; Service Status<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Server-Side Fixes for Website Owners<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the page fails for everyone, the problem is on the server, and the fix is in your hands. Work through these in order.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Confirm the services are running.<\/strong> &#8220;This site can&#8217;t be reached&#8221; for every visitor usually means the web server (Apache or LiteSpeed) or the database (MySQL\/MariaDB) has stopped. Check service status first.<\/li>\n\n\n\n<li><strong>Check DNS and nameservers.<\/strong> Make sure the domain&#8217;s A record points to the correct server IP and that the nameservers resolve. A recent DNS change can take time to propagate.<\/li>\n\n\n\n<li><strong>Renew or reissue the SSL certificate.<\/strong> An expired certificate blocks secure connections. Confirm auto SSL is active and that the certificate covers both the domain and its www version.<\/li>\n\n\n\n<li><strong>Review the firewall.<\/strong> A rule that is too aggressive can drop legitimate traffic. Confirm ports 80 and 443 are open and that no security rule is blocking whole regions by mistake.<\/li>\n\n\n\n<li><strong>Look at resource usage.<\/strong> If CPU or RAM is maxed out, the server may refuse connections under load. Adding resources or moving to dedicated resources solves this.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Most &#8220;server down&#8221; incidents are not dramatic. A database process gets killed by a memory spike, and the site stays dark until someone notices. On <a href=\"https:\/\/www.scalahosting.com\/managed-cloud-hosting.html\"><strong>fully managed VPS hosting<\/strong><\/a>, closing that gap is the whole point. <a href=\"https:\/\/www.scalahosting.com\/spanel.html\"><strong>SPanel<\/strong><\/a>, our in-house control panel, runs a service watchdog every five minutes that checks the web server, database, mail, FTP, DNS, and every installed PHP version, and restarts anything that has stopped. A crashed service is usually back before your visitors notice. You can see what is running right now on the <strong>Service Status<\/strong> screen in your SPanel admin dashboard.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Some outages start as attacks. A flood of malicious requests can exhaust resources until the server stops answering. <a href=\"https:\/\/www.scalahosting.com\/website-security.html\"><strong>SShield<\/strong><\/a>, the real-time security system included with every managed plan, analyzes traffic and blocks known attack patterns before they reach your site, removing one of the common triggers for a server not responding. Pairing that with solid website security best practices keeps the attack surface small.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If your site cannot tolerate any downtime, a single server is a single point of failure. <a href=\"https:\/\/www.scalahosting.com\/cluster-hosting.html\"><strong>Managed Cluster Hosting<\/strong><\/a> spreads your workload across several coordinated nodes, so if one node fails, the others keep serving traffic automatically. Because every cluster is tailored to its workload rather than sold as a fixed package, the right next step is to talk to our technical team about what a cluster would look like for your setup.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>The Bottom Line<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">&#8220;This site can&#8217;t be reached&#8221; looks alarming, but it is one of the easiest errors to fix on the web. Read the sub-code, run the ten-second test to learn whose problem it is, then work the matching fix. Most visitor-side issues clear in a minute or two. If the page is down for everyone and the site is yours, the server is where to look, and the less time it spends there, the better.<\/p>\n\n\n<div class=\"shortcode-cta-new-wrap row cloudvps\">\r\n    <img decoding=\"async\" class=\"shortcode-logo\" src=\"\/blog\/images\/shortcode-bg-new-logo-cloudvps.svg\" alt=\"shortcode-logo\" title=\"shortcode-logo\"\/>\r\n    <div class=\"shortcode-cta-img col-10 col-sm-7 col-md-5\">\r\n        <img decoding=\"async\" class=\"shortcode-bg\" src=\"\/blog\/images\/shortcode-bg-new-cloudvps.webp\" alt=\"shortcode-bg\" title=\"shortcode-bg\"\/>\r\n    <\/div>\r\n    <div class=\"shortcode-cta-content col-12 col-md-7\">\r\n        <div class=\"content\">\r\n            <div class=\"heading\">Supercharge Your Business with an All-inclusive Fully Managed Cloud<\/div>\r\n            <div class=\"list-wrap\">\r\n                <div class=\"list\">\r\n                    <div><b>Free, Effortless & No-Downtime Migration<\/b><\/div>\r\n                    <div><b>Anytime Unconditional Money-back Guarantee<\/b><\/div>\r\n                    <div><b>Full Scalability & 24\/7 Expert Cloud Support<\/b><\/div>\r\n                <\/div>\r\n            <\/div>\r\n            <div class=\"btn-wrap row\">\r\n                <div class=\"col-auto\">\r\n                    <a class=\"button green\" href=\"https:\/\/www.scalahosting.com\/managed-cloud-hosting.html\">Start Now<\/a>\r\n                <\/div>\r\n                <div class=\"col-auto\">\r\n                    <button class=\"button brown_outer\" title=\"Contact Sales\" onclick=\"chatChangeVisibility(this, 'maximize', {}, 5);\">Chat with our Experts<\/button>\r\n                <\/div>\r\n            <\/div>\r\n        <\/div>\r\n    <\/div>\r\n<\/div>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Frequently Asked Questions<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Q:<\/strong> <strong>Why does it say &#8220;This site can&#8217;t be reached&#8221; on only one website?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A:<\/strong> Because the problem is specific to that site, not your whole connection. If every other site loads but this one doesn&#8217;t, the issue is likely the site&#8217;s server or DNS, or you have a stale cached address for it. Clear your cache and try another network. If it still fails only there, the issue is on the site&#8217;s end.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Q:<\/strong> <strong>How do I know if a website is down for everyone or just me?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A:<\/strong> Open the site on another device or network, such as your phone on mobile data. If it loads there, the problem is your device or connection. If it fails everywhere, the server is down, and only the owner can fix it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Q:<\/strong> <strong>Does &#8220;This site can&#8217;t be reached&#8221; mean I have a virus?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A:<\/strong> Almost never. The error is a network or server problem, not a malware symptom. That said, an aggressive antivirus, a rogue browser extension, or a proxy set by unwanted software can block connections, so it is worth disabling recent extensions and security tools to test.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Q:<\/strong> <strong>How do I fix a DNS error causing this message?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A:<\/strong> Flush your DNS cache, restart your router, and switch to a public resolver like 1.1.1.1 or 8.8.8.8. On Windows, run ipconfig \/flushdns; on Mac, run sudo dscacheutil -flushcache. If the domain still will not resolve anywhere, its DNS records need attention from the site owner.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Q:<\/strong> <strong>Why did the error appear right after I set up SSL on my site?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A:<\/strong> A newly installed certificate that does not cover the exact domain, or that has not finished propagating, can break the secure connection. Confirm the certificate matches both the root domain and its www version, that auto SSL is active, and that nothing is forcing an outdated protocol.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Q:<\/strong> <strong>The site works on mobile data but not on my home Wi-Fi. Why?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A:<\/strong> Something on your home network is blocking it, usually the router&#8217;s DNS cache, a firewall rule, or a proxy. Restart the router, switch the device to a public DNS resolver, disable any VPN or filtering software, and reload.<\/p>\n\n\n\n<script type=\"application\/ld+json\">\n    {\n      \"@context\": \"https:\/\/schema.org\",\n      \"@type\": \"FAQPage\",\n      \"mainEntity\": [{\n        \"@type\": \"Question\",\n        \"name\": \"Why does it say 'This site can't be reached' on only one website?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"Because the problem is specific to that site, not your whole connection. If every other site loads but this one doesn't, the issue is likely the site's server or DNS, or you have a stale cached address for it. Clear your cache and try another network. If it still fails only there, the issue is on the site's end.\"\n        }\n      }, {\n        \"@type\": \"Question\",\n        \"name\": \"How do I know if a website is down for everyone or just me?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"Open the site on another device or network, such as your phone on mobile data. If it loads there, the problem is your device or connection. If it fails everywhere, the server is down, and only the owner can fix it.\"\n        }\n      },{\n        \"@type\": \"Question\",\n        \"name\": \"Does 'This site can't be reached' mean I have a virus?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"Almost never. The error is a network or server problem, not a malware symptom. That said, an aggressive antivirus, a rogue browser extension, or a proxy set by unwanted software can block connections, so it is worth disabling recent extensions and security tools to test.\"\n        }\n      },{\n        \"@type\": \"Question\",\n        \"name\": \"How do I fix a DNS error causing this message?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"Flush your DNS cache, restart your router, and switch to a public resolver like 1.1.1.1 or 8.8.8.8. On Windows, run ipconfig \/flushdns; on Mac, run sudo dscacheutil -flushcache. If the domain still will not resolve anywhere, its DNS records need attention from the site owner.\"\n        }\n      },{\n        \"@type\": \"Question\",\n        \"name\": \"Why did the error appear right after I set up SSL on my site?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"A newly installed certificate that does not cover the exact domain, or that has not finished propagating, can break the secure connection. Confirm the certificate matches both the root domain and its www version, that auto SSL is active, and that nothing is forcing an outdated protocol.\"\n        }\n      },{\n        \"@type\": \"Question\",\n        \"name\": \"The site works on mobile data but not on my home Wi-Fi. Why?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"Something on your home network is blocking it, usually the router's DNS cache, a firewall rule, or a proxy. Restart the router, switch the device to a public DNS resolver, disable any VPN or filtering software, and reload.\"\n        }\n      }]\n    }\n<\/script>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>TL;DR &#8220;This site can&#8217;t be reached&#8221; is the message Chrome and Edge show when your browser cannot open a page. &#8230;<\/p>\n","protected":false},"author":106,"featured_media":75126,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_seopress_titles_title":"This Site Can't Be Reached: Complete Fix %%sep%% %%sitetitle%%","_seopress_titles_desc":"\"This site can't be reached\" in Chrome or Edge? Learn what the error means and how to fix it on Windows, Mac, mobile, and the server, step by step.","_seopress_robots_index":"","_seopress_robots_follow":"","_seopress_robots_imageindex":"","_seopress_robots_snippet":"","_seopress_robots_primary_cat":"","_seopress_robots_breadcrumbs":"","_seopress_robots_freeze_modified_date":"","_seopress_robots_custom_modified_date":"","_seopress_robots_canonical":"","_seopress_social_fb_title":"","_seopress_social_fb_desc":"","_seopress_social_fb_img":"","_seopress_social_fb_img_attachment_id":0,"_seopress_social_fb_img_width":0,"_seopress_social_fb_img_height":0,"_seopress_social_twitter_title":"","_seopress_social_twitter_desc":"","_seopress_social_twitter_img":"","_seopress_social_twitter_img_attachment_id":0,"_seopress_social_twitter_img_width":0,"_seopress_social_twitter_img_height":0,"_seopress_redirections_value":"","_seopress_redirections_enabled":"","_seopress_redirections_enabled_regex":"","_seopress_redirections_logged_status":"","_seopress_redirections_param":"","_seopress_redirections_type":0,"_seopress_analysis_target_kw":"","_seopress_news_disabled":"","_seopress_video_disabled":"","_seopress_video":[],"_seopress_pro_schemas_manual":[],"_seopress_pro_rich_snippets_disable_all":"","_seopress_pro_rich_snippets_disable":[],"_seopress_pro_schemas":[],"footnotes":""},"categories":[3],"tags":[],"class_list":["post-75125","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-web-hosting-in-general"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/posts\/75125","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/users\/106"}],"replies":[{"embeddable":true,"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/comments?post=75125"}],"version-history":[{"count":5,"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/posts\/75125\/revisions"}],"predecessor-version":[{"id":75135,"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/posts\/75125\/revisions\/75135"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/media\/75126"}],"wp:attachment":[{"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/media?parent=75125"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/categories?post=75125"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/tags?post=75125"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}