disables Cursor AI

Hi @davecotter, thanks for reaching out.

It is generally not recommended to add any IP to Wordfence > All Options > Allowlisted IP addresses that bypass all rules unless absolutely necessary, such as when an IP from your host is being consistently blocked. Wordfence will never check anything that comes from them.

Instead it’d be preferable to find the rule or setting that is causing the Cursor AI connection to be blocked. Having Learning Mode on for a short period while you try to use Cursor AI would be the easiest first step. If it works, return the firewall to “Enabled and Protecting” afterwards.

If you still see problems when Learning Mode is turned off, visit the Live Traffic page immediately afterwards. If there is a recent block there, check the reason after expanding the entry with the eye icon in the corner. You may find a specific firewall rule or Wordfence setting stated here after expanding the entry. The reason is shown in red text.

Feel free to paste that reason here if you’re unable to manually allowlist it successfully using the “ADD PARAM TO FIREWALL ALLOWLIST” button on the Live Traffic page.

Let us know what you find out,
Peter.

Hi @davecotter, thanks for the extra information.

Yes, Live Traffic will be the main way of finding out whether Wordfence is blocking the calls Cursor AI is making as they’ll be logged with a reason. There’s often a button there that can allowlist future requests instead of blocking them, but sometimes firewall rules can be the cause. Make sure to read the help docs linked in my last post if you need any help understanding Live Traffic’s features and what the page is telling you.

It was a reasonably good test to have already turned off Wordfence and see Cursor AI working again, but sometimes plugin conflicts can make it appear like disabling Wordfence was the solution. For example, if Wordfence and Cursor AI work together when all other plugins are disabled, you may need to reenable your others one-by-one to see what causes the conflict.

Thanks again,
Peter.

Yes, sorry, that is strange as a complete Wordfence removal along with its auto_prepend_file value and database tables means it doesn’t have anything left to even affect the site or make blocks going forward. Unfortunately, that helps me understand the steps to recreate but doesn’t seem consistent with an issue I’ve seen before to diagnose it. I trust that you fully removed it from your description but we do have a list of things to check for here: https://www.wordfence.com/help/advanced/remove-or-reset/#remove-or-reset

To send us a diagnostic report so we could potentially check for why that issue might occur, you’d need to reinstall Wordfence. If you do choose to do that, I’ll leave the instructions here. Send one to wftest @ wordfence . com by using the link at the top of the Wordfence > Tools > Diagnostics, followed by “Send Report by Email”. Please add your forum username where indicated and respond to us here after you have sent it.

NOTE: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email

If Wordfence wasn’t ever logging any blocks in Live Traffic and it continues after plugin removal it does suggest a server firewall, or other security product like Cloudflare might be involved but that’d need more investigation.

Many thanks,
Peter.