Plugin Firewall One of more of your Plugin Firewall Whitelist rules are not valid

Home Forums BulletProof Security Pro Plugin Firewall One of more of your Plugin Firewall Whitelist rules are not valid

Viewing 3 posts - 31 through 33 (of 33 total)
  • Author
  • #26175
    AITpro Admin

    Yeah we know.  Removal of those older defunct things keeps getting bumped back due to higher priority tasks taking precedence, but BPS Pro 11.5 will have these older things corrected/removed/etc.  You do not need the Regex whitelist rule since I completely misunderstood what the issue/problem is/was.  The Plugin Firewall Tools section will also display error checking messages if there is a problem with any whitelist rules, but since newer code automatically corrects any invalid code/whitelist rules then this is also in a transitional state from older code and newer code.  So at this point your Plugin Firewall whitelist rules are correct and nothing else needs to be done.

    ARQ only needs to be turned off if you are manually editing or uploading files to your website via FTP.


    [Topic has been merged into this relevant Topic]

    I am trying to fix this white list problem but I can´t get it done, I see one of the plugins has a https its the amazon pay plugin, but don´t I need this? And when I try to remove it it says that I have extra white spaces even though I make sure I dont…
    How can I fix this without disturbing the function of the amazon payment?

    Error: One or more of your Whitelist rules are not valid
    Click on the Plugin Firewall Whitelist Tools accordion tab and correct/fix any invalid plugin whitelist rules in the Plugins Script|File Whitelist Text Area.
    Edit your Whitelist rules and correct whitelist rules that contain any of these invalid things:
    ver=, page=, src=, www, http, https, href, .com, .net, .org, .biz, .info, .gov, .edu and
    click the Save Whitelist Options button and activate the Plugin Firewall again.
    Valid plugin Whitelist rules MUST use ONLY this Format: /plugin-folder-name/plugin-script.js, /plugin-folder-name/(.*).js. Plugin paths/scripts are separated by a comma and a single space.

    Here´s the list:

    /coming-soon/themes/default/js/script.js, /coming-soon/themes/default/bootstrap/js/bootstrap.js, /coming-soon/themes/default/js/modernizr.min.js, /woocommerce/assets/js/jquery-flot/jquery.flot.time.min.js, /woocommerce/assets/js/jquery-flot/jquery.flot.pie.min.js, /woocommerce/assets/js/jquery-flot/jquery.flot.min.js, /the-grid/backend/assets/js/admin-grid-list.js, /woocommerce-services/dist/woocommerce-services-banner.js, /woocommerce/assets/js/jquery-flot/jquery.flot.resize.min.js, /the-grid/includes/metabox/assets/js/tomb.js, /woocommerce/assets/js/admin/reports.min.js, /woocommerce/assets/js/jquery-flot/jquery.flot.stack.min.js, /cornerstone/assets/dist/js/site/cs-head.js, /contact-form-7/includes/js/scripts.js, /woocommerce/assets/js/js-cookie/js.cookie.min.js, /woocommerce/assets/js/frontend/add-to-cart.min.js, /tco-woo-checkout-editor/(.*)assets/js/tco_woo_scripts.js, /woocommerce/assets/js/frontend/woocommerce.min.js, /cornerstone/assets/dist/js/site/cs-body.js, /woocommerce/assets/js/frontend/cart-fragments.min.js, /woocommerce/assets/js/jquery-payment/jquery.payment.min.js, /woocommerce-gateway-paypal-powered-by-braintree/assets/js/frontend/wc-braintree.min.js, /woocommerce-gateway-paypal-powered-by-braintree/lib/skyverge/woocommerce/payment-gateway/assets/js/frontend/sv-wc-payment-gateway-payment-form.min.js, /the-grid/frontend/assets/js/the-grid.min.js, /woocommerce/assets/js/frontend/cart.min.js, /woocommerce/assets/js/frontend/address-i18n.min.js, /woocommerce/assets/js/frontend/country-select.min.js, /woocommerce-gateway-stripe/assets/js/stripe-apple-pay.min.js, /payments-gateway-amazon-woocommerce/assets/js/eh-https-amazon-pay.js, /payments-gateway-amazon-woocommerce/assets/js/eh-amazon-script.js, /woocommerce-gateway-stripe/assets/js/stripe-checkout.min.js, /woocommerce/assets/js/frontend/checkout.min.js
    AITpro Admin

    @ Ariell – This plugin script is triggering the Plugin Firewall error check since the file path contains: https in the file path naming convention:  /payments-gateway-amazon-woocommerce/assets/js/eh-https-amazon-pay.js. Do these steps below to fix the problem.

    1. Edit this whitelist rule /payments-gateway-amazon-woocommerce/assets/js/eh-https-amazon-pay.js and change the whitelist rule to this: /payments-gateway-amazon-woocommerce/assets/js/(.*).js.
    2. Click the Save Whitelist Options button.
    3. Click the Activate button to activate the Plugin Firewall.

Viewing 3 posts - 31 through 33 (of 33 total)
  • You must be logged in to reply to this topic.