Title: Cannot update firewall rules
Last modified: May 15, 2021

---

# Cannot update firewall rules

 *  Resolved [bellotaweb](https://wordpress.org/support/users/bellotaweb/)
 * (@bellotaweb)
 * [5 years ago](https://wordpress.org/support/topic/cannot-update-firewall-rules/)
 * Hi,
 * I hope you can help me with a problem I’m having…
 * I get the message “The last rules update for the Wordfence Web Application Firewall
   was unsuccessful. The last successful update check was 3 May 2021 03:59, so this
   site may be missing new rules added since then. You may wait for the next automatic
   attempt at 17 May 2021 04:11 or try to Manually Update by clicking the “Manually
   Refresh Rules” button below the Rules list.”
 * When I click “Manually Refresh Rules” nothing happens.
    Clicking “Restore Defaults”
   doesn’t do anything The “Export”, “Send Report By Email” or “Expand All Diagnostics”
   buttons on Tools/Diagnostics don’t work
 * I’ve deleted and reinstalled the plugin but this hasn’t changed anything – I 
   still see the message “The last successful update check was 3 May 2021 03:59”.
 * I would very much appreciate your assistance with this.
 * Thanks
 * Mike
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fcannot-update-firewall-rules%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Support [WFAdam](https://wordpress.org/support/users/wfadam/)
 * (@wfadam)
 * [5 years ago](https://wordpress.org/support/topic/cannot-update-firewall-rules/#post-14448226)
 * Hello [@bellotaweb](https://wordpress.org/support/users/bellotaweb/) and thanks
   for reaching out to us!
 * It sounds like something might be interfering with the JS that is running on 
   your site’s dashboard.
 * Could you try the follow to see if it works:
    Can you send a diagnostic report
   to **wftest @ wordfence . com**? You can find the link to do so at the top of
   the **Wordfence Tools > Diagnostics** page. Then click on **“Send Report by Email”**.
   Please add your forum username where indicated and _respond here after you have
   sent it._
 * If it doesn’t work, let me know.
 * Thanks again!
 *  Thread Starter [bellotaweb](https://wordpress.org/support/users/bellotaweb/)
 * (@bellotaweb)
 * [5 years ago](https://wordpress.org/support/topic/cannot-update-firewall-rules/#post-14448782)
 * Thanks for getting back Adam.
 * I’m unable to run the diagnostic report – clicking the ‘Send Report By Email’
   button just does nothing.
 * I’ve restored a backup copy of the live site to a different webserver and the
   problem persists. I have disabled all other plugins on the non-live site but 
   the problem persists. Happy to give you the IP address and admin access for the
   non-live site if this helps.
 * Cheers
 *  Plugin Support [WFAdam](https://wordpress.org/support/users/wfadam/)
 * (@wfadam)
 * [5 years ago](https://wordpress.org/support/topic/cannot-update-firewall-rules/#post-14449317)
 * [@bellotaweb](https://wordpress.org/support/users/bellotaweb/)
 * Can you email wftest @ wordfence . com with subject ” bellotaweb for WFADAM “.
 * Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Cannot update firewall rules’ is closed to new replies.

 * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865)
 * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordfence/)
 * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [WFAdam](https://wordpress.org/support/users/wfadam/)
 * Last activity: [5 years ago](https://wordpress.org/support/topic/cannot-update-firewall-rules/#post-14449317)
 * Status: resolved