Title: Config File Locking
Last modified: September 17, 2018

---

# Config File Locking

 *  Resolved [notanonymous](https://wordpress.org/support/users/notanonymous/)
 * (@notanonymous)
 * [7 years, 8 months ago](https://wordpress.org/support/topic/config-file-locking/)
 * I’m using Azure’s Linux web app hosting for a site using the latest version of
   the Wordfence plugin (7.1.12). I’m getting sporadic errors that php can’t read/
   write to some of the config files. Examples:
 * [17-Sep-2018 22:34:06 UTC] Unable to open /home/site/wwwroot/wp-content/wflogs/
   config-transient.php for reading and writing.
    [17-Sep-2018 22:34:06 UTC] Unable
   to open /home/site/wwwroot/wp-content/wflogs/config-transient.php for reading
   and writing. [17-Sep-2018 22:34:21 UTC] Unable to open /home/site/wwwroot/wp-
   content/wflogs/config-synced.php for reading and writing.
 * But its able to read/write to them some times, just inconsistently. Has anyone
   run into this issue running either Azure’s linux hosting or other docker container
   environment. I’m working with Azure support as well, but thought I’d check here
   too.

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

 *  [wfalaa](https://wordpress.org/support/users/wfalaa/)
 * (@wfalaa)
 * [7 years, 8 months ago](https://wordpress.org/support/topic/config-file-locking/#post-10725029)
 * Hi [@notanonymous](https://wordpress.org/support/users/notanonymous/)
 * On some servers, we have seen that certain scripts might delete “wflogs” directory
   thinking of it as a potential threat (false positive), as a result the folder
   will be regenerated again, it might be that when it’s regenerated it will be 
   owned by a different user than the user your web server is running on?
 * I suggest manually deleting this folder and recheck the generated copy to make
   sure it’s owned by the server user that has read/write permissions.
 * Thanks.
 *  [wfasa](https://wordpress.org/support/users/wfasa/)
 * (@wfasa)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/config-file-locking/#post-10787818)
 * Hi [@notanonymous](https://wordpress.org/support/users/notanonymous/),
    Since
   we haven’t heard from you for a while I’m going to go ahead and resolve this 
   thread. You are welcome to create a new one at any time!
 *  Thread Starter [notanonymous](https://wordpress.org/support/users/notanonymous/)
 * (@notanonymous)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/config-file-locking/#post-10789423)
 * Thanks. To follow up in case anyone else comes across this, it seems to be an
   issue with our hosting environment. It’s running in a container with a virtual
   file system and I think it’s just not able to keep up with the read/write requests
   so things get locked. Engineers are investigating.
 *  [wfasa](https://wordpress.org/support/users/wfasa/)
 * (@wfasa)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/config-file-locking/#post-10792578)
 * That’s very helpful thanks for sharing [@notanonymous](https://wordpress.org/support/users/notanonymous/)!

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

The topic ‘Config File Locking’ 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/)

 * 4 replies
 * 3 participants
 * Last reply from: [wfasa](https://wordpress.org/support/users/wfasa/)
 * Last activity: [7 years, 7 months ago](https://wordpress.org/support/topic/config-file-locking/#post-10792578)
 * Status: resolved