Request failed with status code 403 - Forum | JoomShaper
Staff replied SP Page Builder

Request failed with status code 403

Asked by allreps.ltda 9 months ago Last activity 8 months ago

Can not save any page in JoomShaper : message Request failed with status code 403

8 replies

Ziaul Kabir Staff

Hello,

Thanks for reaching out to us.

Please contact your hosting provider and ask them to disable ModSecurity or any AWF rules that may be blocking this request.

Right now, when you hit “Save,” the request is being blocked by your hosting environment.

Thanks.

allreps.ltda Asked this

The error only occurs when editing in the backend; it does not occur when editing in the front end.

Answer from Godaddy hosting:

Thank you for reaching out regarding the 403 error you're experiencing with JoomShaper in your Joomla installation.

We understand how frustrating these types of issues can be when you're trying to manage your website content.

We've conducted a thorough review of your server configuration and found that while ModSecurity was installed, there were no active rules or vendor configurations that would typically cause the blocking behavior you're experiencing. As a precautionary measure, we've removed ModSecurity from your server to eliminate it as a potential cause. This can easily be reinstalled later if needed and you determine it wasn't the source of the problem.

but the error still appears with the change on the server.

allreps.ltda Asked this

Hello, any news on how to resolve this problem?

Ziaul Kabir Staff

Could you please share temporary administrator access to your Joomla backend? You can provide the credentials securely in the hidden content section. Also, please take a full backup of your site before we make any changes.

Once I have access, I’ll investigate further and see what’s causing the issue. Let me know once you’ve shared the details!

Best regards,

allreps.ltda Asked this

Hi, I shared the access, thanks

Nicolas Pascault

Hi - I am joining this conversation because I am experiencing the same issue with several sites.

On my side, it seems that there is an issue with the "Securitycheck" extension : If I disable Securitycheck, the error disappears.

This behavior only appeared after Securitycheck's latest update...

(Maybe this helps)

Best,
Nicolas

allreps.ltda Asked this

Hi Nicolas you are right, the problem was Securitycheck extension.

Thanks

Ziaul Kabir Staff

So, Your issues is resolved?

Thanks

Nicolas Pascault

Update on my side : this error only seems to happen with back-end editing.
Front-end editing seems to work normally...

Log in to reply.