When you integrate with Ezoic, the system will act as a proxy between your site and your users. Without a proxy, requests for your content would come directly from the user's IP address. When Ezoic is turned on, the requests will start coming via IP addresses from Amazon's Web Servers. This can sometimes be incorrect, and be classified as a 'bot' traffic by your sever, or prevent users from accessing content behind a login.
There are three main options to help your host pass along requests from the Ezoic system:
- Whitelisting Ezoic's IP Addresses- choose this if your host is blocking requests coming via Ezoics's IP Addresses. You might see a '403 Forbidden' or 'Origin error'.
- User Agent Authentication- another option to prevent your host from blocking Ezoic's request, it allows your server to pass along requests that come via Ezoic.
- X-Forwarded-For-XPP or HTTP Header- This is the option to choose if you need your server to be able to see the 'real' IP of your user.
- Whitelisting Ezoic's IP Adresses: in rare cases, your hosting company may inadvertently block Ezoic's servers (AWS) from your site's content. You may see a 403 Access Forbidden error or Origin Error when this occurs. If the hosts are using IP addresses to block, feel free to ask them to whitelist Ezoic's range of IP addresses.
- User Agent Authentication: if your host is blocking requests, you can also ask them to set user agent authentication for 'X-middleton' (which comes with all requests).
- X-Forwarded-For Header: in plain English, the X-Forwarded-For header is a header field you can use to make sure the 'real' IP of your users is passed along by a proxy like Ezoic or CloudFlare. Without this, only the IP of the proxy would be passed along. Some features (like login forms) might 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.