chevron_right
chevron_right
My Site Is Down
Technical Support/Troubleshooting

My Site Is Down

Last Updated a few days ago
Article Navigation
Introduction
Overview
Steps
Troubleshooting
Best Practices or Tips
Need Further Assistance?

Introduction

Discovering your site is inaccessible is a critical issue that requires immediate systematic troubleshooting. A "site down" state can be caused by anything from an expired SSL certificate to a hosting server outage or a DNS misconfiguration. Use the following steps to identify the root cause and restore service.

Overview

Before changing settings, determine if the site is down for everyone or just for you. Use a third-party tool like "Down For Everyone Or Just Me" to verify global accessibility.

  • If it's just you: Clear your browser cache or try an Incognito window.

  • If it's everyone: Follow the integration-specific steps below.

Steps

1. For JavaScript & WordPress Integration (Primary)

If you are integrated via JavaScript or the WordPress plugin, Ezoic is not "in front" of your site. If the site is down, the issue is likely with your origin server.

  1. Check Your Host: Log in to your hosting provider (e.g., Bluehost, SiteGround) to see if there is an active outage or if your account has been suspended.

  2. Plugin Conflicts: If you recently updated a plugin, it may be crashing your CMS. Deactivate the Ezoic plugin via FTP or your host’s file manager to see if the site returns.

  3. Resource Limits: Check if your server has hit its CPU or RAM limits, which can cause "508 Resource Limit Reached" errors.

2. For Cloud & Nameserver Integration (Secondary)

If you are integrated via the Cloud, Ezoic sits between your visitor and your host.

  1. Check Origin Errors: If you see an Ezoic-branded error page (e.g., "Origin Error"), it means Ezoic is active, but your host is not responding to our requests.

  2. Verify DNS: Ensure your A Records in the Ezoic Settings > DNS tab match exactly what is listed at your host.

  3. SSL Handshake: If you see "SSL Protocol Error," check that your SSL settings in Ezoic (Settings > SSL) match your host’s encryption (Full, Flexible, or Strict).

Troubleshooting

520 / 521 / 522 (Origin Errors)

These codes indicate that Ezoic is trying to reach your server, but your server is refusing the connection or timing out.

  • Fix: Contact your host and ensure Ezoic’s IP addresses are "whitelisted" in their firewall. If the host blocks Ezoic's optimization crawlers, the site will appear down.

403 Forbidden

This usually means your server’s security (like ModSecurity or a security plugin) is blocking the request.

  • Fix: Temporarily disable security plugins like Wordfence to see if the site restores.

1016 / DNS Errors

This happens if the DNS records in Ezoic are pointed to the wrong IP address or if the Nameservers were recently changed and haven't fully propagated.

  • Fix: Use a DNS checker to ensure your Nameservers are pointing to the correct Ezoic addresses.

Best Practices or Tips

The JavaScript Advantage:

If you frequently experience DNS or SSL "Site Down" issues while Cloud integrated, we recommend switching to JavaScript Integration. Because JS integration is lightweight and sits on the page level, it cannot "break" your DNS or prevent your site from loading due to a cloud handshake failure.

Keep a Backup:

Always have a recent backup of your site. If a plugin update causes a "White Screen of Death," a quick restore is the fastest way to get back online.

Monitor Uptime:

Use a free service like UptimeRobot to get instant alerts if your site goes down, allowing you to react before it impacts your revenue.

Confirm Ezoic Status: 

Check ezoicstatus.com to see if Ezoic itself is experiencing a platform-wide outage.

Need Further Assistance?

If you need further assistance with getting your site back up and running, please log in via support.ezoic.com to make use of our dedicated resources for support. We're here to help!

× Enlarged Image

Loading ...