JamesBondBro
Junior Member
- May 1, 2020
- 108
- 44
Solutions to Origin Errors
There are three main options to help your host accept requests from Ezoic, all of which can be implemented by your host at your request. 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.
Whitelisting Ezoic's IP Addresses
If your host has blocked one or more of Ezoic's IP addresses because it has mistaken it for bot traffic (typically, but not always, accompanied by a '403 Access Forbidden' error, 520, or 'Origin Error'), whitelisting Ezoic's IP addresses will allow your host to recognise and authorize the IP addresses in question.
All you need to do to is see the attachment at the end of this article and send the listed Ezoic IP addresses to your host, requesting that they add them to their whitelist.
User Agent Authentication
If your host cannot whitelist Ezoic's IPs, you can ask them to set user agent authentication for 'X-middleton'. This will enable the host to recognise Ezoic requests due to the presence of 'X-middleton' in the header, which is featured in all requests made by Ezoic.
Set up an X-Forwarded-For Header
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. This is especially helpful for specific features (like login forms) that need to see the original user's IP. You can add this header to your server, or ask your host to do it for you.
--
Original article:
here
There are three main options to help your host accept requests from Ezoic, all of which can be implemented by your host at your request. 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.
Whitelisting Ezoic's IP Addresses
If your host has blocked one or more of Ezoic's IP addresses because it has mistaken it for bot traffic (typically, but not always, accompanied by a '403 Access Forbidden' error, 520, or 'Origin Error'), whitelisting Ezoic's IP addresses will allow your host to recognise and authorize the IP addresses in question.
All you need to do to is see the attachment at the end of this article and send the listed Ezoic IP addresses to your host, requesting that they add them to their whitelist.
User Agent Authentication
If your host cannot whitelist Ezoic's IPs, you can ask them to set user agent authentication for 'X-middleton'. This will enable the host to recognise Ezoic requests due to the presence of 'X-middleton' in the header, which is featured in all requests made by Ezoic.
Set up an X-Forwarded-For Header
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. This is especially helpful for specific features (like login forms) that need to see the original user's IP. You can add this header to your server, or ask your host to do it for you.
--
Original article:
here
- Mar 30, 2018
- 12,094
- 14,361
You can ask ezoic for help they’ll sort it for you
Corpus_Callosum
Newbie
- May 13, 2017
- 9
- 6
Contact their support. I had this problem and they were really helpful. For me, it turned out to be a problem with my hosta ssl cert. I had to call my host 3 times, before they sorted this out. The host were blaming first ezoic, and then the CDN... By the help from Ezoic, I got my host to fix the issue.
ya Ezoic's support solved my issue couple of hours ago
Mikeoh
Registered Member
- Jul 6, 2020
- 72
- 18
Whats the issues about and which hosting are u on?
Tixegeek
Registered Member
- Dec 20, 2021
- 75
- 20
Usually, your hosting block their ip's which create this origin error. Better move the hosing to ezoic and they take care of everything.