Hi @wdoutjah, thanks for your message.
Is the full error message you mention in the title related to wordfence-waf.php? I wouldn’t imagine not finding this file would max out resources on its own, but this should only pose an issue if you’ve either migrated or restored a site from a location where the path to that file is different to your live site.
I’d try to remove the auto_prepend_file = '/path/to/wordfence-waf.php' line from .htaccess or .user.ini (whichever your site uses) manually by downloading/editing/reuploading those files or using the file manager provided with your host’s control panel. The site should then load, returning Wordfence’s firewall to “Basic Protection”. Once your site loads again instead of giving you errors, you can re-optimize the firewall using our wizard, which will reflect the correct path.
Thanks,
Peter.
Its a fresh installation. No plugins or whatsoever
This is the full error
PHP Fatal error: Failed opening required ‘/var/home/driftsto/public_html/wordfence-waf.php’ (include_path=’.:/opt/alt/php80/usr/share/pear:/opt/alt/php80/usr/share/php:/usr/share/pear:/usr/share/php’) in Unknown on line 0
These are the only codes on the htaccess
Block the include-only files.
RewriteEngine On RewriteBase / RewriteRule ^wp-admin/includes/ – [F,L] RewriteRule !^wp-includes/ – [S=3] RewriteRule ^wp-includes/[^/]+.php$ – [F,L] RewriteRule ^wp-includes/js/tinymce/langs/.+.php – [F,L] RewriteRule ^wp-includes/theme-compat/ – [F,L]
order allow,deny deny from all require all denied BEGIN WordPress
RewriteEngine On RewriteBase / RewriteRule ^index.php$ – [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] END WordPress
