Hello
unable to save SP page, getting this error "Request failed with status code 403"
please provide solution
Staff replied
SP Page Builder
Unable to Save SP page
12 replies
Paul Frankowski Senior Staff
Hi,
Share access, otherwise, we are blind.
Paul Frankowski Senior Staff
But before read >> https://www.joomshaper.com/documentation/sp-page-builder/troubleshooting#i-cant-save-page-blocked-by-cors-policy
Directive Team Asked this
hello
admin detail added.
please check and resolve the issue
Directive Team Asked this
1 year ago
· edited
checked document
applied those changes, but the issue still hasn't been resolved.
also added admin details in the comment above
Directive Team Asked this
Hello Just checking in on this ticket, we provided admin access and tried the troubleshooting steps but the issue persists. We are unable to make any changes to any pages on the website.
Directive Team Asked this
Hello? Has anyone been able to take a look at this?
Paul Frankowski Senior Staff
-
I cannot get into admin area, I clicked link 3x and now "Oops, something went wrong. This message normally occurs after too many failed login attempts, or some other suspicious activity. "
-
Since when you have that issue. Becuase I saw that your site is using SPPB already. Maybe that problem is caused by Security extension that you have there. This is popular reason of 403. If you have any, disable and recheck, and if that helps, contact with extension support how to solve it / correct settings.
Directive Team Asked this
See updated Admin URL and notes in hidden content
Paul Frankowski Senior Staff
1 year ago
· edited
I think it's caused by Akeeba Tools Pro settings. Quite popular.
Paul Frankowski Senior Staff
Yes, it was caused by ATP security level. I used WAF Exceptions to fix it - but please ask Akeeba Support - how it can be done better, and share answer here, so I will be able to update documenation.
Directive Team Asked this
Hey Paul,
Thanks for checking into this, unfortunatley we are still getting the 403 error when trying to save an SP page. We started up a ticket with Akeeba and we will let you know what they say. I can confirm the messaging you received was from an Admin Tools block, probably because the original credentials/admin URL were incorrect. Are you sure the saving issue is due to Admin Tools as well? We manage ALOT of sites, and admin tools is on all of them and we have never run into this error. The site does use CloudFlare as well if you think that might be an issue, please let us know what should be done.
Paul Frankowski Senior Staff
1 year ago
· edited
In general, it's not SPPB issue, something else is blocking process of saving. Otherwise you would have the same 403 everywhere.
I was able 8h ago create "ABC JoomShaper Test" but now "SAVE" don't work again ??!!!
Paul Frankowski Senior Staff
1 year ago
· edited
The error Request failed with status code 403 in Joomla (with a message from Axios, so it's probably JS/AJAX in the background) means that the browser received a Forbidden response from the server when it tried to save the page via an HTTP request.
Some extensions (e.g., Admin Tools Pro, Akeeba Web Application Firewall) or modules ModSecurity on the server block POST requests if they contain “suspicious” data.
Browser Error Console on Page view tells that
So yes, I would disable ModSecurity for 15min and recheck. The same with CloudFlare.
If will help, you have to make SPPB trusted in that software. Hosting Support should help more. My options are limited.
Log in to reply.