Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Hi,

    I changed those lines and it indeed fixed 403 issue also.

    Thanks!

    Hi,

    We also get 403 Forbidden code after we updated plugin to Version 1.16. There is no PHP errors but server log shows the following Apache error: (I have replaced sensitive data with *** characters.)

    [client ***.***.***.***] ModSecurity: Access denied with code 403 (phase 4). Match of “rx \\\\ssrc=\\\\x22https:\\\\/\\\\/www\\\\.googletagmanager\\\\.com\\\\/ns\\\\.html\\\\?id=GTM|\\\\ssrc=\\\\x22https:\\\\/\\\\/w\\\\.soundcloud\\\\.com\\\\/player\\\\/\\\\?url=” against “TX:0” required. [file “/etc/apache2/modsecurity.d/rules/comodo_free/19_Outgoing_FilterInFrame.conf”] [line “14”] [id “214540”] [rev “5”] [msg “COMODO WAF: Possibly malicious iframe tag in output||***.****.***|F|3”] [data “Matched Data: <iframe src=\\x22https://www.googletagmanager.com/ns.html?id=1\\x22 height=\\x220\\x22 width=\\x220\\x22 style=\\x22display:none found within TX:0: <iframe src=\\x22https://www.googletagmanager.com/ns.html?id=1\\x22 height=\\x220\\x22 width=\\x220\\x22 style=\\x22display:none”] [severity “ERROR”] [tag “CWAF”] [tag “FilterInFrame”] [hostname “***.***.***”] [uri “/index.php”] [unique_id “***”], referer: https://***.***.***/***/

Viewing 2 replies - 1 through 2 (of 2 total)