I’ve just installed BricksForge and activated ProForms to begin a tutorial. I typically like to save after every step. After adding ProForms to the page, I get the follow error when I try to save:
Error 406 Error on Save. When I remove ProForms, I cab save again. Any Ideas?
Are you running some kind of firewall serverside? If yes, could you try to deactivate it?
Yes. I tried deactivating both Malcare, Headers Security Advanced & HSTS WP, and Admin and Site Enhancements (ASE), but to no avail. I am still having the same problem 
I noticed on a similar post that you suggested raising the memory limit with the hosting provider. I’m reaching out today to see if that is a viable option
1 Like
Sorry, I didn’t read that properly. It’s unclear to me at this writing if my hosting provider is using their firewall to block any of my plugins. My first response was a list of my security plugins on my WordPress install.
I figured I would share this screen of my Server Environment. Perhaps the minor errors that are showing may be the cause? At a loss and I am so eager to start working with ProForms…
Resolved! Resolved through my hosting company by resolving ModSecurity per this article: Learning About Mod_security and Disabling Mod_security
1 Like
Great! Thanks for letting us know! 
Hi @MMaddMann111
If you don’t mind me asking, did this error occur when trying to just save the default form added to a page with Pro Forms? Or did you make changes to it - e.g. add a field, change a label etc?
If you were following a tutorial, could you link it?
This happened right after dropping the form into my web page (I usually save after each step for good practice). The tutorial I was following was https://www.youtube.com/watch?v=EVgQv4lzL5g
Which was very good and simple btw.
1 Like
Thanks for providing the link. I thought it might be related to another issue but the tutorial doesn’t do any of the things which triggered mod security rules for me. Just be mindful that those firewall rules are there for a reason so you should be very careful when requesting for them to be turned off.
1 Like
Absolutely correct! Thankfully, in my case, it was all fixable by my hosting company and the fix was in within guidelines of the server needs and hosting requirement guidelines. Such a fix should be implemented be the hosting company for best practice.
1 Like
Agreed. Hopefully they only poked a hole in the Firewall/WAF for this specific issue and didn’t turn ModSec off completely. I’ve disclosed an issue privately to the team which was causing false positives in Modsec protected web servers. Hopefully they’ll be able to implement a fix at some point.
1 Like