jetpack might be blocking zapier from authorizing my account for integration?

  • Unknown's avatar

    I checked with Zapier to get help as to why my account set-up for WordPress integration with Zapier kept failing, and they suggested that ‘Especially if you’re using the site theme called ‘Jetpack’, it can be helpful to double check any security settings to see if they are blocking integrations or black-listing specific IP addresses. If you think this might be the case, you can disable Jetpack’s ‘Protect’ to allow Zapier’s IP address to pass through.’

    Has anyone experience this? How do I turn protect off, and what are the potential consequences?

    The blog I need help with is: (visible only to logged in users)

  • Hi,

    It looks like your website is hosted with Cogeco Peer 1. 
We can only assist with WordPress.com hosted sites on this forum.

    You can ask for support in the WordPress.org forums: 
    https://wordpress.org/support/forums/

    There is a jetpack plugin .org support forum here:
    https://wordpress.org/support/plugin/jetpack

    The difference between .ORG and .COM is explained here:

    WordPress.com vs. WordPress.org

    Hope this helps :)

  • Unknown's avatar

    hm, not sure why it looks like that. I am a business plan wordpress.com customer.

  • Unknown's avatar
  • Hi,

    You can be on a WordPress.com Business plan and still have your website hosted by a third party: shttps://en.support.wordpress.com/domains/all-about-domains/

    Since you’re on the Business plan you also have access to direct Live Chat Support if you would prefer: https://en.support.wordpress.com/live-chat/

    Hope this helps :)

  • Hi there,

    Jetpack is not a theme, as the folks at Zapier apparently told you. It’s a plugin that adds a number of WordPress.com features to your site, including security protection, malware scanning, spam filters and backups.

    But they are correct that Jetpack’s security features are blocking the connection. This happens when Zapier tries to access your site too many times with incorrect credentials, so the security feature is working as it should, and the problem is the way which Zapier retries when a connection attempt fails. We reached out to them about this a few months ago.

    The error is coming from the Jetpack Protect module, which is a security plugin that comes with your site. We definitely do not recommend completely disabling this feature as Zapier advised you to do.

    Could you please try disabling and then re-enabling the module to see if that helps?

    Click on My Site ->Settings ->Security and disable the option that says Prevent and block malicious login attempts and save the setting.

    Turn back on the same setting and save again.

    If you open the panel, you’ll also see an IP whitelist, where you can add any IPs you like – these you’ll need to get directly from Zapier.

    After doing that, please let us know if your Zapier integration works again.

    For more help with this, please contact us via live chat at https://wordpress.com/help/contact as the volunteers in this forum do not have access to all the tools and information needed to effectively support the advanced features of your Business Plan site.


    @catkiinson

    You can be on a WordPress.com Business plan and still have your website hosted by a third party

    That is not accurate. A domain can be registered with WordPress.com and pointed to another hosting provider, but if the domain’s name servers is pointed to us and the site is on our Business Plan, then we are the host.

    You won’t see the WordPress.com admin bar on that site, as WordPress.com Business Plan sites with plugins work differently from regular WordPress.com sites, but the domain’s name servers are pointed to us and we are definitely hosting this site.

    In future, please tag threads for staff if it involves a WordPress.com Business Plan site,.

  • Thanks for the great info, @kokkieh :) will do

  • The topic ‘jetpack might be blocking zapier from authorizing my account for integration?’ is closed to new replies.