When integrating with Ezoic, the system acts as a proxy between your site and your users to provide an Ezoic version of your site. As a result, when Ezoic is enabled, your origin server will see requests as coming from Amazon Web Services (AWS) instead of directly from your users' IP addresses. This indirect routing can sometimes be misidentified as 'bot traffic' by your hosting provider, leading to origin errors, such as pages not loading or login pages failing to work.
To address origin errors and permission denied issues (403 errors) after login, it is essential to understand the impact of firewalls and security plugins. Many hosts have a separate firewall for WordPress logins, which requires Ezoic's IP addresses to be whitelisted. Failure to do so can block legitimate traffic and prevent successful logins. Additionally, security plugins like WordFence or WP Cerber might misinterpret Ezoic's IP addresses as bots, causing legitimate login attempts to fail.
For resolving these issues, whitelist Ezoic's IP addresses both on your server and within any security plugins you may be using. For further troubleshooting, if these steps do not resolve the issue, contacting Ezoic's support team and creating a test-login account can help diagnose and address the problem more effectively.