If I just reinstall the plugin, does everything get fixed?

Almost always. wp plugin install wordfence --activate regenerates wordfence-waf.php, the wp-config.php defines, and the wflogs directory in one step. Manual repair is for when you can't reach wp-admin to install plugins (a fatal error on every page) — once wp-admin loads, prefer the reinstall.

Why does the article walk through downloading the file separately?

For two recovery scenarios. (1) You're on shared hosting where WP-CLI isn't available and the site can't reach wp-admin. (2) The plugin install fails mid-way and you need to verify just the WAF file in isolation. The plain-file path is slower but works in the cases where the high-level repair doesn't.

Mode 644 and owner = web-server user — anything special?

Mode 0644 reads as: owner can read+write, group can read, world can read. Web server (PHP) needs read only, and it usually runs as www-data (Debian/Ubuntu Apache, most Nginx setups) or nginx (RHEL Nginx). The owner can stay www-data; the important part is that the web server user is at least in the group with read access.

wordfence-waf.php keeps disappearing — what's deleting it?

Three usual culprits: (a) a malware-cleanup tool quarantining it as suspicious, (b) a host-level security scanner removing what it thinks is shell-like code, (c) a botched WordPress restore from an older backup. Check the server's audit log for who touches the file, then disable the offender or whitelist the path.

Fixing "wordfence-waf.php" Issues — Download & Check File Permissions

If your WordPress site is showing errors related to wordfence-waf.php, the cause is one of three things: the file is missing, the wp-config.php define points at the wrong path, or file permissions block PHP from reading it. The other three WAF-error articles cover specific symptoms — see Fixing wordfence-waf.php Fatal Error, Fixing "wordfence-waf.php Not Found", and Fixing "Failed Opening Required wordfence-waf.php". For the manual recreate procedure, How to Recreate wordfence-waf.php Manually in WordPress; for the data side, Understanding the wflogs Folder.

Fixing Wordfence waf.php File Permissions — Wordfence WAF — the file, its permissions, and the wp-config wiring.

Download wordfence-waf.php

If wordfence-waf.php is missing, you can manually download or recreate it.

Download from Wordfence Plugin (Fresh Install)

Go to Wordfence Official Plugin.
Download the latest version.
Extract the .zip file.
Locate wordfence-waf.php inside the wordfence directory.
Upload it to your server in public_html/ using FTP, cPanel, or SSH.

Restore or Manually Create wordfence-waf.php

If you can't download the file, you can create it manually.

Create wordfence-waf.php

Run:

nano /home/user/public_html/wordfence-waf.php

or use cPanel File Manager > Click Create File > Name it wordfence-waf.php.

Add the Following Code

<?php
// Wordfence Web Application Firewall
if (file_exists(__DIR__ . '/wp-content/wflogs/bootstrap.php')) {
    include_once __DIR__ . '/wp-content/wflogs/bootstrap.php';
}

Save & Exit (CTRL + X, then Y, then ENTER).

Check & Fix File & Folder Permissions

After restoring or recreating wordfence-waf.php, ensure it has the correct permissions.

Set Correct File Permissions

chmod 644 /home/user/public_html/wordfence-waf.php
chown www-data:www-data /home/user/public_html/wordfence-waf.php  # For Apache
chown nginx:nginx /home/user/public_html/wordfence-waf.php        # For Nginx

Check Permissions on wflogs Directory

chmod -R 755 /home/user/public_html/wp-content/wflogs
chown -R www-data:www-data /home/user/public_html/wp-content/wflogs

Restart Apache/Nginx

sudo systemctl restart apache2

sudo systemctl restart nginx

Verify & Update wp-config.php

If wordfence-waf.php isn't loading, ensure the correct path is set in wp-config.php.

Open wp-config.php:

nano /home/user/public_html/wp-config.php

Check if this line exists:

define("WFWAF_LOG_PATH", '/home/user/public_html/wp-content/wflogs/');
if (file_exists(__DIR__ . '/wordfence-waf.php')) {
    include_once __DIR__ . '/wordfence-waf.php';
}

If missing, add it before:

/* That's all, stop editing! Happy publishing. */

Save and exit.

Reload your website and check if the error is resolved.

Reinstall Wordfence (If Necessary)

If the issue persists, reinstall Wordfence:

wp plugin deactivate wordfence
wp plugin delete wordfence
wp plugin install wordfence --activate

This will regenerate wordfence-waf.php automatically.

Summary of Fixes

Issue	Fix
Missing wordfence-waf.php	Download from Wordfence or manually create it
Incorrect file permissions	Set `chmod 644` and `chown www-data:www-data`
Permissions issue on wflogs/	Set `chmod -R 755` and `chown -R www-data:www-data`
Wrong wp-config.php settings	Add `define("WFWAF_LOG_PATH", ...)`
Wordfence corrupted	Reinstall with `wp plugin install wordfence`

Now Wordfence WAF should be working correctly!