icontrolwp blocks Tawk.to

  • Resolved Brad Johnson

    (@p4fbradjohnson)


    7 years, 9 months ago

    Hi,

    thank you for this great plugin! The brute force attacks have basically stopped.

    However, I just received an email from iControlWp:

    – Page parameter failed firewall check. The offending parameter was “__tawkuuid” with a value of “e::passion4fashion.co.za::r/vO0rkjnH2gzSVUoNBOwor0BWOpVZZnAb/IqIBNJh 0xd13D wCuBKGR3s8Lc m::2”.
    – Firewall Trigger: WordPress Terms.
    – Firewall Block Response: Visitor connection was killed with wp_die() and a message.

    The IP is a South African IP and is not blocked at all. (I try avoid IP blocking).

    Please kindly advise.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Paul

    (@paultgoodchild)

    I assume this should be in the Shield support forum? Anyways, it all comes to the same place ??

    The IP isn’t blocked, but the particular request was. If you need to permit requests with this parameter (__tawkuuid) then see here for parameter white listing: https://www.ads-software.com/plugins/wp-simple-firewall/faq/

    you’ll probably want something like
    *, __tawkuuid

    You can replace the “*” if you know the precise page that will be used with this parameter.

    Thread Starter Brad Johnson

    (@p4fbradjohnson)

    Hi Paul,

    thank you so much for the quick response! Impressive!!

    I have white listed the parameter in Shield. However the application still did not load. I did an inspect with chrome and came up with this error:

    Uncaught EvalError: Refused to evaluate a string as JavaScript because ‘unsafe-eval’ is not an allowed source of script in the following Content Security Policy directive: “default-src ‘self’ data: ‘unsafe-inline’ https: *”.

    at Object.$_TAWK_JSON.parse (default:100)
    at default:618
    at XMLHttpRequest.m.onreadystatechange (default:221)
    at XMLHttpRequest.nrWrapper (VM598:4)

    So I ticked Allow Javascript eval() and it worked.

    Just so you know, I read your Misinformation VIRUS post! Brilliant! I think more WP Admins need to think like that. (hence why I tried to figure out the problem, before coming back to you saying that it was resolved!

    Plugin Author Paul

    (@paultgoodchild)

    Brilliant… glad you got it resolved and dug into the problem. It means you’ll be well-equiped to deal with future issues that may come up. Great job! ??

    Thanks for reporting back too!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘icontrolwp blocks Tawk.to’ is closed to new replies.