swedeman

You’ve solved it. All working now.

Thank you very much Scott.

Removed and confirmed then re-added. Same error.

Thanks Scott.

Finally got the site updated to PHP 7.2 but now seeing this error:

HTTP 401 received from Wordfence Central: {“errors”:[{“status”:401,”title”:”The server encountered an error processing your request.”,”detail”:”Token has expired”}]}

Thanks Scott.

Will try, however the customer account level on GoDaddy currently only allows 5.6.

Thanks Scott.

Done and resent.

Thank you Scott.

Has been sent.

Thanks Scott

Same here – CentOS

Thanks wfalaa for the response.

In CSF raise the PT_USERMEM setting.

We’ve also noticed a performance improvement by moving to PHP 7.

Don’t have a link to cPanel docs as this was accomplished after having submitted a support ticket. Have included the steps below in case it helps someone else or WF wants to add to its documentation.

As @wfyann mentioned – “It isn’t possible to use any kind of variable substitution for this” to add multiple domains in one shot. While potentially time consuming, after adding the directive to all DOMAIN.php-fpm.yaml files the implementation went smoothly.

For a single account, add the following directive to the cPanel userdata file that keeps some of the basic settings for the domain. This would be located at /var/cpanel/userdata/USERNAME/DOMAIN.php-fpm.yaml
-=-=-=-=-=-
php_admin_value[auto_prepend_file]: /path/to/file
-=-=-=-=-=-
Once this is added, rebuild the configuration files ( /scripts/php_fpm_config –rebuild ) and restart both Apache and the PHP-FPM services ( /scripts/restartsrv_apache_php_fpm; /scripts/restartsrv_apache ) Altering the PHP-FPM settings via WHM or cPanel would overwrite this file and remove the custom content. This should be preserved through other configuration rebuilds.

Thanks @wfyann for the response.

Did find a solution by consulting with cPanel tech support although it did require a fair amount of configuration.

Perhaps as WF continues to evolve and the documentation becomes more detailed, these types of multi-domain requirements will be addressed.

Thanks Josh.

Any tips for setting relative links in the WP interface?

Images added to a post seem to reject editing of the URL.

Thanks Mark for this update.

Was tearing my last remaining hair out resetting the default choices on multiple sites.

@rcuringt

Doing a search will bring up numerous resources to implement blocking using .htaccess files assuming you’re on an Apache server.

Just be aware that blocking users via IP address will require updating the allowed IPs when they change.

You may prefer to password protect access to wp-login.php and wp-admin instead.

One caveat I believe Mark has mentioned before is allowing access to admin-ajax.php when using IP blocking or password protection.

Agree with @montanagrafix that having this ability in WF would be quite useful.

Simplest way by IP (not in Wordfence) is to use .htaccess files.