Please ask them to be more specific. It’s their plugin so they should know what is being blocked. Once we know, we can unblock it, if it is indeed something caused by Wordfence.
Thanks,
Mark.
Plugin Support
wfphil
(@wfphil)
Hi @diamich
I am following up on behalf of Mark.
This is likely due to the firewall seeing legitimate Blog2Social plugin requests as being potentially malicious and blocking them. You can either whitelist these requests via the Learning Mode feature or from the Tools >> Live Traffic tool page. Both whitelisting methods are described in our instructions in the link below:
https://www.wordfence.com/help/firewall/learning-mode/
Thank you for the follow up. I put Wordfence in learning mode and scheduled a post. Once again the post failed and nothing was triggered in Learning mode. I’m guessing that if something was already in the firewall rules it would have been block automatically. I looked in the Live Traffic and there were no entries at the time of the scheduled post. Sadly, I’m not getting any assistance from B2S to help figure out what it is that could be blocked.
Hello @diamich,
We already wrote you an email. Therefore, we would like to ask you to take a look in your spam folder to see whether it might have landed there. We will gladly continue to support you with your request.
Plugin Support
wfphil
(@wfphil)
Hi @diamich
It certainly sounds as though Wordfence is not involved if the firewall is in Learning Mode and no blocks related to Blog2Social plugin requests were seen in the Live Traffic page feed.
To completely rule out Wordfence then you can manually disable Wordfence by renaming the Wordfence plugin directory as below:
~/wp-content/plugins/wordfence-disabled
If you still have the same problem then Wordfence can’t be involved.
To enable Wordfence again then rename the Wordfence plugin directory back to:
~/wp-content/plugins/wordfence