How to allow IFTTT recipes

Hi airsid can you elaborate a bit more what your problem is. What is IFTTT recipes?

Thank you

Hello,

The recipe is this one: Post by email to wordpress.

When the plugin is on, the wordpress ifttt channel can’t be active.
The following error message appear: “Unable to verify WordPress credentials. Please try again.”

I had to deactivate the plugin to have wordpress ifttt channel activate and the recipe working.

Thank you now I know what IFTTT means ??

What is the error message you see if any? Can you check your log files and report back? Can you enable debug mode on your website?

Try to disable all firewall features and see if the issue is resolved. If the issue is resolved enable one by one the options and at the same time testing each option to see which one is triggering the issue.

Have you got any of the features under Miscellaneous enabled?

Sorry we must of have crossed paths :). I now know the error message from your reply above. Can you carry the other options for me.

Thank you

Ok so it is working when “WordPress Pingback Vulnerability Protection” firewall option is unchecked ??

Thanks.
But does it mean my site is less protected as this option is a basic one ?

Hi, I am glad you found what was causing the issue. In regards to your comment.

But does it mean my site is less protected as this option is a basic one ?

To some degree you could start getting attempts at login into your website but if you have either option from the Brute Force enabled i.e. Rename Login or Cookie Based Brute Force Prevention will stop any attempts.

This is explanation the developers provide about the feature you disabled.

This setting will add a directive in your .htaccess to disable access to the WordPress xmlrpc.php file which is responsible for the XML-RPC functionality such as pingbacks in WordPress.

Hackers can exploit various pingback vulnerabilities in the WordPress XML-RPC API in a number of ways such as:

1) Denial of Service (DoS) attacks

2) Hacking internal routers.

3) Scanning ports in internal networks to get info from various hosts.

Apart from the security protection benefit, this feature may also help reduce load on your server, particularly if your site currently has a lot of unwanted traffic hitting the XML-RPC API on your installation.

NOTE: You should only enable this feature if you are not currently using the XML-RPC functionality on your WordPress installation.

Ultimately you could share this information with the IFTTT developers.

If your issue is resolved can you mark this support thread as resolved.

Thank you

Thank you for all explanations.
As i have many users using my site I can’t enable “Cookie Based Brute Force Prevention” option which block users access to the login page.
But I’ve enabled “Rename Login” option so it should be ok as you told me.

If so, thank you for your very quick and useful support !! ??