When you integrate with Ezoic, the system will act as a proxy between your site and your users, so that we can provide an Ezoic version of your site.

However, if you're in the early stages of Ezoic integration and experience an origin error, this may be because your host has miscategorized Ezoic traffic, as explained below.

There is no one single cause of an origin error - for example, it may simply be that the site is down at your host, in which case Ezoic won't be able to directly help. What is an Origin Error?ДЄn Origin Error occurs whenever the origin server isn't providing the site to Ezoic's servers as expected. * If you are on a shared server and your host refuses to implement any of the above fixes on a shared server, then you may need to consider asking them if they would do so if you upgraded your hosting package, or else look at the possibility of using another hosting provider. If you explain this to your host, they should be able to find the request IP there, rather than by using a 'requested-by' header. With all requests, Ezoic will send the actual IP of the user under the request header 'x-middleton-ip'. You can find instructions for implementing X-Forwarded-For on your site here. You can add this header to your server (and let your host know that they need to look for it and authorize requests on that basis), or ask your host to do it for you. This is especially helpful for specific features (like login forms) that need to see the original user's IP. The X-Forwarded-For Header is a header field that you can use to make sure the 'real' IP of your users is passed along by a proxy like Ezoic or Cloudflare. Once you have whitelisted the above IPs, please contact our team so to complete the request for you and check that everything has gone through. You may find that you are able to resolve your problem just by taking one of these steps, but if you've experienced an issue then it's good practice to implement each of the solutions below. Otherwise, there are four main options to help your host accept requests from Ezoic, any of which can be implemented by your host at your request. If you discover it is a security plugin blocking Ezoic, you can whitelist Ezoic's IP ranges (linked at the end of this article) via their plugin (if you are using Wordfence, they have specific instructions for how you can make sure that requests via the Ezoic proxy are whitelisted. If you are still seeing an origin error after confirming that your DNS records and SSL settings are configured correctly, then it's likely that Ezoic IPs are being miscategorized as 'bot traffic' by either a security feature or your host. If you have recently moved hosts or your existing host has moved your site to a new server, then the origin server IPs will likely have changed, and the copy of these in your Ezoic account needs to be updated accordingly. Regardless of the error you are seeing, it's a good idea to first check that the DNS records at your host match those you have entered at Ezoic and that your SSL settings are correct. Key Indicators of an Origin Error Solutions to Origin Errors

How to fix origin download error