IP Geo block creating “origin errors”

  • Resolved FireMyst

    (@firemyst)


    6 years, 8 months ago

    Hey everyone:

    So I’ve been integrating my sites with Ezoic for some ad revenue. Before doing this, IP Geo block was working like a charm.

    Unfortunately, now on my sites I receive “origin error”.

    According to the Ezoic help article:
    https://support.ezoic.com/hc/en-us/articles/206245065-Origin-Errors-and-Other-Error-Messages- this is why it’s happening.

    However, I found on my site it’s not at the host level, but rather the IP Geo block level because when I rename the IP Geo block plugin folder, I can access all my sites and I don’t receive that error any more.

    My questions are:
    1) when I rename the IP Geo block plugin folder back to what it should be so I can get in and disable the plugin through WordPress, I cannot access my admin area because of the “origin error”. How can I get around this?

    2) How do I need to configure the IP Geo Block settings to allow for Ezoic and the AWS they describe in their article? I’ve tried putting in all their IP address in the “Whitelist of extra IP addresses prior to country code” configuration item, but that hasn’t helped.

    I am running the latest version of WordPress and Version 3.0.9 of IP Geo Block.

    Thank you!

    • This topic was modified 6 years, 8 months ago by FireMyst.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter FireMyst

    (@firemyst)

    This looks like it was caused by some DNS settings not matching up on EZoic side of things.

    So nice to see IP-Geo-Block was doing its job. ??

    Plugin Author tokkonopapa

    (@tokkonopapa)

    Hi @firemyst,

    Although You marked this topic as resolved, I’ll provide you some suggestions related to your questions.

    1) I do not recommend “renaming (or even deleting) the plugin’s folder” even if you can log in and deactivate the plugin, because normal deactivating process for this plugin could not be executed properly.

    Please follow the document “What should I do when I’m locked out?“.

    2) After I read their article, I understood that Ezoic works like proxy server in AWS. So all the requests (including yours) to your host will be sent to Ezoic server and Ezoic server will access your host.

    They have a lot of fragmented IP address ranges (CIDR). And it would not be good if you put all of them into the “Whitelist of extra IP addresses prior to country code” because of its validation cost. Please consider to use AS Number to identify the AWS server. Or I think the best way is to configure to accept those IPs at your server level.

    And then you should put HTTP_X_FORWARDED_FOR into “$_SERVER keys to retrieve extra IP addresses” to validate the real client IP address.

    After you success to configure DNS, all the requests to your host (including malicious access?) may come from Ezoic server. But you can verify the client IP address using HTTP_X_FORWARDED_FOR.

    If you sill have some troubles, please feel free to ask more!

    • This reply was modified 6 years, 8 months ago by tokkonopapa.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘IP Geo block creating “origin errors”’ is closed to new replies.

Tags