How To Fix Ezoic Origin Error [The Ultimate Guide 2023]

This guide is all about how I fixed the Ezoic origin error issue after integrating my website with Ezoic.

Some links on this site are affiliate links, so I might earn a commisison if you make a purchase through them. Such commissions allow me to maintain and improve this site. Read full Disclosure

I applied for Ezoic with this website and got approved.

Back to the main issue; how to fix origin error from Ezoic.

The main reason why most websites using Ezoic experience origin error is that most hosts usually miscategorize Ezoic IP addresses as bot traffic. In some cases, this can be caused by a security plugin.

Ezoic uses reverse proxy which means that when people visit your website, all requests will be replaced with Ezoic IP addresses rather than visitors’ IP addresses.

Since all requests are coming from a single or few IP addresses, your host takes them as bots attacking your websites so they are blocked.

Origin error usually happens to websites on shared hosting plans, especially on Namecheap.

Some users on a shared hosting plan on other hosting companies said they didn’t experience origin errors on their websites monetized with Ezoic.

Nevertheless, if you are experiencing an Ezoic origin error, the first step to fix it is to whitelist all Ezoic IP addresses. Unfortunately, that cannot be possible as many hosts will ask you to upgrade to a higher plan such as VPS or cloud hosting before you can whitelist the Ezoic IP addresses.

My Origin Error Experience

As my first time using Ezoic, I thought it was an easier process like the Google AdSense application and approval where you place the codes on your website and that is all.

When I integrated my website with Ezoic using their nameservers, my website started having critical issues and origin error.

So I contacted Ezoic support; I was told to contact my host and to tell them to whitelist the Ezoic IP addresses.

Namecheap said for security reasons it is not possible to whitelist third-party IP addresses on shared hosting except I upgrade to a higher plan.

Then I send the feedback to Ezoic and I was given other options that I should  set up an x-forwarded-for header.

Since I was using WordPress, I was told to copy and paste the code below to my  wp-config.php file.

// Use X-Forwarded-For HTTP Header to Get Visitor’s Real IP Address

if ( isset( $_SERVER[‘HTTP_X_FORWARDED_FOR’] ) ) {

$http_x_headers = explode( ‘,’, $_SERVER[‘HTTP_X_FORWARDED_FOR’] );

$_SERVER[‘REMOTE_ADDR’] = $http_x_headers[0];

}

I wasn’t ready to temper with my website theme so I didn’t buy this idea.

I was given another option to download the ‘proxy real IP’ plugin. I downloaded and install the plugin with the hope that my website will stop having origin error.

The proxy real IP plugin appears to be abandoned (updated 27/12/2012, tested to WP 3.3.2) and has never been tested with the 3 major releases on WordPress.  Nevertheless, Ezoic still recommends using the plugin to stop the origin error. This couldn’t fix the origin error.

Before that, I have switched to Cloudflare nameservers and added my website to Cloudflare as advised by a friend who also uses Ezoic for one of his websites. Cloudflare is the number one in usage statistics of reverse proxy services for websites in the entire world.

Ezoic is a certified Cloudflare partner, so there ought not to be any negative impact from the nameservers and SSL.

The Ezoic origin error stopped but another issue started. The website started having Cloudflare 520 error (web server is returning an unknown error).

I contacted Ezoic once again, I was told to try “User-Authorization” where I permit user-agents ending in x-middleton/1 to not be miscategorized as bot traffic on my site. My hosting package won’t permit me to do that.

Now it was dawn on me that I will need to switch to another host. I was advised to move my website to Ezoic WordPress free hosting or another host that won’t block Ezoic IP addresses.

What did I do?

I decided to return to how everything was by switching back to Namecheap nameservers and starting afresh.

I was determined to figure out a permanent solution to this.

How To Fix Origin Error

Two Methods To Fixed Ezoic Origin Error

Method 1

The next stages of what I will show you might be able to help you to fix the Ezoic origin error.

1. Use the Ezoic Nameservers
chipmunk.ezoicns.com
javanese.ezoicns.com

2. In your Ezoic account, for site integration, use Name Servers integration.

3. Do not activate Cloudfare in your Ezoic account.

4. For the SSL settings, turn SSL type to Strict. For Automatic HTTPS Redirect, turn it ON.

5. Deactivated and delete the proxy real IP plugin if you have it installed. Install the Wordfence security plugin to whitelist all of the Ezoic IP addresses. First, make sure to tick Use the X-Forwarded-For HTTP header.

Next, click on Edit trusted proxies and paste all the Ezoic IP addresses in the box and save.

Wordfence security plugin has a feature for whitelisting visitors’ IP addresses. I wonder why Ezoic is yet to recommend the plugin and update it on their support page.

Method 2

This method is similar to the first but has a little slight difference in the settings.

1. Use the Cloudflare Nameservers
gannon.ns.cloudflare.com
liberty.ns.cloudflare.com

2. In your Ezoic account, for site integration, use Cloudflare integration or WordPress Plugin.

3. Activate Cloudfare in your Ezoic account. If you are integrating your site using the WordPress plugin, you should not activate Cloudflare here.

4. For the SSL settings, turn SSL type to Strict. For Automatic HTTPS Redirect, turn it ON

5. Deactivated and delete the proxy real IP plugin if you have it installed. Install the Wordfence security plugin to whitelist all of the Ezoic IP addresses. First, make sure to tick Use the Cloudflare “CF-Connecting-IP” HTTP header to get a visitor IP.

Next, click Edit trusted proxies, paste all the Ezoic IP addresses in the box, and save.

If you installed the Ezoic WordPress plugin, you would get a compatibility warning that “the following plugin(s) must be disabled to fully utilize Ezoic WordPress integration without issues or conflicts.” You should ignore the message. Do not deactivate the plugin as long it is Wordfence security.

You can deactivate other plugins such as WP Super Cache or other caching plugins. Ezoic has Leap features for caching and speed performance improvements. Ezoic’s Leap optimization features may require that these plugins be turned off or that all minification, caching, or “speed” optimizations are disabled to prevent conflicts. Leap optimally replaces the functionality of these plugins as it relates to site speed.

How To Get The Cloudflare Nameservers

You can’t just copy any Cloudflare nameservers and add them to your domain host. You will need to create an account with Cloudflare and add your domain.

You should see the assigned nameservers to your account and add them to your domain.

All of the above settings can stop the Ezoic origin error on your website. You can try it if it will work for you. For me, I don’t need to change my host anymore for now.

You might not need to follow all the exact settings on this guide but it is necessary to use the Wordfence security plugin to whitelist the IP addresses.

If your website is still encountering Ezoic origin error after following my guide, you can leave a comment below or shoot me a message for assistance.

You may still have origin error or any other errors for using Ezoic or Cloudflare integration after installing the Wordfence security. Some host only allows whitelisting IPs from the server side and not from the website dashboard.

So what this means is that any plugin or any other method used won’t work except if you upgrade to VPS hosting or change to another host that has no issue with Ezoic IP addresses.

Method 3

This method is sure to work. I am 100% sure of it except you didn’t do something right. This method involves using WordPress Integration despite the fact your site is connected to Cloudflare or Ezoic nameservers.

The latest development on origin error with Namecheap

Namecheap has fixed their shared hosting blocking of Ezoic IP addresses. So now, it is unlikely for you to experience an origin error if you integrate your site through Cloudflare. Occasionally but not frequently, you might experience 520 error from Cloudflare.

FAQs on Ezoic Origin Error

What Is The Ezoic Origin Error?

The Ezoic origin error is an issue that occurs when Ezoic, an advertising platform, encounters difficulties connecting to your website’s origin server.

Why Does The Ezoic Origin Error Occur?

The error can be triggered by various factors, such as incorrect server configurations, DNS misconfigurations, firewall settings, or conflicts with other plugins or services.

How Can I Fix The Ezoic Origin Error?

Start by checking your server configurations, ensuring proper DNS settings, and verifying firewall rules. Clearing cache, disabling conflicting plugins, or contacting Ezoic support for assistance can also help resolve the error.

Can A Misconfigured SSL Certificate Cause The Ezoic Origin Error?

Yes, an incorrect SSL certificate configuration can lead to the Ezoic origin error. Ensure that your SSL certificate is correctly installed and configured for your domain.

Is It Necessary To Contact Ezoic Support For Help?

While you can attempt to troubleshoot the error yourself, contacting Ezoic support is recommended if the issue persists or if you require further guidance specific to your Ezoic setup.

Are There Any Additional Precautions To Prevent The Ezoic Origin Error?

Regularly monitor your server and website configurations, stay updated with Ezoic’s guidelines, and ensure compatibility with other services or plugins to minimize the chances of encountering this error.

Last Updated 6/13/2023