Viewing 5 replies - 1 through 5 (of 5 total)
  • Moderator James Huff

    (@macmanx)

    That error is from Cloudflare, not WordPress.

    I recommend checking with their support, maybe there’s a security rule you hit somehow.

    Thread Starter daronsong

    (@daronsong)

    I fixed it by adding

    add_header Content-Security-Policy “default-src ‘self’ https: data: ‘unsafe-inline’ ‘unsafe-eval’; connect-src ‘self’ *.example.ca; frame-src ‘self’ https: blob:;” always;

    to the nginx.conf file

    • This reply was modified 9 months, 2 weeks ago by daronsong.

    Thanks, @daronsong You saved my day. Sel-hosted too. I’m withous words.

    @daronsong Can you share what was the root cause of your CSP misconfiguration ? (plugin changed the CSP or something else?)
    I have the same problem, and it appeared only after some time of making my website.
    Purely changing the CSP settings isn’t safe, if you don’t know what is causing the error according to my hosting support…

    Thread Starter daronsong

    (@daronsong)

    @alexsikov I’ve since moved to a hosted WordPress instance as I didn’t have the time or attention anymore to deal with maintenance on my own

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.