Thanks for sharing your thoughts about Wordfence.
As we told you in the tickets you opened, Premium support is clearly outlined in our Terms of Service, which everyone agrees to when they install the plugin. As Phil told you, Premium support is available during business hours only. The hours, listed in the ToS and various places on the website, are 9am-8pm ET, 6am-5pm PT and 2pm-1am UTC/GMT excluding weekends and holidays. If you need 24/7/365 support a Response license is likely more what you need.
As to your issue you were having, the error you reported to us was that you were seeing remote post tests back to the site were failing. Basically, meaning the site could not connect back to itself. This can affect cron jobs and scheduled tasks like scans. The error that the server sent back to itself was this:
HTTP/1.1 403 Forbidden
date: Mon, 01 May 2023 11:26:59 GMT
server: Apache
content-length: 199
content-type: text/html; charset=iso-8859-1
x-service-level: standard
x-backend-server: web14.hosting.stackcp.net
x-via: LHR1
connection: close
403 Forbidden Forbidden
You don’t have permission to access this resource.
As Scott and Phil said to you, this is not a Wordfence generated block page. It is the kind of block page your server displays for its blocks and can be due to code in .htaccess or a mod_security rule or even a file permissions issue. Wordfence has nothing to do with those. You responded at one point, confirming that the hosting provider had said “It looks like this is hitting one of our mod_sec rules due to a missing referrer.” The hosting provider (and you) are the only people that can fix that sort of thing. No one else can.
I haven’t seen any requests regarding your sitemap I can’t provide any details since you didn’t provide any.
As the last reported scan we see was done on July 19th I am assuming that you have chosen to use another security provider. We wish you well in whichever one you chose.
Mia
