• Resolved Mohsen

    (@msedighiyan86)


    I recently changed the DNSs of my domain (alo-diet.ir).

    I get a 403 error when saving forms that I created before this DNSs change. (Access to this resource on the server is denied!)

    But I don’t have this problem in saving new forms.

    Is there any solution to solve this problem.

    Domain: alodiet.ir

    Previous DNSs: ns61.spadit.com – ns61-2.spadit.com

    New DNSs: ns219.spadit.com – ns219-2.spadit.com

    New IP: 185.141.134.219

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author codepeople

    (@codepeople)

    Hello @msedighiyan86

    The issue you report is usually related to false positives in third-party plugins like Wordfence when the form contains script blocks of code.

    Please send me the link to the page that contains the form you cannot edit to check its structure.

    Best regards.

    Thread Starter Mohsen

    (@msedighiyan86)

    For example, this page: https://alo-diet.ir/13908-2/

    Plugin Author codepeople

    (@codepeople)

    Hello @msedighiyan86

    The URL provided loads a blank page from the cache generated by the “LiteSpeed Cache” plugin.

    Could you please indicate the form ID?

    Best regards.

    Thread Starter Mohsen

    (@msedighiyan86)

    This is the form Shortcode: [CP_CALCULATED_FIELDS id=”75″]

    Thread Starter Mohsen

    (@msedighiyan86)

    Plugin Author codepeople

    (@codepeople)

    Hello @msedighiyan86

    To check if the issue is caused by a false positive related to WordFence, or server rules, please remove the script blocks of code from the fieldname59 and fieldname66 fields’ content attributes and try to save the modifications.

    Best regards.

    Thread Starter Mohsen

    (@msedighiyan86)

    After deleting fields 59 and 66, I try to save the changes, but I still get a 403 error and the changes are not saved.
    The script of these two fields:
    Field 59:

    <script>fbuilderjQuery(document).one('showHideDepEvent', function(){ jQuery('#fbuilder .pb0 .pbNext').text('Analyze');} );</script>

    Field 66:

      <script type="text/javascript">
            if (document.addEventListener) {
                document.addEventListener('contextmenu', function (e) {
                    e.preventDefault();
                }, false);
            } else {
                document.attachEvent('oncontextmenu', function () {
                    window.event.returnValue = false;
                });
            }
        </script>

    I also disabled the plugins that I updated recently. Again, I get error 403 when saving this form.

    Plugin Author codepeople

    (@codepeople)

    Hello @msedighiyan86

    If you can modify your other forms but not this specific form, and you deactivate the other plugins on your WordPress, there is a server rule that generates a false-positive and blocks the save changes action.

    Unfortunately, the process of identifying its cause is not easy. It could be a field label, an equation, or a simple combination of characters. The majority of these regulations rely on regular expressions.

    One way to troubleshoot an issue where the server is blocking the save changes is to duplicate the current form to preserve its structure. Then, you can systematically delete fields from the duplicated form until you identify the field that is causing the issue. This process helps to isolate the problematic field and find a solution.

    However, if you contact your hosting provider, I am pretty sure they will be able to adjust the server rules to allow you to save the form modifications.

    Best regards.

    Thread Starter Mohsen

    (@msedighiyan86)

    I talked to my hosting providers. They solved the problem and said in response:

    Your request has been checked and the problem of saving the forms has been resolved.

    This error was caused by the unusual content (sql injection) that these forms had.

    In fact, this security plugin (which caused the 403 error) was disabled on your site so that this error would no longer be seen, but obviously, if the security of your site is compromised, you are responsible for it.

    Plugin Author codepeople

    (@codepeople)

    Hello @msedighiyan86,

    Perfect. As I said previously, some code in your website was generating a false-positive due to the form structure.

    Best regards.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘403 ERROR, forbidden access.’ is closed to new replies.