If you suspect your website or hosting account was compromised, you must act quickly to mitigate potential damage. The longer you wait, the worse things will become. You could even be on the hook for liability lawsuits.

Follow the steps below to regain control and secure your website.

Change All Passwords

The first step when compromise is suspected is changing ALL passwords.

Depending on your configuration, the password reset process may involve updating FTP/SFTP passwords, Database Users, Website Logins, Email Accounts, and anything else associated with your website.

Fixing a breach will mean nothing if the individual still has all your passwords.

Use strong, unique passwords for each account, and ensure you do NOT reuse any previously used passwords, as once a password is compromised, it will remain compromised indefinitely and cannot be reused, even on another service.

If you’re not sure how to make a password stronger, feel free to use our password generator. In a single click, it will generate a password that is more difficult to crack.

Scan Your Local Devices for Malware:

Run thorough antivirus and malware scans on all devices you use to access your website or hosting account. Remove any detected threats promptly to prevent re-infection.

Password-based compromises are often the result of malware on your PC or other device that sniffs your password.

Review Website Files

Check all files and directories on your website for any unauthorized modifications, unfamiliar files, or suspicious code injections.

When a website is compromised, malicious files are often created or modified at approximately the same time. After a malicious file is found, searching for other files modified around the same time may identify additional malicious files.

If you’re using WordPress, the Wordfence security plugin constantly scans your files and keeps you apprised of any changes. The best part is that it’s free to use, though, it does have some great features if you upgrade.

Restore Clean Backups

Once you have confirmed that your website is compromised, restoring a known clean backup is the most effective way to remove the malware.

If you need assistance restoring a backup or don’t have a known clean backup, GreenGeeks takes regular server-side backups and offers one free restore from the server-side backups per month.

If you’re using WordPress, it’s probably a good idea to install a backup plugin. A lot of these will create backups automatically while storing them on separate servers, such as Dropbox or OneDrive.

Update Website Components

Outdated software is often vulnerable to exploitation of known vectors by attackers, such as out-of-date coding or components.

To prevent attacks against known security vulnerabilities, ensure that all website components for your website CMS are up-to-date with the latest security patches, including Themes, Plugins, or other Extensions.

Enabling Automatic updates for all components will ensure you’re always using the most up-to-date software versions for your website, minimizing the risk of compromise.

Monitor Website Activity

Implement website activity monitoring tools or security plugins to track unauthorized access attempts, file modifications, or suspicious behavior. Regularly review access logs for any anomalies.

For WordPress, GreenGeeks recommends WP Cerber to help provide enhanced security measures and strengthen your website installation overall.

Implement Additional Security Measures

Enhance your website’s security by implementing additional measures such as two-factor authentication and regular security audits.

GreenGeeks offers 2FA for both the GreenGeeks Dashboard and Hosting Account to secure your account.

WordPress and other CMS applications offer 2FA plugins and extensions; the exact steps will vary depending on your website’s platform. Nonetheless, there are plenty of plugins available, so pick one that best suits your needs.

If you require assistance implementing 2FA within your GreenGeeks Dashboard or Hosting Account, the GreenGeeks Support Team will assist you.

Communicate with Your Users

If your website collects user data or provides services to customers, inform them about the security incident, the actions you’ve taken to address it, and any steps they should take to secure their accounts.

Each State/Country has different disclosure requirements for a cyber security breach, and you must follow any specific notification requirements for your state or jurisdiction.

For the United States of America, refer to the National Association of Attorneys General & National Conference of State Legislatures for data breach guidelines. Note that these are general guidelines and you’ll need to consult with legal counsel for specific guidance on reporting requirements.

WordPress Admin Checks

A commonly overlooked problem is when hackers or malicious code injects a new admin or user into your website without your knowledge. This can give someone backend control of your site who can quickly undo any fixes you may have implemented.

Check your user list in WordPress to ensure no new admins or other users were added. Even if WordPress gives these unknowns “Subscriber” status (the lowest privilege in WordPress), it’s better to delete them immediately.

Conclusion

By following the above steps promptly and thoroughly, you can restore your website to working order and minimize the potential for your website to be compromised going forward.

Note that GreenGeeks may require additional actions to secure your account to guarantee the integrity of the server.

If you have any questions about how to apply one or more steps to your GreenGeeks hosting account, the GreenGeeks Support Team will be happy to assist you from your GreenGeeks Dashboard.

The post What to Do After Your Website or Web Hosting Is Compromised appeared first on GreenGeeks.

As a website owner, particularly if you’re hosting a WordPress website, you should be concerned about Error 520. This is because it can indicate that visitors cannot access your website due to issues on “your side.”

This can lead to frustrated visitors and potentially lost business.

In this article, we’ll review some of the common causes of Error 520 and provide tips for troubleshooting and fixing the issue.

How Websites are Rendered

To understand error 520 better, let’s take a quick high-level look at how websites and webpages are rendered through web browsers.
Skip this bit if you already know the nuances of how websites are rendered.

Or, if you’re familiar with concepts such as DNS, proxy servers, CDN, SSL handshake, and the like.

When a visitor types in a website URL into the web browser and presses Enter, the browser, first off, sends a DNS query to the Domain Name System (DNS) server. This is usually provided by the Internet Service Provider (ISP).

The DNS server is responsible for translating the website’s domain name (the one you entered in words) into the corresponding IP address of the server the website is hosted on.

The browser then sends a request to the website’s server address (which it received from the DNS server.) The request is relayed to the website server’s (web server’s) firewall.

This is where the request’s journey “through the internet” unfolds to ultimately render the website on the user’s browser.

If the website is protected (or served) by a Content Delivery Network (CDN) like Cloudflare, which is usually the case, the request first goes to the CDN’s servers. These act as forward proxy servers.

The server (also called the edge server) checks its cache to see if it has the requested content. If it does, it sends the content back to the user’s browser. If it doesn’t, it acts as a reverse proxy server and relays the request to the web server hosting the website and its content.

To do so, the reverse proxy server needs to know the IP address of the web server. This is where DNS comes in again.

A Quick Primer on Firewalls and CDN

CDNs are a geographically distributed network of servers (edge servers) that work together to provide fast delivery of internet content. They are designed to serve content to end-users with high availability and high performance.

Cloudflare is a widely used household name of a CDN that provides a range of services, including content delivery, DDoS protection, and web security.

From the purview of the website and the server it’s hosted on, a Firewall creates a barrier between the trusted internal network and untrusted external networks, such as the Internet.

Based on security policies, it monitors and filters incoming and outgoing traffic.

Coming back to how website content is relayed, the request from the CDN goes through the web server’s firewall and into the web server, where it is processed and responded to (with requested content) back to the user’s browser.

It is, in turn, rendered for the user to view.

Now that we have a broad understanding of how websites are rendered let’s look at how they may be obstructed, resulting in error 520.

How Error 520 Occurs

By displaying error 520, the server is essentially saying that it cannot process the request from the user’s browser. Hence, the website is currently unavailable.

Here are some ways it can occur:

PHP Applications Crashing

Sometimes, the website code written in PHP can crash or stop working properly. When this happens, it can cause Error 520 because the server cannot process the request from the web browser.

Incorrectly Configured DNS Records

At any point during the journey of the web browser’s requests, if the DNS records of your website are not set up correctly and in accordance with the web server, the web browser may not be able to find the website’s server, which can cause Error 520.

Corrupt or Incorrectly Configured .htaccess File

An .htaccess file is a configuration file associated with your website code that tells the web server how to handle certain requests. If this file is damaged or has incorrect settings, it can cause Error 520 because the server doesn’t know how to handle the request properly.

Large Request Headers and Excessive Cookie Usage

When a web browser requests a server, it sends along information called “headers,” which include things like cookies (which remember your preferences on a website). If there are too many headers or cookies, it can overload the server and cause Error 520.

Missing Request Headers

In contrast to the above point, sometimes, the web browser may not send all the necessary information to the server when making a request, and it may not be able to process the request correctly.

Empty Response From Server

It can also happen that the web server or the proxies do not send any response back to the browser, resulting in error 520 because the browser wouldn’t know what to do next.

A Firewall Blocking the Connection

Error 520 can occur if there is a firewall or other security measure in place that is blocking the connection between the reverse proxy server and the origin server.

SSL/TLS Handshake Failure

When a user connects to a website over HTTPS, their browser and the web server engage in an SSL/TLS handshake to establish a secure connection. This involves a series of steps to negotiate the encryption settings and exchange keys for encrypting and decrypting data.

Any issue with the SSL/TLS certificate configuration on the origin server can cause a handshake failure with the reverse proxy server and result in Error 520.

For instance, this can happen if the certificate has expired, is misconfigured, or is invalid.

Overloaded Server

Error 520 also arises if the origin server is overloaded and cannot respond to requests from the reverse proxy server.

How to Troubleshoot and Fix Error 520

There is no need to panic when you come across Error 520. There are several ways to identify and troubleshoot the root cause of the error.

Wait it Out

If you encounter an Error 520 while trying to access a website, you should wait a few minutes and refresh the page to see if the issue has been resolved. The error may arise due to temporary network or server issues.

For instance, the server or network may be experiencing a high volume of traffic or temporary overload that causes it to be unable to process requests.

During this time, the server may be fixing the underlying issue or automatically scaling up its resources to handle the increased load. So, it’s only logical that you give it time to start processing requests again.

Pause/Disable Cloudflare Temporarily

If you use Cloudflare as your reverse proxy server, you can temporarily disable Cloudflare to see if the error disappears. If it does, then you’d know the issue lies with Cloudflare and go about troubleshooting the same.

• Log in to your Cloudflare account
• Go to the Overview tab on the left-hand panel
• Scroll down to the Advanced Actions section
• Click on “Pause Cloudflare on Site” to temporarily disable Cloudflare from your website

Check and UpdateDNS Records

Login to your DNS provider account, the way to which could also be through your hosting provider, Cloudflare, or similar services. Check if the records are correctly configured, particularly the CNAME (Canonical Name) records.

CNAME record tells the DNS resolver to look up the IP address of the domain specified in the CNAME record and use that IP address as the destination for the request.

Depending on the DNS provider, updating the records could take a few minutes to several hours for the changes to take effect globally.

Restart PHP

Log in to your web server or hosting account, and locate the PHP configuration file for your website. It is usually named php.ini or located in a directory named conf.d or php.d.

Edit/review the file and make sure that the settings (such as memory limits, execution time limits, and file upload size limits) are configured correctly.

Enter your server’s command to restart PHP. Sometimes, the way to restart PHP is by restarting the web server itself. The commands vary depending on the type of web server and the software it runs.

Check Web Server Error Logs

Error logs can provide valuable information about an incident or error, such as where and why. Depending on the hosting provider, locating or generating error logs may differ.

Most error logs share a similar structure and offer essential details such as the incident’s date and time, the client’s IP address (if applicable), the error message, and a path to the affected resource or line of code responsible for the issue.

Scrutinize them and try to identify the root cause.

Clear the Website Cache

Clearing a website’s cache deletes the temporary files and data stored on the website’s server, like images, scripts, stylesheets, and other types of website content. This will force the webserver to reload all its content from scratch, which can help resolve errors like Error 520.

Clearing the cache can also cause temporary performance issues, as the website must load all its content again.

It’s essential to weigh the benefits and drawbacks before clearing the cache. Ensure all necessary backups are in place before making any changes to the website’s configuration.

On that note, you may want to clear your browser cache on the off chance that the issue stems from your browser.

Check HTTP Error Response With a cURL Command

Running a cURL command in your command terminal, Windows key + R” and typing “cmd” (Windows) | Applications > Utilities > Terminal (MacOS), simulates a request to your website’s server and receives a detailed response.

The command format is as follows: curl -I http://example.com

By understanding what a successful response and an error response look like after a cURL command execution, you can verify that the web server is configured correctly and responding to requests.

You can also retrieve the server’s HTTP response headers and review the status codes and messages. Leave the review part to the experts (the support team) if you think it may be too much to digest.

Disable .htaccess

If your web server is powered by Apache, which is most likely the case, disabling the .htaccess used to configure web server settings on Apache servers can help resolve Error 520.

You can also verify that Cloudflare IPs are not blocked in .htaccess or your firewall.

The .htaccess (hypertext access) is a configuration file for Apache-hosted sites. For the unacquainted, Apache is a popular open-source web server software.

When there is a conflict between the rules in the .htaccess file and the server settings, or if the file is corrupted, the browser can return Error 520.

Check Headers and Cookies

Large headers and cookies can exceed the maximum allowed size limit of web servers or CDNs (like Cloudflare) which can cause Error 520.

For instance, at the time of writing this piece, the maximum threshold size of Cloudflare’s request headers is 32 KB, 16 KB per individual header.

Here are the steps to check headers and cookies.

1. Open the web page where you are experiencing the 520 error.
2. Right-click anywhere on the page and select “Inspect” from the context menu. This will open the developer tools panel.
3. In the developer tools panel, select the “Network” tab.
4. Make sure the “Preserve log” checkbox is checked.
5. Click on the “Clear” button (stop sign icon) to clear any previous network activity.
6. Reload the page to start capturing network activity.
7. Right-click anywhere in the network activity area and select “Save all as HAR with content.”
8. Choose a location on your computer to save the HAR file and click “Save.”

Analyze it to check for any anomalies, such as excessively large cookies or header sizes. If you find large headers and cookies, you can:

• Remove any unnecessary third-party plugins or scripts from your website
• Limit the request overhead i.e. the amount of unnecessary data that is transmitted between the client and the server during each request
• Use a cookie-free domain for your static assets, such as images, CSS, and JavaScript files

WordPress Specific Measures to Addressing Error 520

In addition to the aforementioned steps, here are a couple more that are more specific to WordPress websites.

• Check the WordPress logs to see if there are any errors that are causing Error 520
• Disable all plugins to see if Error 520 goes away. Then re-enable the plugins one by one to determine which one is causing the problem

Last But Not Least – Seek Professional Support

Although there are several steps that you as a website owner can take to troubleshoot Error 520, there may be situations when addressing the error is not entirely within your control.

For instance, if the error is caused by a temporary network outage or a server maintenance issue, you may have to wait for the server to come back online or for the hosting provider to fix the issue.

Also, resolving issues caused by a bug or configuration oversight may require technical expertise that is beyond your scope.

You may need to acquire support from their hosting provider, web developer, or other technical experts who have experience in troubleshooting server-side errors.

Do not hesitate to seek help from technical experts. After all, waiting too long to address them can result in lost traffic and potential revenue for the website.

The post How to Fix Error 520: A Comprehensive Overview appeared first on GreenGeeks.

A website’s inability to load can be caused by a variety of factors. So, in this article, we’ll look at the possible causes of the ERR CONNECTION TIMED OUT error before looking at possible solutions.

The Internet has grown to become one of the world’s largest networks, connecting the entire globe and facilitating data sharing. However, there are a few errors that disrupt the normal operation of the Internet, reducing users’ efficiency while working on the system.

What is the err_connection_timed_out Error?

The connection timed out error is not a dangerous problem or an infected file that can harm your system. This message primarily informs you that the system was unable to establish a connection with the server.

Let us first examine how the Internet works.

When a user enters a keyword in the search bar or the URL of a website, the system sends a request to the server to allow access to the website’s content. The connection is established after the server checks the request and grants permission to the system, and data packets are shared between the system and the server.

An ERR CONNECTION TIMED OUT error usually indicates that there is a problem with your local network connection. That is not always the case, however.

A connection timed out error appears when your website attempts to do more than your server can handle. It’s especially common on shared hosting, where memory is limited.

When you visit a website that doesn’t load, your browser will try for about 30 seconds before disconnecting. It will then return an “ERR CONNECTION TIMED OUT” error, indicating a communication failure.

In Google Chrome, this may appear as “This site cannot be reached.” Domain.com responded too slowly.”

Because of the various web browsers, operating systems, and servers, the error can manifest itself in a variety of ways.

However, the majority of them have the same or similar meanings. “ERR NETWORK CHANGED” and “ERR CONNECTION REFUSED” are two very similar errors that can usually be resolved using the same troubleshooting steps outlined below.

Another common error code that appears under ‘This site cannot be reached’ is DNS PROBE FINISHED NXDOMAIN, which is a DNS error that essentially means the requested domain does not exist.

The following are some examples of how the error might appear in different browsers.

• Mozilla Firefox
  The error message in Mozilla Firefox will be “The connection has timed out.” Domain.com’s server is taking too long to respond.
• Microsoft Edge
  The error message in Microsoft Edge will be “Hmmm… can’t reach this page.” Domain.com responded too slowly.” It does, however, contain the “ERR CONNECTION TIMED OUT” error in Edge.
• Safari
  The error message in Safari will be “Safari Can’t Open the Page.” Safari is unable to open the page domain.com because the server on which it is hosted is not responding.”

What Causes the err_connection_timed_out Error?

There could be several potential causes for the connection timed out error. Some of these factors include:

• Slow Internet Connection: One of the possible causes of the error is a slow Internet connection. If the system does not have a fast and reliable Internet connection, it is possible that the server accepted the request but the system took too long to respond due to the slow Internet.
• Invalid URL: If a user attempts to access data via an invalid URL, the server automatically rejects the request.
• Server Delay or Error: There doesn’t need to be a problem at the user end only; it is also possible that there is a server delay and that a data timeout occurred before the server could release.
• Firewall Settings: It is possible that the Windows Firewall did not allow data packets to enter the system, causing the browser to display this error.

How to fix the err_connection_timed_out Error

If you see this error on your website, where should you begin troubleshooting? Without a lot of context, it can be frustrating and overwhelming to know where to start.

Typically, these are either client-side issues (problems with your network connection or firewall) or server-side issues (problems with the server where the site is hosted) (memory limits, execution times, etc.).

Let’s take a look at some solutions for ERR CONNECTION TIMED OUT. First, we’ll go over how to fix the problem if you’re getting the error while trying to load the site.

1. Examine Your Internet Connection

To resolve the ERR CONNECTION TIMED OUT error, a browser will usually recommend that you first check your internet connection. Due to poor connectivity, it may be difficult for a site to reach a computer promptly.

Google Chrome, Firefox, and Microsoft Edge all advise you to check your network connection. While this may seem obvious, they all point to first checking your connection because it is one of the most common causes of the error.

Here are a few recommendations:

• Restart your router at home or work. This takes only a few minutes and solves far more problems than most people would like to admit. Disconnect the power supply and wait 30 seconds before plugging it back in to completely power cycle it.
• Examine your wifi connection to see if it is bad or slow. This is common in crowded public wifi hotspots like coffee shops or airports.

If the problems persist, try switching to a different network or restarting any relevant devices if you have access to them.

2. Disable Any Proxy Server Settings or VPN Connections.

A proxy server acts as a go-between for your computer and the website you’re visiting. Its function is to protect the user’s IP address, control which sites can be accessed, and cache site data to improve page loading speed.

However, proxy servers may unintentionally block the website you want to visit, resulting in the ERR CONNECTION TIMED OUT error.

Reset your proxy settings to see if these servers are the source of the problem. For Windows 10 users, go to the Control Panel by pressing the Windows logo key. Select Network and Internet Options from the menu.

Open the Connections tab -> LAN settings in the Internet Properties window. Make sure to untick all of the proxy settings.

Users of macOS can go to System Preferences Network and select Advance. Uncheck each box on the Proxies tab and then click OK.

Reload the page to see if the error has been resolved. If it has, and you require the use of a proxy server for day-to-day tasks, consider reconfiguring the settings or switching to a different provider.

Those who use a VPN service may also experience the ERR CONNECTION TIMED OUT error. In that case, we recommend switching VPN protocols because your ISP or firewall may have blocked the one you’re currently using.

Alternatively, try temporarily disabling the application.

3. Turn Off the Firewall and Antivirus Software, Temporarily

Firewalls and antivirus software are designed to keep users and their systems safe. They regularly scan your device and automatically block any suspicious activity.

However, this level of security can occasionally cause connection problems.

This is because firewalls frequently block unnecessary pages or reject content that is completely safe. This has happened numerous times with software such as AVG.

To see if this is the case for you, disable your firewall and antivirus software. Of course, this is only advised if you are certain that the site you intend to visit is secure.

Furthermore, you should only disable this type of software temporarily. To avoid becoming vulnerable to attacks, turn it back on after you’ve finished checking to see if the error has been resolved.

If you keep getting errors because of your firewall or antivirus software, you should think about changing it and whitelisting the site for access.

4. Change DNS Server

The next option is to change your DNS servers. DNS servers are automatically assigned by your ISP by default. However, you could try temporarily switching to a public DNS server, such as Google or Cloudflare.

Some people prefer to use Google’s public DNS (8.8.8.8 and 8.8.4.4) over time because it is often more reliable.

Cloudflare also provides free, secure, and lightning-fast DNS (1.1.1.1 and 1.0.0.1), which we will use in this example. The steps are the same if you want to use Google; simply replace the DNS server addresses with Google’s.

If you’re already using a free DNS server and experiencing problems, removing and reverting it back to your ISP’s DNS servers may help.

Google and Cloudflare aren’t perfect all of the time, and there have been a few instances where switching back has resolved the problem. This is especially true if you’re connecting to a Wi-Fi hotspot in an airport or coffee shop.

Follow these steps if you’re using Windows 10:

• Open the Network and Internet Network and Sharing Center in the Control Panel. On the top left, click Change adapter settings.
• Select Properties by right-clicking on the current connection.
• Select whether your DNS settings should use IPv4 or IPv6 addresses. Then, select Properties.
• Substitute the following IP addresses for the originals:

Use 8.8.8.8 and 8.8.8.4 for IPv4 addresses.

Use 2001:4860:4860::8888 and 2001:4860:4860::8844 for IPv6.

• Restart the browser by clicking OK.

Those running macOS can refer to the following guide: Customize Your Mac with System Settings. On the DNS tab, in the DNS Servers section, click the Plus sign. Enter each IP address one at a time. Select OK.

5. Renew IP Address and Flush DNS

To flush DNS, you must first clear the DNS caches that your computer has saved.

The DNS cache keeps track of the IP addresses of the websites you visit. This saves the computer from having to translate the domain name to the IP address every time you visit the site.

The DNS cache, like browser data, can become out of date. The IP addresses may be outdated, causing problems when attempting to access the site.

Users of Windows 10 can flush DNS by using the Command Prompt. To access the Run command, press the Windows logo and R keys together. Then, in the dialog box, type “cmd” and press OK.

Enter the following into the Command Prompt window:

ipconfig /flushdns

If it is successful, it will display a success message.

Then add the lines below to troubleshoot the network and renew the IP address. Each time you add a new command, make sure to press Enter:

ipconfig /registerdns

ipconfig /release

ipconfig /renew

netsh winsock reset

Restart your computer and open the browser to see if the commands were successful.

For macOS:

Open the Terminal application on macOS and type the following command:

dscacheutil -flushcache

On Macs, there is no success message.

6. Examine Your Hosts File

Every computer has a file called the local host’s file. This is a file containing manual DNS entries that are associated with specific IP addresses.

This is usually only changed when you want to preview your DNS before moving domains to a new host. Alternatively, you may have a local development site running using a tool such as DevKinsta, Vagrant, or Docker.

There are numerous ways this file could have been changed or edited. As a result, it’s always a good idea to double-check that the website you’re trying to access isn’t listed. Simply follow the steps outlined below.

Windows

Additional access to the host’s file is usually required. As a result, the first step is to launch your text editor as an administrator.

Simply go to your start menu, look for your text editor, right-click it, and choose “Run as administrator.” This can be done in any text editor, including Notepad, Notepad++, Atom, and others.

Navigate to File -> Open in the top-left menu and enter the path below into the File name bar.

C:\Windows\System32\drivers\etc\

Then choose the host file.

Below the last line that begins with the “#” sign, the file will display a list of blocked websites. Delete them and save your changes by pressing Ctrl + S.

macOS

macOS clients can open the Terminal, embed this line underneath, and hit Enter:

sudo nano/private/etc/host

Eliminate the rundown of sites that are underneath the “::1” line.

7. Verify Your Domain’s DNS

You should also ensure that your domain’s DNS is correctly pointed to your hosting provider.

If you recently migrated your WordPress website to a new host, it is possible that the DNS was incorrectly cached on your computer. In that case, step 5 above should suffice.

It could also be that it is too soon and you need to wait a few hours for the DNS to fully propagate.

8. Remove Browser Cache

Web browsers cache information on your computer. This includes your browser history, stored login data, and cookies, which are all preserved to load the relevant sites faster the next time you visit them.

But, before you do anything, you may quickly determine if it’s a browser cache problem by opening your browser in incognito mode.

You might also try a different browser.

If you’re still seeing the issue, you should erase your cache. We’ll use Google Chrome in this example.

Begin by accessing the main menu (in the top-right corner of your browser window). From there, choose More Tools: After that, select Clear browser data.

Make sure that all of the stated file categories are chosen on the subsequent page. Chrome will be unable to remove the full cache if they are not. Instead, it will merely delete the most recent items, which will not provide the intended result.

Another way to finish this procedure is to type the following URL into your browser’s address bar:

chrome://settings/clearBrowserData

The subsequent screen should provide you with the same options as described previously.

WordPress-Specific Fixes for err_connection_timed_out

Sometimes, how your WordPress site is set up can cause a connection time out error. Let’s take a look at what you can check for in WordPress to clear the problem.

The remaining troubleshooting methods will concern the settings of your WordPress site or server.

Examine the Maximum Execution Time

Your site’s maximum execution time. The default time on most servers is 30 seconds. This is the maximum amount of time a PHP script may execute (after which it times out).

On shared hosts, this is usually set to a low value or left at the default.

Because the php.ini file is placed on your server, you cannot simply alter it from WordPress. To change this, we recommend contacting your hosting provider to see if they can assist.

Change the maximum execution time in the php.ini file

Some PHP programs may consume more memory than is permitted, causing the site to take too long to reply to the browser.

The memory limit, like the maximum execution duration, can be increased. However, the quantity should be within the maximum available RAM allowed to your plan by your hosting provider.

If you don’t know the maximum available RAM for your hosting plan, contact the company’s support team or read the documentation.

Open the .htaccess file in File Manager to raise the limit. Then insert the line below, utilizing the maximum available RAM as follows:

memory limit php value 128M

The code should be placed at the bottom. It should be above “END WORDPRESS” if you use WordPress. Finally, click the Save & Close button.

Change the maximum execution time in the .htacess file

Another option is to manually alter the timeout value on the website’s .htaccess file. Locate the .htaccess file in the public html directory. Edit it and paste the following code before the “END WORDPRESS” line:

php value max execution time 120

Finally, click the Save & Close button. Access the website to check if the error has been resolved.

Disable Your Plugins Temporarily

A plugin, like with most WordPress issues, might undoubtedly be the source of the issue. To see if that’s the case, you’ll need to disable all of your site’s plugins.

If you receive the “ERR CONNECTION TIMED OUT” error, this indicates that you do not have access to your WordPress admin area. This implies you’ll have to SFTP into your website. We recommend that you use FileZilla.

Connect to your website using your SFTP client and browse to the WordPress root folder. If you can’t locate it, it’s commonly named public html, html, public, www, or the name of your site.

Navigate to the wp-content directory by opening that folder. Inside, you’ll find a plugins folder, which has distinct subdirectories for each plugin installed on your site (both active and inactive).

What you’re going to do now is right-click on the plugins folder and rename it. To make it easier to identify later, we propose plugins.old or plugins.deactivated.

WordPress will now be unable to locate any of your plugins. When this occurs, the plugins are immediately disabled. Try entering your WordPress dashboard now.

If the timeout problem has disappeared, you can presume that one of your plugins was to blame. All that remains is to determine which one was causing the problem.

Return to the wp-content directory and appropriately rename your original plugins folder. Then, one by one, disable each of your plugins until you locate the problem.

NOTE: GreenGeeks customers can disable all of the plugins from the Manage WordPress dashboard of their accounts. This is perhaps easier and quicker for those who don’t know much about using FTP software.

Activate the Default Theme for a Limited Time

If a theme has bloated code or compatibility difficulties with a website, it may produce ERR CONNECTION TIMED OUT. WordPress suggests returning to the default theme to see whether the theme is the problem.

If the admin interface is unavailable, you can do this operation manually. This means that you must log in to phpMyAdmin to access your WordPress database.

Click on wp options in the phpMyAdmin section. Then, using the names template and stylesheet, identify two queries. They might be found on the second or third page.

When you’ve located them, double-click on the option value column and change the current theme’s name with a default one. It may be twenty-one, twenty-two, or twenty twenty-three.

You may also have a “Default” WRC Theme that comes with the installation of WordPress.

Check to see whether the admin panel and website are now accessible. If they are, consider reinstalling or changing the theme.

Increase the Memory Limit

The WP MEMORY LIMIT option allows you to determine the maximum amount of memory that PHP can utilize. If you’re using shared hosting, it’s most likely set to a low amount, such as 64M.

You can increase the memory limit by adding the following to your wp-config.php file. This must be placed above the wp-settings.php inclusion.

define(‘WP MEMORY LIMIT’, ‘256M’);

Do you know what your current PHP memory limit is? If you have access to your WordPress dashboard and are using WordPress 5.2 or higher, the PHP memory limit may be found under the “Site Health” tool.

Conclusion

Connection and timeout issues are never enjoyable to troubleshoot, but perhaps you now have a bit more information under your belt to help you address them fast.

It’s critical to understand that the “ERR CONNECTION TIMED OUT” error might be caused by a client-side issue, such as a faulty network connection, or by a problem with the server where your WordPress site is hosted.

Do you have any other suggestions for resolving this mistake or problem? Let us know in the comments section below.

The post How to Fix the “err_connection_timed_out” Error appeared first on GreenGeeks.

Today, let’s see if we can solve this problem.

Fixing the DNS PROBE FINISHED NXDOMAIN Error

To understand better, here is a quick primer on how DNS works.

Your computer or device usually has one or more DNS servers configured in its network (or internet) settings, which your browser uses to resolve domain names.

When you type in a domain (something like XYZ.com) or click on a link, your browser needs to know the IP address of the website’s server to establish a connection and load the website’s content.

For this, it sends a request to a DNS server, which is responsible for translating the website’s domain name into its corresponding IP address. And when that is obstructed, you’d get the seemingly glaring error – DNS PROBE FINISHED NXDOMAIN.

Different browsers have different ways of exhibiting NXDOMAIN errors. In fact, at the time of writing this piece, Chrome is the only major web browser that displays the error verbatim.

As a Website Owner, Should You Be Worried About the NXDOMAIN Error Message?

Receiving an NXDOMAIN error can be concerning for a website owner, blogger, marketing agency, or business hosting their website on WordPress.

It’s natural to wonder whether other users are also unable to access your website and whether the error is a sign of a larger problem.

First, panic is unnecessary when encountering an NXDOMAIN error, as it is relatively common. And you don’t necessarily need to be a website expert to resolve an NXDOMAIN error.

The error might even fix itself when you restart your PC or wait it out for a while.

However, it can be helpful to have a basic understanding of DNS and website hosting to troubleshoot and resolve the issue effectively, should the need arise.

Here is how to fix DNS PROBE FINISHED NXDOMAIN error.

First Steps in Scrutinizing an NXDOMAIN Error

You need to figure out if it is just happening for you (or your device), or are all visitors affected.

Here is what you need to check.

1. Check the Domain Name

Check if you’ve typed in the domain name correctly. A simple mistake in the spelling of a domain can lead to an NXDOMAIN error.

It could be as simple as adding an extra character or misspelling something within the address bar.

2. Try a Different Device or Connection

Try accessing the website from a different device, browser, or network. Perhaps you can switch from wifi to cellular for checking your connection.

It’s likely that the error is specific to your current device or network, and other users may be able to access the website without issue.

To that end, check if you can access other websites and try restarting your router or modem. Network connectivity can also cause NXDOMAIN errors.

3. Check Security Settings

Check if your firewall, VPN, or antivirus software may block your website’s accessibility. Sometimes, security software can accidentally flag legitimate websites as being malicious.

Do this by disabling them temporarily and trying to reach the website.

4. Wait Out the Problem

Wait and try again later. NXDOMAIN errors can be temporary and may resolve on their own over time. Sometimes, if you (or your ISP) have recently changed DNS settings, it can take some time for the changes to propagate across all DNS servers.

To that end, clear your browser cache, which can force your browser to retrieve fresh DNS data instead of the cached one.

5. Monitor Website Performance

While you wait, monitor your website: Keep an eye on your website’s performance and connectivity to ensure that you are not experiencing any other issues affecting your visitors’ experience.

Didn’t Work? Let’s Do Some More!

Again, there’s no need to panic should the above steps be futile. There are many ways to go about addressing the NXDOMAIN error.

Before you look at a few prominent ones, it’s essential to understand what a Command Prompt is.

Skip this bit if you already know.

The Relevance of Command Prompt

The Command Prompt is a command-line interface (CLI) program included in most operating systems (OS). It’s a powerful tool that can be used for various purposes, such as troubleshooting and system administration.

To access the Command Prompt in Windows, press the Windows key + R to open the Run dialog box, type “cmd” in the box, and hit Enter. In some instances, you may need to permit it to “Run as Administrator.”

The Mac OS also has a command-line interface called Terminal. Use the Spotlight search to find and launch the Terminal. Press the Command + Space keys to bring up Spotlight, then type “Terminal” and press Enter.

Let’s look at how we can use the Command prompt, among other ways, to resolve the DNS PROBE FINISHED NXDOMAIN error.

Clear DNS Cache

When you visit a website, your computer stores its IP address in a DNS cache so that it can be quickly accessed in the future without needing to perform a new DNS lookup. However, sometimes the cache can become outdated or corrupted, leading to the DNS_PROBE_FINISHED_NXDOMAIN error.

To clear the DNS Cache on Windows, open the command prompt, type “ipconfig /flushdns,” and hit Enter. Open your browser, and try reaccessing the website.

In MacOS, type in the following command in the terminal window and press Enter: sudo killall -HUP mDNSResponder. Enter the administrator password when prompted.

A few seconds after the command is executed and the DNS cache is cleared, you should see a message indicating that the mDNSResponder process has been restarted.

To that end, Google Chrome has a dedicated DNS cache. To clear the same, type in “chrome://net-internals/#dns” at the browser search bar, hit enter, and click “clear cache host.”

Restart DNS Client Service

As a Windows Service that runs in the background, DNS Client Service is responsible for resolving domain names to IP addresses. Without it, users would need to manually enter the IP addresses associated with every website they visit.

This is impractical and time-consuming.

Restarting the DNS Client Service can help address the NXDOMAIN error.

Type “net stop dnscache” in Command in the Windows command prompt and press the Enter key. This will stop the DNS Client Service. Wait for a few seconds to let the command take effect. Then, type “net start dnscache” to start the DNS client service again.

MacOS does not have a DNS Client Service like Windows.

Change DNS Server

Your ISP usually supplies DNS Server addresses, which you can freely change while facing issues. The most prominent ones to adjust to are Google’s (8.8.8.8) and Cloudflare’s (1.1.1.1) public DNS. Often, switching to these servers resolves the NXDOMAIN error.

Here is an outline of how you can go about it:

• Start menu
• Type and select “Control Panel” in the search bar
• Network and Internet > Network and Sharing Center
• Change the adapter setting (on the left-hand side)
• Right-click on the network adapter you want to configure (which is usually the one representing your internet connection)
• Select “Properties”
• Internet Protocol Version 4 (TCP/IPv4)
• Click Properties

Use the following DNS server addresses:

On Windows, enter the new DNS server addresses (Google and Cloudflare from above) in the “Preferred DNS server” and “Alternate DNS server” fields. You can enter multiple DNS servers separated by commas.

Click “OK” to save the changes and exit the Properties window.

On MacOS, Click on Apple menu > System Preference > Network > Select the network connection you want to configure from the list on the left-hand > Advanced > DNS

Click on the Apple menu in the top left corner of the screen and select “System Preferences.” Click on the “+” button at the bottom left of the DNS Servers list to add a new DNS server (click the “-” button to remove the existing DNS server).

Type in the IP address of Google and Cloudflare public DNS. Then click “Ok” to save changes.

Release and Renew Your IP Configuration

Often regarded as a quick fix for networking issues, releasing and renewing IP addresses can resolve NXDOMAIN errors.

In Windows, open the command prompt, type “ipconfig /release,” and press Enter to release the IP configuration. Then type “ipconfig /renew,” and press Enter to renew the IP address.

Try accessing the domain name again and see if the NXDOMAIN error is resolved.

Additionally, flushing the DNS will clear any old or stale entries (i.e., any record in the DNS database that maps a domain name to an IP address) that may be causing NXDOMAIN errors.

Type in: ipconfig/flushdns

In MacOS, Type the following command into the Terminal window and press Enter: sudo ipconfig set en0 DHCP. If you are using Wi-Fi, replace “en0” with “en1” in the command.

Enter the administrator password if prompted.

Reset Chrome Flags

Enabling certain Chrome Flags can lead to DNS PROBE FINISHED NXDOMAIN error.

Chrome Flags are experimental features in the Google Chrome browser. They are not enabled by default. So if you weren’t aware of Chrome Flags until now, don’t bother resetting.

If you’ve played with Chrome flags, you’d probably know how to reset it.

In the address bar of your Google Chrome browser (or its derivatives like Brave), type chrome://flags and locate and click “reset all to default” at the top of the page.

Other Browser Tweaks

Disabling browser add-ons and reinstalling the browser can sometimes help alleviate NXDOMAIN.

Add-ons or extensions can interfere with the browser’s ability to connect to the internet, which can cause DNS errors. Also, an outdated browser may not be compatible with the latest DNS protocols.

Fixing NXDOMAIN Error on Android and iOS

To rectify the DNS PROBE FINISHED NXDOMAIN error on your Android or iOS, you can trial-and-error around clearing the mobile browser cache, disabling extensions, using a different browser, resetting DNS, or using a different DNS server.

If none of these solutions resolve the NXDOMAIN error, it may be a more complex issue that requires further investigation or assistance from a technical expert.

Lastly, Seek Technical Assistance

If none of the above-mentioned techniques work and your browser still displays the NXDOMAIN error, consider seeing technical help from the experts or your hosting provider.

Encountering errors like DNS PROBE FINISHED NXDOMAIN can frustrate and disrupt your online experience. However, by taking the time to troubleshoot and fix such issues, you can gain valuable knowledge and experience, which is critical to creating a successful online presence.

The post Troubleshooting the DNS PROBE FINISHED NXDOMAIN Error appeared first on GreenGeeks.

However, it is comforting to know that the NET::ERR_CERT_DATE_INVALID error is a pretty common problem with a variety of potential explanations.

Naturally, you would want to try a range of solutions to get back on track, and all of these issues can be resolved relatively easily.

Today, we’ll go through what NET::ERR_CERT_DATE_INVALID is and the SSL certificate. We’ll also discuss several methods for resolving the problem.

Let’s get this party started!

What is NET::ERR CERT DATE INVALID?

The system error NET::ERR CERT DATE INVALID is commonly known as “Your Connection Is Not Private.” People usually come across it while using Google Chrome to access specific websites, even if they are legitimate and trustworthy.

When people receive this message, it signifies that the Internet connection or the device itself is blocking Google Chrome from loading the website because it is insecure, and accessing it puts one’s privacy at risk.

SSL and NET::ERR CERT DATE INVALID

Having an SSL certificate installed on your website should put you and anyone else at ease when using your website. This is because of what SSL is and how it acts

SSL stands for Secure Sockets Layer, and it’s the industry standard for keeping an internet connection secure. Its purpose is to secure any sensitive data passed between two systems, preventing thieves from reading and altering any data provided, including potentially personal information.

These two systems can be a server and a client (a shopping website and a browser) or a server to server (for instance, a shopping website and a browser).

For example, an application with personally identifiable information or with payroll information is at risk.

SSL certificates must be installed on a company’s or organization’s website in order to safeguard online transactions and keep customer information private and secure.

The website you’re visiting is safeguarded by SSL if you see a padlock icon next to the URL in the address bar.

How does SSL work?

SSL accomplishes its objectives by ensuring that any data sent between users and sites, or between two systems, is unreadable. It scrambles data in transit using encryption methods, preventing hackers from accessing it as it travels over the network.

Credit card numbers and other financial information, as well as names and addresses, are examples of potentially sensitive information being sent, and they need to be protected.

The procedure it undertakes is as follows:

• A browser or server tries to connect to an SSL-secured website (i.e., a web server).
• The web server is asked to identify itself by the browser or server.
• In response, the web server delivers a copy of its SSL certificate to the browser or server.
• The SSL certificate is checked by the browser or server to see if it is to be trusted. If it is, the web server receives a notification.
• After that, the web server sends a digitally signed acknowledgment, which initiates an SSL-secured session.
• Then, encrypted data is transferred between the browser or server and the web server.

The term “SSL handshake” is used to describe this process. While it may appear to be a lengthy procedure, it is completed in milliseconds.

The term HTTPS (which stands for Hypertext Transfer Protocol Secure) appears in the URL when a website is secured by an SSL certificate. Only the letters HTTP – i.e., without the S for Secure – will appear if you don’t have an SSL certificate.

Thus, with this form of sophisticated and air-tight security, it is surprising that one can have SSL cert installed, and still experience NET::ERR CERT DATE INVALID error message.

In the vast majority of circumstances, the error will not prohibit you from viewing the site. You can choose to ignore it and proceed to go to the page you’re looking for, but we don’t encourage it.

Because while the NET::ERR CERT DATE INVALID issue is common and easy to rectify, it does occasionally signify a genuine hazard.

Variations of the NET::ERR CERT DATE INVALID Message

While the NET::ERR CERT DATE INVALID error message is most commonly seen in Chrome, other browsers have their own version of the error. The particular message you see is also influenced by your operating system.

On Chrome, Firefox, Microsoft Edge, and Safari, the messages differ from one another, as well as the solutions.

On Firefox: the bright yellow outline is a dead giveaway.

On Safari: the error mostly appears as a pop-up.

How to Fix the NET::ERR CERT DATE INVALID Error Message

Now that we’ve taken a look at why this error could occur, how it appears differently on various browsers, and SSL certificates, let us now talk about how to fix it.

The steps below will teach you how to fix the NET::ERR CERT DATE INVALID system problem and get rid of the notification “Your connection is not private”.

You should attempt all of the approaches listed as there is no assurance that just one will fix it right away.

1. Reload the Site

Let’s start with the most basic solution, simply reloading the page. You could alternatively close and relaunch your browser before returning.

Things don’t always operate the way they should, and it’s preferable to try a quick repair than waste time troubleshooting. Unusual as it may sound, it’s possible that you just caught the website owner in the middle of renewing their SSL certificate.

2. Check Your Internet Connection

This is the next logical step to take if the error persists after you’ve reloaded the page. If you’re using public Wi-Fi, there’s a good chance that your connection isn’t secure.

To be safe, you might wish to stop browsing and disconnect from the public Wi-Fi. Attempt to re-access the internet using a mobile hotspot.

If you don’t encounter the same error message, then you know that the issue was from the public connection. If you do get the same error, try using a Virtual Private Network (VPN).

On the other hand, if you were already using a VPN when you first noticed the problem, you should try disabling it, since that could be the source of the problem.

3. Restart Your Computer

After doing the above with no resolution, restart your computer. Many times, restarting your computer solves a lot of issues.

4. Check Date and Time Settings

Incorrect date and time parameters error can occur if your time is wrongly set. Your browser checks that a site’s SSL certificate hasn’t expired using the clock on your machine.

Even if your computer is set to automatically sync, it can still be thrown out of sync. If you’ve recently traveled between time zones, for example, your laptop may not yet be up to date.

So, double-check that your device’s date and time are correct. Then try navigating again after reopening the browser.

5. Determine if Your SSL Certificate Has Expired or is Faulty

If you notice this mistake on your own website, it may be time to have your SSL certificate reissued. SSL certificates do expire. You may check this immediately on Chrome.

How to Check Your SSL Certificate

Begin by clicking the three dots in the browser window’s top-right corner. Then go to More Tools > Developer Tools.

Go to the Security page and check to see if the certificate is still valid. To access further information, including the certificate’s expiration date, click the View Certificate button.

You can also check the validity of your certificate with a tool like Website Planet SSL Checker, Qualys’ SSL Server Test, SSL certificate expiration alerts, certificate expiry monitor, SSL certificate expiration checker, TrackSSL, and more

For example, using Qualys’ SSL Server Test looks like this:

Simply enter your domain name in the space provided and press the Submit button.

The test may take several minutes to complete. A detailed analysis of your SSL configuration, as well as a letter grade for each item, will be included in your results. Ensure that you pay special attention to the SSL certificate’s expiration date.

These methods can also be used for the verification of the authenticity of an SSL certificate on someone else’s website. You won’t be able to do much more than try to contact the website’s owner and inform them that their accreditation has expired.

If your own certificate has expired, you can resolve the NET::ERR CERT DATE INVALID problem by renewing it. Your host may be able to help you with this, or you may be able to do it yourself using your control panel.

Whichever method you use, ensure that you sort out your SSL certificate’s renewal before it becomes a huge problem for you.

6. Reinstall Chrome or Other Browsers

Sometimes, settings or functions of browsers can become corrupt for a number of reasons. In some cases, it’s better to start over from scratch.

Since browsers don’t take long to reinstall, it’s an easy method to see if it fixes the problem.

7. Update Your Operating System

Because earlier versions of operating systems may no longer be supported once, they become obsolete. You should always have the most recent version installed.

Furthermore, elements of SSL certificates are no longer compatible with earlier operating systems.

If your operating system is out of date, you’ll start seeing errors like NET::ERR CERT DATE INVALID more frequently as time goes on.

The same can be said about out-of-date browsers. If you haven’t updated your browser in a while, now is a good time to do so. Even if the browser is current, uninstalling and reinstalling it might occasionally help.

8. Disable Doubtful Third-Party Browser Extensions

Third-party extensions are known to cause issues from time to time, and this can be dependent on the number of third-party extensions you have installed.

The solution to this requires you to test each extension individually. You do this by uninstalling the extension, then testing the browser and checking if the error persists.

9. Disable Windows Firewall Temporarily

It’s possible that your antivirus software has a setting that causes the NET::ERR CERT DATE INVALID issue. To see if this is the case, turn off your antivirus software and try to access the website. When you do this, make sure to force a refresh.

If you find that your antivirus program is the source of the problem, you should first attempt updating to the most recent version. If the problem persists after updating, you can contact the software’s support team.

To disable the Windows Firewall:

1. Click on the Windows key and type Windows Firewall.
2. Click on the first option and open Turn Windows Firewall off or on section.
3. Select Turn off Windows Firewall and check if the issue still occurs.

10. Clear Browser Cache and Cookies

There are a couple of ways to figure out if deleting your cache will assist. First, use incognito mode to access the website. If it doesn’t work, try accessing the site using a different browser.

If nothing of these options work, deleting your browser cache is a good bet for resolving the issue.

The procedure varies depending on which browser you’re using.

You can try reopening your browser and reloading the website after clearing your cache and cookies.

Clearing browser cache on chrome:

1. Open Chrome and click on the Menu icon.
2. Navigate to History and select Clear browsing data.
3. Ensure that the Browsing history and cache are cleaned.
4. Wait for the cleanup to finish before reopening the browser.

11. Clear Your SSL Cache

If clearing the cache in your browser didn’t work, try emptying the SSL cache. To save time when you reconnect later, the SSL cache keeps credentials for websites you’ve visited.

In the meanwhile, if an SSL certificate is changed, your browser’s SSL cache may prevent it from recognizing the change.

Navigate to the Control Panel and select Network and Internet to clear the SSL status in Chrome on Windows. The button to Clear SSL status can be found under the Content tab.

Reopen your browser and go to the webpage once more. If the NET::ERR CERT DATE INVALID problem persists, there are more solutions for you to try.

12. Replace Current DNS Servers with Google DNS Servers

Depending on your present arrangement, you might want to consider switching your Domain Name System (DNS) server to or from Google’s Public DNS. Before making any changes to your DNS settings, make a note of what the numbers are now in case you need to go back and alter them.

Start by going to the Control Panel in Windows and changing your DNS server there. Then, select Network and Internet > Network and Sharing Center.

The adapter settings need to be changed. Select Properties from the context menu when you right-click on your connection.

After that, select and then press the button. Select The following DNS server addresses should be used:

Enter 8.8.8.8 and 8.8.4.4 in the boxes to use Google’s Public DNS. Cloudflare’s DNS addresses are 1.1.1.1 and 1.0.0.1, respectively.

Close the window by clicking OK. For the changes to take effect, you’ll need to restart your browser.

The procedure is identical for Mac users, with a few exceptions.

Having discussed these very many likely fixes, it is important to state a disclaimer. While some fixes such as reloading the site and reinstalling the browser are not risky, others such as lowering your firewall protection level or changing your network settings should be done with care.

If you’re confident in the website and its owner, however, please go ahead. But be sure you’re not jeopardizing your safety.

NET::ERR_CERT_DATE_INVALID and WordPress

“Your connection is not private; attackers might be trying to steal information…”

This error basically occurs when an SSL certificate is not installed on your website. In this section, we’ll discuss how to fix this, and install an SSL certificate on your website

For this, you have to first go to your dashboard or your cPanel. It all depends on the hosting that you’re using. Whenever you purchase from a new hosting provider, you get an email. In that message, you have your cPanel link, username, and password.

Thus, you have to start with that email. Not to worry, as the message will have all the details about how to log into your web hosting account and access cPanel and other features.

Once in your hosting account, it’s easy to add Let’s Encrypt SSL to your website. That is as long as your web host provides such a feature.

One of the ways to fix the “not secure” warning on your WordPress website if your SSL certificate has been installed, is by installing an “SSL Content Fixer” plugin.

You do this by navigating to your dashboard in WordPress, going to Plugins, and clicking, “Add New.”

Search the plugins. Then, add and activate the SSL Content Fixer.

Navigate to the plugin and edit its settings. Select the level of fixing and start from the simple level first. It has the least effect on the site’s performance.

Most times, the capture does it. Save changes and reload the site.

Summary

The ‘NET::ERR_CERT_DATE_INVALID’ error has many potential causes. It can be very frustrating trying to figure it out, but we’ve provided an array of options, some with step-by-step guides on how you can possibly solve them.

Good luck!

The post 12 Ways to Fix the NET::ERR_CERT_DATE_INVALID Error appeared first on GreenGeeks.

No one likes seeing an error message pop up, especially when working on a difficult project. Fortunately, it’s not entirely difficult to address depending on the browser you’re using. Here is a detailed guide to help you move past the error.

What is the Err_Connection_Refused Error?

Before diving into further details, it’s essential to brush up on some basics of what causes this problem. It’s something that can affect virtually any Internet browser.

The error represents an issue retrieving whatever page you tried accessing with your browser on the Internet. Most browsers show a problem with the connection by showing a message that says “Check your internet connection” or “Check the firewall proxy.”

The error is especially common with non-WordPress sites and is a message you see primarily on Google Chrome. Luckily, it’s simple to identify and solve the problem.

It’s essential to understand the error in further detail and how it may appear in different browsers for users.

What are Some Common Internet Errors?

The ERR_CONNECTION_REFUSED is not the only internet error that you will come across. You will also find other errors like:

• 502 Bad Gateway
• 401 Error
• Error 400

You can find solutions for your connectivity issues by understanding all these errors. But today, let’s focus on the ERR_CONNECTION_REFUSED error across different internet browsers.

How Different Browsers show ERR_CONNECTION_REFUSED

Here are some of the most common ways users may find the error displayed in various browsers.

Google Chrome

Chrome is the most popular internet browser available with over three billion people using it across different devices. Users will see a message popup on their screens if the connection refused error occurs:

“This site can’t be reached” or “This webpage is not available“

The error means that the user’s attempt to connect to the internet failed. The same error may appear in other browsers in a different format. 

Another standard error that chrome users may encounter in the DNS_PROBE_FINISHED_NXDOMAIN is a DNS error. 

A domain name error means that the requested DNS domain does not exist. Therefore, the internet cannot connect to the website.

Mozilla Firefox

Mozilla Firefox shows an “Unable to Connect Error” if there’s a connectivity refusal. In other cases, the browser may also display a “Firefox can’t establish a connection to the server at domain.com.” error.

The browser can also suggest a few reasons for seeing these errors. But, users may not always find the solutions practical.

Microsoft Edge

Microsoft Edge is a lesser popular internet browser, but it is still a favorite for some users. It is primarily used on Windows-based computers, and users may see the “Hmmm… can’t reach this page Error” displayed.

What Causes the ERR_CONNECTION_REFUSED Errors?

The ERR_CONNECTION_REFUSED error is related to the browser’s inability to connect to the web server. The error message 102 only appears for Google Chrome users; others may see it differently.

The specific error occurs on the client-side in most cases for different reasons, including: 

• incorrect firewall
• system settings
• browser settings

But you can see the same error if the website is unavailable on the domain side. The error may show up regardless of the operating system you use. Even Android users may encounter the same error if they use Google Chrome.

ERR_CONNECTION_REFUSED: How to Solve It?

You understand the error appears primarily because of client-side misconfiguration. So, there’re many methods you can utilize to target these problems.

But the problem may also arise because of technical issues on the user’s side.

Unfortunately, the problem is that the error can arise because of various reasons. It can make it difficult for users to line out the exact cause. The browser message shows the error but does not show the actual reason.

Therefore, users need to try various solutions until they can resolve the error, and different solutions exist for different issues. Nevertheless, you can try the following methods.

Here’s a pick of the top issues for the error:

• Check Your Proxy Settings
• Change Your DNS Address.
• Check If the Page Itself Has Gone Down.
• Clear Browser’s Cache.
• Flush DNS Cache.
• Restart Router.
• Temporarily Disable Antivirus or Firewall Software.

Check the Website Status

Not being able to connect to the web server is the most common problem leading to the error. Perhaps the server itself is having issues and preventing connections from visitors.

There’s a chance that the website may be offline, and the browser may show the ERR_CONNECTION_REFUSED error. But in this case, the actual error code should be the HTTP 503 message.

There are primarily two different solutions you can try to check the website server:

Access other websites and see if they work. If you can access other websites, then the one giving the error may be at fault. The other option is checking online detection tools like “Down for Everyone or Just Me?“, which allows users to instantly check the website’s status.

While using tools can be helpful in certain situations, those situations happen to be very specific. Therefore, it’s best to follow the classic approach of checking another website on your internet browser.

Restart the Router

A more straightforward solution for the error is to check the internet device you are using. Sometimes routers and network hubs can be at fault, which could impact how your devices access online resources.

Restarting the router usually takes a few minutes. For this reason, it’s quicker to unplug the power and wait for 30 seconds.

It allows the router to reconnect quicker so that users can check the website. It’s essential to wait for around 30 seconds for the router to start functioning again. 

Access the target website, and it might resolve the ERR_CONNECTION_REFUSED error.

Clear Browsing Cache

All internet browsers (especially Google Chrome) save large chunks of information known as browsing cache. The cache includes records of visited websites, cookies, log-in data, etc., which can help you visit certain websites faster.

But, some users may experience issues with website access in case of outdated or faulty caches.

It contradicts the site’s existing cache and the user’s record. Fortunately, it takes just a few seconds to resolve this issue, as you need to refresh Google Chrome’s cache.

Users unfamiliar with the clearing method can follow these steps:

1. Access the browser’s menu by clicking the button located on the top right of the screen.
2. Find “More Tools” and click on “Delete Browsing Data.”
3. Google Chrome users can add the Chrome: //settings/clearBrowserData on the chrome URL and access the cache to clear it.

These methods allow users to access and remove the cache information. Users should ensure adding all the categories and cache types. Next, they should find the “All Time” option under “Period” to clear all cache records scored on the platform.

Selecting these options is essential because Chrome will only delete cache files in the past few hours or days. Thus, it can cause the same error because of cache problems.

Note: Sites may take longer to load after clearing the cache, but it should resolve the ERR_CONNECTION_REFUSED error.

Check Proxy Settings

Internet surfing safety is a significant concern for most users online. Companies, firms, and individual users are all worried about data breaches. Most internet users follow a wide range of security measures to protect their systems from such problems.

However, users may still use personal internet protection methods such as internet proxies and VPS web hosting. The proxies are like a bridge between the internet and the site accessed: 

• The proxies change 
• Filter cache data
• Website connectivity

Moreover, proxies are a great option because they protect the user’s IP address from the website. Unfortunately, these proxy servers can cause ERR_CONNECTION_REFUSED errors to appear.

For example, a server may prevent a proxy IP from accessing the website, displaying the same error.

Additionally, these proxies have a caching function, storing relevant website data and information. Though, users may experience connectivity issues because of proxies for different reasons.

For example, it can be because the proxy is offline or configuration issues.

Users receiving ERR_CONNECTION_REFUSED errors should check their proxy server settings and ensure it’s functioning properly. Even Google Chrome has proxy settings that users should check by typing:

“Chrome: //settings/”

Users should click on “Advanced” and open the full Google Chrome settings menu. Click on “Open Proxy Settings” and check the operating system’s proxy menu.

Windows users can check the “LAN settings” and change the proxy settings as well.

Turn the Firewall and Antivirus off Temporarily

Firewalls are a protective measure designed to protect internet users against malware. These firewalls also filter out websites and block suspicious files or access to certain web pages.

Users also get their systems scanned at regular intervals.

In some cases, the firewall will automatically block pages it thinks are unsafe. But there’s a chance that the firewalls may block secure pages at times.

The easiest way to resolve the ERR_CONNECTION_REFUSED message in this instance is to deactivate the firewall.

You can also switch to other security tools to stop the firewall from blocking websites unnecessarily.

Clear the DNS or Perform a DNS Flush

Most people think caches are limited to internet browsers. But the operating systems can also collect and store relevant information for future reference.

The operating system stores different entries, including information required for name resolution for the domain addresses. Caching the information makes website access easier by eliminating the need to access the DNS server each time.

Operating systems answering connection queries may cause connectivity errors. For example, if the current cache entries do not match the website, the same error may persist.

Fortunately, it’s simple to clear out these errors from the system by clearing the DNS server. Some even call it a DNS Flush.

Windows users can use the following command to clear their DNS records:

“ipconfig /flushdns”

Changing the DNS Server

Website connectivity relies largely on name resolution. Resolving DNS names can cause issues with computer connectivity. The cache in internet browsers and the operating system is not the only cause for the ERR_CONNECTION_REFUSED, but can also be because of the DNS itself.

For example, you may face connectivity issues if the DNS server is overloaded or is temporarily offline. Most users can collect the DNS server from their internet provider directly, or you can enter it manually.

For example, many internet users prefer using Google’s DNS servers (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1 and 1.0.0.1). It all depends on how users wish to resolve their problems.

Nonetheless, sometimes changing the DNS server your device uses can clear the connection problem.

Bottom Line

ERR_CONNECTION_REFUSED errors are a common problem for internet users around the world. The problem can show up on any internet browser because of many problems.

Some of the easiest ways to resolve the issue include:

• Changing the DNS Server
• DNS flush
• Turning off Antivirus and Firewall
• Checking proxy settings
• Clearing browsing cache, etc

Following the fixes we have mentioned in this comprehensive guide can resolve connection problems. Users still facing complications should try contacting their internet service providers. 

They can provide users with more information and details on the website in question.

The post What is the Err_Connection_Refused Error and How to Fix It appeared first on GreenGeeks.

And the good news is that the code behind them is not complicated. In fact, you can just copy and paste them, but I’m sure you will commit them to memory after a few uses.

Let’s go over how you can easily manage your Nginx server with the Start, Stop, and Restart commands.

What Is Nginx?

Nginx (pronounced EngineX) is an open-source HTTP and reverse proxy server that excels at managing high-traffic websites. And that’s exactly why it is widely used by some of the largest websites on the internet.

It’s important to note that while it can be used as a standalone web server, it is more often used as a reverse proxy for Apache and other web servers.

This is because Nginx is often used as a load balancer, which just means it’s responsible for distributing the load (traffic) to less burdened servers. Thus, it ultimately helps speed up websites impacted by high traffic.

So, how does it manage to do all this? Well, it employs a Master-Worker event approach. This means that the master manages the worker processes, while the workers do the actual processing.

In other words, Nginx doesn’t really use many resources and instead dictates what should use them.

Why Are the Start, Stop, And Restart Commands So Important For Nginx?

Simply put, they are the most common commands you will need to input into the webserver. If Nginx is not on, your website will appear offline to visitors, thus, they directly affect if your website is visible.

So, what does each one do?

Start: The Start command begins the Nginx service.

Stop: The Stop Command terminates the Nginx service.

Restart: The Restart command first stops the Nginx service and then starts it up again.

As you can see, the commands are very true to their names. The most important of these three commands is Restart. You will need to restart Nginx every time you make a change to its configurations.

The only problem you may encounter when restarting Nginx is if a syntax error was made when making a change elsewhere. This can result in the service not starting again.

Thus, like everything in web design, triple-check any code you enter.

The Start and Stop commands can also be used since the Restart command simply performs both of these functions.

Are There Any Other Useful Commands?

Absolutely! There are a variety of commands for Nginx that can help you manage it. Three other commands you should be aware of when trying to manage Nginx are the Status, Error Log, and Reload Commands.

Status: The Status command shows the current server status.

Error Log: The Error Log command will allow you to see the error log. This will highlight any errors in the configuration files. It is particularly useful when Nginx will not restart as it identifies the lines with the errors.

Reload: The Reload command restarts Nginx by shutting down the child processes, loading any new configuration changes, and then starting new child processes.

The Status command is really useful for tracking down errors within your server. More specifically, it will notify you if there is an error within the configuration file. It will also specifically list the line the error is occurring on, which is greatly beneficial for troubleshooting.

The Reload command is a safer way to restart Nginx because it keeps the Nginx server running while reloading the updated configuration file. If it catches a syntax error in any file, then reload is aborted, which keeps your server running on the old configuration file.

As such, it is safer to reload than it is to restart Nginx.

You’ll generally want to use the Status command on a regular basis or whenever a major change is made to the configuration file. Whereas the Error Log should only be used as a troubleshooting tool when Nginx will not start.

How to Start, Stop, and Restart Nginx

I will now cover the commands you will need to use to start, stop, and restart Nginx. However, be aware that the commands change depending on if you use Systemctl or SysVinit.

You will need to check your server settings to find out which is correct.

I will share the commands for both.

Using Systemctl

To Start Nginx, enter the following command:

sudo systemctl start nginx

To Stop Nginx, enter the following command:

sudo systemctl stop nginx

Finally, to Restart Nginx, enter the following command:

sudo systemctl restart nginx

Using SysVinit

To Start Nginx, enter the following command:

sudo service nginx start

To Stop Nginx, enter the following command:

sudo service nginx stop

Finally, to Restart Nginx, enter the following command:

sudo service nginx restart

FAQ

How Often Should I Restart Nginx?

Every time you make a change to the configuration files, a restart or reload is necessary to apply those changes.

How often this occurs depends on the developers managing the server. In some cases, this could be on a monthly, weekly, or even a daily basis. However, since it takes very little time to restart, it won’t have any impact on your website.

Just remember that using the reload command is safer than the actual restart command because it will abort if a syntax error is detected.

What Happens If a Syntax Error is Detected When Restarting Nginx?

The restart process will fail and Nginx will remain off. Nginx will not turn on until the syntax errors are resolved.

This means your website will remain offline until the issues are fixed. You will need to access the log to see where the error is located. This will tell you the exact line the error occurs so you can quickly fix it.

As such, you need to thoroughly test the code before applying it to Nginx.

When Should I Use Stop & Start Instead of Restart?

If you are taking your website down for planned maintenance, you will generally want to use the Stop command to shut it down.

This also means you will need to use the Start command to turn it back up, but remember that it will not start if it detects a syntax error. Thus, you might need to spend extra time fixing the code if an issue arises.

Is Nginx Only For High-Traffic Websites?

No.

In 2021, Nginx became the most popular web server by surpassing Apache. The platform performs well for both high and low-traffic websites, which is why its popularity has been increasing steadily over the years.

That said, Nginx is more useful for high-traffic sites, but it still performs better even when on a smaller scale compared to Apache.

Can I Use Nginx For My WordPress Website?

Absolutely!

WordPress was written in PHP, thus, it can be run in an Nginx unit. In terms of performance, Nginx is an excellent choice for WordPress, and it can easily scale as your website grows. If your website gets a lot of traffic, it can run circles around Apache.

And to top it all off, it’s actually easier to set up.

The only issue you will run into is that most web hosts default to Apache. Thus, you will first need to make sure your web hosting company supports Nginx, and then contact them to help you transition to it.

Note: This won’t be possible for shared hosting plans. Thus, you would need a dedicated server.

Is Nginx Easier to Use Than Apache?

Generally speaking, Apache is slightly easier to use when looking at a beginner scenario.

That is exactly why web hosting companies default to Apache. Any software or features you want to use on your website has been tested with Apache and is still the default for testing environments.

How does this make it easier?

Typically you may need to take an extra step or make a small alteration to get something to work outside of Apache. While it’s not a big deal at all for veteran developers, it can be a bit much for beginners to do.

That said, I still want to stress that Nginx is easy to use, but there is a good reason why Apache is still the default choice.

You Are Going to Restart Nginx A Lot

Nginx is an excellent piece of web server software that a lot of websites use. If you plan to regularly make changes to the configuration files, you are going to end up restarting Nginx a lot. The good news is that it’s pretty easy to do.

The only problem you may run into is that Nginx does not restart due to a syntax error. While this may be scary at first, it’s not unheard of. Just stay calm, and quickly check the error log to identify the problem.

As long as you do this, you should have an easy time managing your Nginx server.

How often do you make changes to the configuration files? Do you use the Reload or Restart command when making changes?

The post How to Manage Nginx with Start, Stop, and Restart appeared first on GreenGeeks.