Cannot save page: `Server Error (403 Forbidden)`

Hi,

To troubleshoot the 403 error when saving or publishing, Kindly check the article below:

403 error when attempting to update a page: This can be due to a security plugin such as WordFence and others.
To sort this out, activate the learning mode of this plugin or contact their support. This issue can also be due to the firewall of your server, so this has to be checked with your hosting company.

For reference: The Publish / Update Button Does Not Work

Lastly, kindly double-check the code you are inserting as it could be causing the issue.

I hope this information helped with your issue.

Thanks for the reply. Here are my follow-ups.

>> This can be due to a security plugin such as WordFence and others.

I have Wordfence installed. I tried deactivating it, but the issue is still present.

>> Lastly, kindly double-check the code you are inserting as it could be causing the issue.

As I mentioned in my original ticket, the line of code that causes the issue is:

<input type="image" src="https://www.sandbox.paypal.com/en_US/i/btn/btn_donateCC_LG.gif" border="0" name="submit" onClick="CalculateOrder(this.form)" alt="PayPal - The safer, easier way to pay online!">

On the surface, there doesn’t seem to be anything offensive about this line. As I mentioned, the default text editor in WordPress seems to accept this line of code without issue. If I add this line in the default WordPress text editor, I am able to both save the page, then load it on the front-end (without any JS console errors).

>> This issue can also be due to the firewall of your server, so this has to be checked with your hosting company.

I’m happy to ask my web host about this. But what exactly should I ask? The first thing they are going to do is note that the issue is not present when I use the default WordPress text editor. So they’re probably going to point to Elementor as the probably cause. Wouldn’t you agree?

>> For reference: The Publish / Update Button Does Not Work

I read that page. At the bottom it reads,

>> If the aforementioned troubleshooting procedure doesn’t help you, please send us your system info so we can try to help you solve the problem.

Can I send you my system info now, and in this channel? If so, what information do you need?

Hello. Has anyone had a chance to read my latest replies on this issue?

Hi Carl,

Saving issues with a 403 error is mainly caused by security plugins or firewalls installed on your the hosting server.

1. have you tried to activate the learning mode of the WordFence plugin? If you have chosen to deactivate the plugin, please try removing your cache and let me know if you see any changes.

2. Try to contact your hosting company and ask them if any firewalls are preventing Elementor from saving.

I hope this information helped you solve your issue.

Thanks for the reply . Here are my follow-ups.

>> please try removing your cache and let me know if you see any changes.

Sure I can try that. But how do I do that exactly?

>> Try to contact your hosting company and ask them if any firewalls are preventing Elementor from saving.

I can, and will, ask them. But is this to say that something on their side might prevent Elementor from saving, yet continue to allow WordPress to save? I ask because, as I mentioned, if I edit the page with the default WordPress text editor, I can save the page without issue. I have a feeling my web host will immediately point to Elementor and say the issue lies with that plugin. But I will ask. Stand by.

Thanks.

• This reply was modified 5 years, 2 months ago by Carl Gross.

@carlgross Do not create duplicate or “(follow up)” topics. Those are removed when found and I have removed your new one.

If you have something to add then do so here.

This post has been marked ‘resolved.’ If I reply here, will the moderators receive an email notification? My understanding was ‘no,’ which is why I created the new post.

I understand you removed the new post. But is the text of that post accessible at all? There was a lot of new information I provided in that post. I hope it is still accessible so I can copy/paste if needed.

To update anyone else that might experience this issue, here is an update. The site in-particular is hosted by DreamHost. I did some testing on other sites. I tested the issue on a local site, and on site hosted by another company (Go Daddy). Neither site exhibited the same issue. So I guess we can rule out Elementor as the cause for now. Unfortunately DreamHost doesn’t seem keen on assisting, saying it is beyond the scope of their support :-/