WAIT: 403 Server Error Forbidden - CPT Problem

Bugs
1

Browser: Brave / Safari / Firefox Developer
OS: macOS
URL: Zoekmachine Optimalisatie (SEO) - Marketence
Video: Error 403 Bricks Builder | Marketence

Hello guys,

I encountered an Error while working on client’s website.

Everything was working fine, but suddenly on CPT page for Services I started getting 403 Errors when I tried to change icon in the card and save the progress. The page started displaying the errors for couple minutes, saving was loading forever, and changes did not appear on the frontend.

You can see example of the problem in the video attached above.

Eventually error stopped, but when I tried to do it again, the same thing happened.

I tested it on 3 different browsers: Brave / Safari / Firefox Developer.

I cleaned cache multiple times, looked for solution but didn’t find one yet.

We contacted hosting provider, but I thought that perhaps someone here would know how to tackle this problem.

Thank you for help in advance!

2

Hi Wikor,
Welcome to the forum, and thanks so much for your report!

Please have a look at your PHP error logs. There, you should be able to see what is causing the error.

However, it will probably be a server problem, as there are many similar reports independent of Bricks: Stackoverflow

Please let me know if you get any feedback from your hoster.

Best regards,
timmse

3

I had the same issue and in my case the 403 error was not coming from Bricks itself but from Wordfence on the main production site.

My staging site was located inside the main site’s /public_html/staging folder, so the firewall from the production site was also protecting (and blocking) requests in the staging folder.

What worked for me:

  1. On the main site, set Wordfence to Learning Mode. (I kept Wordfence disabled on the staging site, since the main site’s firewall already covers it.)
  2. Save the template in the staging installation.
  3. Switch Wordfence back to Enabled and Protecting on the main site.

After that, saving templates in staging worked fine.

It’s also worth mentioning that the initial post on this thread, Lazevsky mentios that the 403 issue was triggered when changing an icon, especially if the icon contains an inline SVG embedded as code. Wordfence (and sometimes ModSecurity) tends to flag those AJAX requests as suspicious and blocks them with a 403.