How to Easily Fix This Site Can’t Be Reached Error in WordPress (8 Ways)

Are you looking for the easiest way to fix the ‘this site can’t be reached’ error in WordPress?

You can get this error on any website, including third-party sites and your own WordPress blog. If this error shows up on your own site, then it’s a big problem as it can stop you from accessing the admin area.

In this article, we will show you how to easily fix the ‘this site can’t be reached’ error.

How to easily fix this site can't be reached error in WordPress

What Is the ‘This Site Can’t Be Reached’ Error in WordPress?

There are lots of common WordPress errors, but ‘this site can’t be reached’ is especially frustrating because the message is vague, and it doesn’t tell you what to do next.

The Chrome 'site can't be reached' error

In the worst-case scenario, this error can stop you from visiting your own website. That will make it difficult to test your WordPress site, add new content, install security updates, and make other important changes.

Usually, the error means that something is stopping the browser from accessing the destination website. This could be anything from an internet outage, to a misconfigured network, or even an issue with your DNS settings.

In this guide, we’ll take a closer look at why you may be seeing this error, including exploring the different error codes. When you encounter a problem, you’ll typically want to solve that problem as quickly as possible.

With that being said, we have 8 ways to troubleshoot this WordPress error, so you can fix the ‘site can’t be reached’ problem quickly.

If you’re unsure what’s causing the issue, then we recommend starting with step one since it’s the easiest. However, if you prefer to jump straight to a particular step, then you can use the quick links below.

1. Check Your Internet Connection

When troubleshooting an error, it’s smart to try the simplest fix first. To start, check that you’re currently connected to the internet.

If there is no obvious problem with the connection, then the next step is restarting your internet connection. Similar to switching your computer off and on, resetting your entire connection can fix all kinds of small problems and get you back on track.

We recommend disconnecting your router from its power supply and then waiting at least 1 minute before reconnecting it. You can then try visiting the website again to see whether this has removed the error message.

2. Clear the Browser Cache

Downloading files from a WordPress hosting server located far away can take a lot of time.

To solve this problem, most modern web browsers store files, data, and other content from the websites you visit. The browser can then simply load this cached content from the local computer, rather than re-downloading it from a remote server.

This helps websites to load faster, but it can sometimes cause problems. For example, cached content can become outdated or get corrupted over time.

Thankfully, it’s easy to clear the browser cache. If you’re using Google Chrome, then simply click on the three-dotted icon in the upper-right corner.

Then, select ‘More Tools,’ followed by ‘Clear Browsing Data….’

How to clear the browser cache in Google Chrome

In the popup that appears, check the box next to ‘Cached images and files.’

Google Chrome will clear the entire cache by default. Another option is to open the ‘Time Range’ dropdown and tell Chrome to only clear content that was cached during a particular time period.

Fixing the site can't be reached error in WordPress

Once you’ve done that, you can check or uncheck any of the other options. For example, the ‘Browsing History’ checkbox is selected by default, but you can uncheck this box if you want to keep your browsing history.

When you’re ready, click on ‘Clear data.’

Emptying the Chrome cache

Google Chrome will now empty the browser cache. Once it’s finished, try revisiting the website to check whether you’re still getting the ‘this site can’t be reached’ error.

For all other browsers, see our beginners guide on how to clear the browser cache in any browser.

3. Disable Your Firewall or Antivirus Software

Antivirus and firewall plugins can keep you safe, but they can also block websites that are perfectly trustworthy.

This might be a problem with how your security plugins and software are configured. For example, your settings may be too strict.

Other times, the website may be set up in a way that triggers your security software even if that website doesn’t pose a real threat.

For instance, if you’re still building your WordPress website, then you might not have an SSL certificate yet. Many firewalls will stop you from visiting a site that doesn’t have a valid certificate, so this may trigger the error.

To test whether a firewall or antivirus program is blocking the connection, simply disable that software. Then, visit the website that was showing the ‘this site can’t be reached’ error.

If the site loads without a problem, then you’ll know that the antivirus program or firewall was to blame.

If this is the case, then we don’t recommend disabling it completely.

Instead, it’s smart to check the software’s settings to see whether you can whitelist a particular website. In this way, you can access the site while still protecting yourself against hackers, viruses, and other digital threats.

If you’re not sure where to find these settings, then try checking the software’s official documentation, forums, or social media pages for more information. Depending on your software license, you may also be able to contact customer support or the developer for help.

For more tips on protecting yourself against hackers without triggering the ‘this site can’t be reached’ error, please see our ultimate WordPress security guide.

4. Reset Your Virtual Private Network

A Virtual Private Network (VPN) can protect your privacy, keep your information secure, and allow you to visit sites that are blocked or censored in your location.

However, if you’re using a VPN then your connection may drop, or the VPN may not recognize the IP address that you’re using. Some VPNs will reconnect automatically if they encounter a problem, but you may have to reconnect manually.

If you get the ‘site can’t be reached’ error when using a VPN, then we recommend checking your provider’s website or documentation for instructions on how to reset your VPN.

5. Disable Your Proxy Server

A proxy server sits between you and the websites you’re trying to visit. Many people use these ‘middle-man’ servers as an extra layer of security, or to cache data.

If your proxy server can’t connect to a website, then you’ll see the ‘site can’t be reached’ error. You may also get this error if you can’t connect to the proxy server in the first place.

In this case, the easiest fix is to simply disable the proxy server. If you’re on a Mac, then go ahead and click the ‘Apple’ icon in the toolbar.

The System Preferences settings on macOS

Then, select ‘System Preferences…’

In the popup that appears, click on ‘Network.’

Fixing the 'site can't be reached' error in WordPress

In the left-hand menu, select the network where you want to disable the proxy settings.

Once you’ve done that, click on the ‘Advanced…’ button.

The Advanced network settings on Mac

In the popup, simply select the ‘Proxies’ tab.

You can now uncheck all of the protocols listed under ‘Select a protocol to configure.’

The proxy server settings

Finally, click on the ‘OK’ button to save your changes. You can now try visiting the website to see whether you can access it without any problems.

6. Flush Your DNS cache

Similar to the browser cache, your computer stores the IP addresses of all the websites you visit. This means the browser doesn’t have to look up the same IP address multiple times.

This helps websites to load faster, but the cached DNS information can get outdated. This may trigger a ‘site can’t be reached’ error, particularly if the site has moved to a new domain name or you’ve moved WordPress to a new host.

By flushing your DNS cache, you’ll get the very latest information about a website, including its new domain name or address.

To help you out, we’ve created a complete guide on how to clear your DNS cache for Mac, Windows, and Google Chrome.

7. Change Your DNS Server

DNS is like the internet’s phone book. Instead of listing people’s names and phone numbers, the DNS lists domain names and their corresponding IP addresses.

Your internet service provider assigns you a DNS server automatically. However, sometimes this server may be unavailable, or it might have the wrong information.

If your browser doesn’t have a site’s correct address, then you’ll get a ‘this site can’t be reached’ error.

You can solve this problem by switching to a different public DNS server, such as Google Public DNS. You can use any public server you want, but just be aware that the DNS provider will be able to see all the websites you visit.

Many providers also collect personal information, such as your business email address, name, and phone number.

With that being said, it’s smart to research your DNS provider carefully.

Once you’ve found a DNS server that you want to use, it’s time to switch to that server. On Mac, this means selecting the ‘Apple’ icon in the toolbar and then clicking on the ‘System preferences…’ option.

The macOS System preferences...

In the popup that appears, select ‘Network’ and then click on the ‘Advanced…’ button.

Once you’ve done that, open the ‘DNS’ tab.

Fixing the site can't be reached error by changing the DNS server

In the bottom-left corner, click on the ‘+’ button.

This adds a new DNS server with the address 0.0.0.0.

Switching the DNS server settings

You can now go ahead and type in the numbers for the public server that you want to use.

After that, simply click on the ‘OK’ button to save your changes.

Switching to a public DNS server to fix the site can't be reached error

This takes you back to the previous popup.

To start using your new DNS server, click on the ‘Apply’ button.

How to switch to a different DNS server

Finally, you’re ready to visit the website to see whether this has removed the error message.

8. Reset the TCP/IP Settings

Transmission Control Protocol/Internet Protocol (TCP/IP) is a set of protocols that control how data is sent and received over the internet.

If there’s a problem with how your internet connection is configured, then renewing your TCP and IP protocol will return the connection to its default settings, which may solve the problem.

To reset the TCP/IP settings on Mac, select the ‘Apple’ icon in the toolbar and then click on ‘System Preferences…’

In the popup that appears, select ‘Network’ and then click on the ‘Advanced…’ button. Once you’ve done that, open the ‘TCP/IP’ tab.

Changing the TCP/IP settings

On this screen, go ahead and click on the ‘Renew DHCP Lease’ button.

That’s it. You can now try visiting the website or blog, to check whether you still get the same ‘site can’t be reached’ error.

What Causes ‘This Site Can’t Be Reached’ Error in WordPress?

There are a few different reasons why you may get this error message, but the code that appears next to the message can help you pinpoint the cause.

Let’s take a closer look at these codes and what they mean for your WordPress blog.

  1. ERR_CONNECTION_RESET

Sometimes, you’ll see an ERR_CONNECTION_RESET code next to the ‘site can’t be reached’ error. Most of the time, this means there’s a problem with your internet connection.

The most obvious problem is an internet outage, but there’s also software and settings that can interfere with the connection and trigger an ERR_CONNECTION_RESET. For example, VPNs and proxy servers can sometimes cause this error code.

  1. DNS_PROBE_FINISHED_NXDOMAIN

Domain Name System (DNS) lets you connect to websites by matching a user-friendly domain name such as www.wpbeginner.com, with the ID of the server where this website is stored.

You’ll get this error code if Google Chrome can’t resolve the domain name or address for the website that you’re trying to access.

Since it can’t connect, the browser assumes that the domain name doesn’t exist. It then shows a DNS_PROBE_FINISHED_NXDOMAIN error code, where the NXDOMAIN part of the error stands for ‘non-existent domain. ‘

If you see this error code next to the ‘site can’t be reached’ message, then it usually means there’s a problem with how your DNS settings are configured.

To learn more about this error code, please see our guide on how to easily fix the DNS_PROBE_FINISHED_NXDOMAIN error.

We hope this article helped you learn how to easily fix ‘this site can’t be reached’ error in WordPress. You can also go through our guide on the difference between domain name and web hosting and the best email marketing for small businesses.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

The post How to Easily Fix This Site Can’t Be Reached Error in WordPress (8 Ways) first appeared on WPBeginner.

How to Easily Fix the DNS_PROBE_FINISHED_NXDOMAIN Error

Recently, one of our readers asked what they could do to fix the DNS_PROBE-FINISHED_NXDOMAIN problem?

This error message appears in Chrome when your browser can’t connect to the website you’ve requested. Other browsers use different messages to display this error.

In this article, we’ll show you how to easily fix the DNS_PROBE_FINISHED_NXDOMAIN error, and how to avoid it in the future.

Fixing the DNS_PROBE_FINISHED_NXDOMAIN error

What Is the DNS_PROBE_FINISHED_NXDOMAIN Error?

The DNS_PROBE_FINISHED_NXDOMAIN error is a Google Chrome error message which appears when the browser is unable to find the website you are trying to access.

An example of the DNS_PROBE_FINISHED_NXDOMAIN error in Google Chrome

This error appears when the DNS (Domain Name System) cannot find or connect to the IP address for that website.

Your browser then assumes that the website domain name doesn’t exist. The NXDOMAIN part of the error stands for ‘non-existent domain.’

To understand more, please take a look at our guide on how domain name / DNS work (visual explanation).

The error looks different in other browsers. For instance, here’s how it looks in Firefox:

An example of the DNS_PROBE_FINISHED_NXDOMAIN error in Firefox

If you’re seeing this error when you try to access your own WordPress site, you may think there’s a problem with your site.

The good news is that your site is likely working fine. The problem is that your computer isn’t able to connect to it.

With that said, let’s see how to troubleshoot and fix this error.

How to Fix the DNS_PROBE_FINISHED_NXDOMAIN Error?

There are several ways to fix the DNS_PROBE_FINISHED_NXDOMAIN error. However, it’s important to first check that it really is an error.

Before doing anything else, you should check that you typed the domain name correctly.

For instance, if you accidentally typed incorrect spelling for a domain name, then your browser may not be able to find that domain and give this error.

Even if you clicked on a link, you should still check that the domain name is correct. It could have been mistyped by whoever created the link.

If you’re certain that the domain name is correct, then click the ‘Reload’ or ‘Try again’ button.

Clicking the button to reload the website

Next, you should try accessing the website from a mobile phone (4G network), so you can see whether the issue is with your device or WIFI connection.

If the website doesn’t load on your mobile phone either, then you need to immediately contact your WordPress hosting provider because this means that your website is down.

However if the website loads just fine on your mobile phone, then you know the issue is either with your computer or your WiFi connection.

Let’s try solving that.

The first thing you should try is restarting your computer. If that doesn’t help, turn your internet modem off and on. These steps may automatically clear DNS and network-related issues.

If the error is still appearing, then you may need to try the following methods. We recommend starting with the first one and working through them.

Clear Your Browser’s Cache

To clear your cache in Chrome, go to the page chrome://settings/clearBrowserData in your browser. This should give you a popup window where you are able to clear your cache.

First, set the time range to ‘All time’ then check just the ‘Cached images and files’ box. Next, click the ‘Clear data’ button.

Clearing cached images and files in Chrome

If you aren’t using Chrome, check out our article on clearing your browser cache for instructions for all major browsers.

Now, try the website again. If it still shows the error message DNS_PROBE_FINISHED_NXDOMAIN, simply try the next solution.

Turn Off Experimental Chrome Features

If you’ve enabled any of Chrome’s experimental features, then these could be causing the DNS_PROBE_FINISHED_NXDOMAIN error.

To turn these off, go to chrome://flags/ in your browser then click the ‘Reset all’ button at the top.

Resetting all experiments in Chrome

If the website you want to access still shows the error, try the next solution.

Flush Your Computer’s DNS Cache

Your computer often saves (caches) the IP addresses of websites that you’ve previously visited. If the website’s IP has changed, then that can cause the DNS_PROBE_FINISHED_NXDOMAIN error.

Here’s how to flush your DNS cache.

Note: These instructions are for Windows 10. For macOS instructions, check out our guide on clearing your DNS cache.

First, search for the Command Prompt app. Go ahead and open it up.

Tip: If you’re not logged in as an administrator, use the ‘Run as administrator’ option.

Opening the Command Prompt app

Next, type ipconfig/flushdns then press Enter on your keyboard. You should then see a success message.

Typing the command into the Command Prompt window to flush the DNS cache

Now, try accessing the website again. If the error message DNS_PROBE_FINISHED_NXDOMAIN still appears, try the next solution.

Release and Renew Your IP Address

The next step is to renew your computer’s IP address on the internet.

Go ahead and open up the Command Prompt app, as shown in the previous step. Next, enter the following commands in this order. Press Enter after each one.

ipconfig /release

ipconfig /flushdns

ipconfig /renew

You will see quite a few lines of information after entering the first and third commands. This is normal.

Renewing your computer's IP address

If the DNS_PROBE_FINISHED_NXDOMAIN error still appears after this, try the next solution.

Use Google’s Public DNS Servers

By default, your computer uses the DNS server from your internet service provider (ISP). You can change this to use Google’s public DNS server instead.

On Windows, open your Control Panel then go to Network and Internet » Network and Sharing Center. Then, click the ‘Change adapter settings’ link on the left hand side.

Clicking the Change adaptor settings link

You will see a list of connections. Right-click on your current connection and select the Properties option.

Click on the Properties for your active internet connection

Next, click on the Internet Protocol Version 4 (TCP/IPv4) and then click the Properties button.

Selecting the Internet Protocol Version 4 (TCP/IPv4) option

After that, you need to click the ‘Use the following DNS server addresses’ option and enter these DNS servers:

Preferred DNS server: 8.8.8.8
Alternative DNS server: 8.8.4.4

Then, click the OK button to save your changes.

Using the details for Google's public DNS servers

Try the website again to see if the DNS_PROBE_FINISHED_NXDOMAIN error is fixed. If not, try the final method.

Check Your Computer’s ‘hosts’ File

The hosts file is a file that your computer uses to map domain names to IP addresses. If the website is incorrectly recorded in this file, that can be the cause of the DNS_PROBE_FINISHED_NXDOMAIN issue.

On Windows, you can find this file through File Explorer. First, open File Explorer, then find the Windows folder on your computer. It’s normally in the C:\ drive. Mac users can find the file under /private/etc/hosts/ folder.

Next, go to System32 » drivers » etc. Here, you need to locate the hosts file and double click on it to open it. If you’re prompted to choose an app, use Notepad.

Finding the 'hosts' file on your computer

Now, check to see if the website’s address is in the hosts file. If it is, delete it along with the IP address next to it. Then, save the file.

Checking the contents of the 'hosts' file on your computer

After doing this, the DNS_PROBE_FINISHED_NXDOMAIN error should hopefully no longer appear for that site.

We hope this article helped you learn how to fix the DNS_PROBE_FINISHED_NXDOMAIN error. You might also like our article on the most common WordPress errors and how to fix them.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

The post How to Easily Fix the DNS_PROBE_FINISHED_NXDOMAIN Error appeared first on WPBeginner.