Title: Cannot Update rules
Last modified: February 3, 2018

---

# Cannot Update rules

 *  Resolved [alan555](https://wordpress.org/support/users/alan555/)
 * (@alan555)
 * [8 years, 4 months ago](https://wordpress.org/support/topic/cannot-update-rules/)
 * WF version Version 7.0.2
 * Trying to update Firewall rules fails, either by pull down rules or manual update.
   The error is “No rules were updated. Please verify you have permissions to write
   to the /wp-content/wflogs directory.”
 * The directory has always been writable and was OK until the latest update. I 
   have checked the Dir folder and it has 0755 permission.
 * Files in the folder – Attack-data, IPS and Config are 0660 and rules is 0664

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

 *  [wfyann](https://wordpress.org/support/users/wfyann/)
 * (@wfyann)
 * [8 years, 4 months ago](https://wordpress.org/support/topic/cannot-update-rules/#post-9937168)
 * Hi [@alan555](https://wordpress.org/support/users/alan555/),
 * Can you confirm that the owner of the directory/files is the user the web server
   runs as?
 * Could you also please go to “_Wordfence –> Tools –> Diagnostics_” and make sure
   that all checks in the “_Filesystem_“, “_Wordfence Config_” and “_MySQL_” sections
   read OK.
 *  Thread Starter [alan555](https://wordpress.org/support/users/alan555/)
 * (@alan555)
 * [8 years, 4 months ago](https://wordpress.org/support/topic/cannot-update-rules/#post-9937178)
 * Hi wfyann.
 * The user in WordPress is also the account holder on the server (shared hosting)
 * I have just run the diagnostic and everything is fine including the file section
   where it shows all files are readable and writeable in the required directories.
 * I have asked the tech support to look at this problem and wil report back here
   if they find a solution.
 *  [wfyann](https://wordpress.org/support/users/wfyann/)
 * (@wfyann)
 * [8 years, 4 months ago](https://wordpress.org/support/topic/cannot-update-rules/#post-9937191)
 * Hi [@alan555](https://wordpress.org/support/users/alan555/),
 * Have you tried deleting the “_wflogs_” directory? –it’ll be automatically recreated
   when someone visits your site.
 *  Thread Starter [alan555](https://wordpress.org/support/users/alan555/)
 * (@alan555)
 * [8 years, 4 months ago](https://wordpress.org/support/topic/cannot-update-rules/#post-9937196)
 * Just tried that – no change. BTW I have 8 websites running on the shared server
   and all have the same problem.
 *  Thread Starter [alan555](https://wordpress.org/support/users/alan555/)
 * (@alan555)
 * [8 years, 4 months ago](https://wordpress.org/support/topic/cannot-update-rules/#post-9938289)
 * Tech Support can find no reason why the plugin will not update.
 * I did notice that the files in the wflogs dir have different permisisons…
 * wafRules.rules – 0644
    rules.php – 0664 the others – 0660
 * Are these correct?
 *  Thread Starter [alan555](https://wordpress.org/support/users/alan555/)
 * (@alan555)
 * [8 years, 4 months ago](https://wordpress.org/support/topic/cannot-update-rules/#post-9939197)
 * This is now sorted. The problem was that the IP address used for the WF updates
   had been grey listed by the hosting companies security software.

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

The topic ‘Cannot Update 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/)

 * 6 replies
 * 2 participants
 * Last reply from: [alan555](https://wordpress.org/support/users/alan555/)
 * Last activity: [8 years, 4 months ago](https://wordpress.org/support/topic/cannot-update-rules/#post-9939197)
 * Status: resolved