Title: API Connectivity Issue
Last modified: December 15, 2016

---

# API Connectivity Issue

 *  Resolved [Mr Puck](https://wordpress.org/support/users/puck1337/)
 * (@puck1337)
 * [9 years, 6 months ago](https://wordpress.org/support/topic/api-connectivity-issue/)
 * So Im using GoDaddy shared WordPress hosting, using the latest version of Ithemes
   security, woocommerce and tryingg to get ThePrintful API to connect. I have determine
   that Ithemes causing an issue getting it to connect. If I disable security it
   works. If I disable brute force and long URL it seems to be somewhat work but
   not completely. Anyone have any ideas or suggestions?

Viewing 3 replies - 1 through 3 (of 3 total)

 *  [Luke Cavanagh](https://wordpress.org/support/users/lukecavanagh/)
 * (@lukecavanagh)
 * [9 years, 6 months ago](https://wordpress.org/support/topic/api-connectivity-issue/#post-8558054)
 * [@puck1337](https://wordpress.org/support/users/puck1337/)
 * What error message shows?
 * [https://www.theprintful.com/faq/woocommerce/90-error-when-connecting-woocommerce-to-printful](https://www.theprintful.com/faq/woocommerce/90-error-when-connecting-woocommerce-to-printful)
 *  Thread Starter [Mr Puck](https://wordpress.org/support/users/puck1337/)
 * (@puck1337)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/api-connectivity-issue/#post-8561890)
 * ![Printful Error](https://drive.google.com/file/d/0B3YO1rBTPx-ITkNGNkV3MmdEMWc/
   view?usp=sharing)
 * So that was the error I was getting. As for what’s going on if I disable Brute
   Force and the Long URL protection, it at least gives me the approve / deny option,
   but once I approve it, it fails with a different error. As I’m importing products
   right now I’d really prefer not to enable everything as I don’t want to have 
   to start over – I think I’d be fine once I disable it again, but kind of nervous
   as I’ve been dealing with this for a week and losing money every time my store
   is down – or potential money anyways.
 * I guess my attempt here was someone who has had this issue and was able to resolve
   it. I spoke with ThePrintful and all they keep telling me is “my host has to 
   white list their IP” – which will not happen as it’s a shared host so they refuse
   to put other sites at risk. I purchased cPanel and started importing my site (
   after 9 re-installs I gave up and started installing everything manually) – all
   of a sudden my new store stopped working. That’s when I realized it was iThemes
   Security causing the issue.
    -  This reply was modified 9 years, 5 months ago by [Mr Puck](https://wordpress.org/support/users/puck1337/).
 *  Thread Starter [Mr Puck](https://wordpress.org/support/users/puck1337/)
 * (@puck1337)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/api-connectivity-issue/#post-8561899)
 * Note sure why the image isn’t showing, but if you open image in new window it
   works. New to the site so my apologies.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘API Connectivity Issue’ is closed to new replies.

 * ![](https://ps.w.org/better-wp-security/assets/icon.svg?rev=3529351)
 * [Kadence Security – Password, Two Factor Authentication, and Brute Force Protection](https://wordpress.org/plugins/better-wp-security/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/better-wp-security/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/better-wp-security/)
 * [Active Topics](https://wordpress.org/support/plugin/better-wp-security/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/better-wp-security/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/better-wp-security/reviews/)

## Tags

 * [iThemes Security](https://wordpress.org/support/topic-tag/ithemes-security/)
 * [printful](https://wordpress.org/support/topic-tag/printful/)

 * 3 replies
 * 2 participants
 * Last reply from: [Mr Puck](https://wordpress.org/support/users/puck1337/)
 * Last activity: [9 years, 5 months ago](https://wordpress.org/support/topic/api-connectivity-issue/#post-8561899)
 * Status: resolved