Issue with Firewall Rule Updates

As described on my addition to this earlier topic;
topic/issue-with-manual-rule-update-and-server-state-warning/#post-18621710

I have had the same issue, it’s been on-going since early-mid August but as I was testing to open this Topic the issue seems to have magically ‘fixed itself’.
Support staff at the host advise they have not made any fixes or recent changes….

I have sent you another Diagnostics report in case you can detect differences or changes.

The symptoms were;

I have had Wordfence installed on many sites over many years, occasionally I would see the message about updating of the Firewall Rules failed. I would Manually Update and all would be fine.

However beginning in the middle of August all of my sites, about 20, on a hosting re-seller account have failed to update new rules. Manual update option also continues to fail.

I can’t find anything relevant in any log files.

The host support has checked and also cannot find any relevant errors logged.

I have other sites with similar WP configurations on another host and they continue to update as normal.

I use Wordfence Central dashboard, that is functioning, it finds all sites connected and I can start Scan from the dashboard.

In Wordfence Tools>Diagnostics this is shown as an error;
“Connecting back to this site via IPv6 (Not required; this may not be an issue on some sites. Click here to learn whether this is an issue)
wp_remote_post() test back to this server failed! Response was: cURL error 7: Couldn’t connect to server”

Deleting wflogs makes no difference; deactivating all other plugins make no difference.

But…after attempting ‘Manual Update’ and receiving the warning ‘No Rules were updated’ the Rules.php file in WFLogs does show the Modified date is changed to the current date and time and a file size (today 804.4kb)

I have not tried MySQLi change yet as my sites are years old and have had no recent config changes, curious why that wold need to be changed now?

I have sent a Diagnostics report to you.

As mentioned above this issue now appears to have resolved itself.

The page I need help with: [log in to see the link]