Fix a Blocked WooCommerce Connection

Some hosts protect WordPress with a firewall, CDN, or bot-protection service that mistakes Quick2Print's signed requests for unwanted automated traffic. When that happens, Sync Health shows a warning that your hosting appears to be blocking Quick2Print.

Your store data is safe, and nothing is broken inside WordPress. In most cases products keep syncing through the connector's durable polling — updates just arrive more slowly, and on a very quiet site they can pause until the site next receives a visitor. Unblocking Quick2Print restores fast, reliable updates.

What is being blocked

Quick2Print contacts your WordPress site in three harmless ways. All of them are signed or carry no data at all, and none of them can change anything without your Store's private key:

1. A signed wake request to /wp-json/quick2print/v1/wake telling the connector work is ready.
2. A signed fallback request to /wp-admin/admin-ajax.php when the first route is rejected.
3. A keepalive page visit that simply lets WordPress run its scheduled tasks.

The exact addresses and identity for your environment are shown in the warning on the Sync Health page, and are published at /.well-known/quick2print-connector on your Quick2Print application domain.

Fix it yourself with an allowlist

Work through whichever of these applies to your site. After each change, open Sync Health in Quick2Print and press Refresh, or use Test connector in WordPress under WooCommerce → Quick2Print, to check whether the state has become instant.

1. Security or firewall plugins in WordPress

If you use a security plugin (for example Wordfence, iThemes/Solid Security, All In One WP Security, CloudFilt, or similar):

• Add the Quick2Print IP addresses from the Sync Health warning to the plugin's IP allowlist or "trusted IPs".
• If the plugin has a user-agent allowlist, add the Quick2Print user agent shown in the warning.
• If the plugin can restrict the WordPress REST API, make sure quick2print/v1 routes stay available to visitors that are not logged in — the wake carries its own cryptographic signature instead of a WordPress login.

2. CDN or bot protection in front of your site

If your site sits behind a CDN or bot-protection layer (for example Cloudflare or your host's built-in protection):

• Create a firewall/allow rule for the Quick2Print IP addresses.
• Make sure the rule allows POST requests to /wp-json/quick2print/v1/wake and /wp-admin/admin-ajax.php — some protections block POST while allowing normal page views.
• Avoid presenting JavaScript challenges ("checking your browser" pages) to those addresses: a server cannot solve a browser challenge.

3. Ask your hosting provider

If you cannot find the setting, or the block happens at the server level, send your host a short request. You can copy this template and fill in the values from the Sync Health warning:

Hi — my store uses Quick2Print, a service that syncs products with my WooCommerce site using signed requests. Your firewall or bot protection appears to be blocking it. Could you please allow the following traffic to my site?

• Source IP address(es): (from the Sync Health warning)
• User agent: (from the Sync Health warning)
• Requests: POST /wp-json/quick2print/v1/wake and POST /wp-admin/admin-ajax.php, plus normal page views

The service publishes its identity, keys, and traffic policy at the /.well-known/quick2print-connector address of my Quick2Print application, so you can verify it. Thank you!

How to confirm it is fixed

• Sync Health shows the Woo connection as Ready with verified instant wake, and the hosting warning disappears.
• In WordPress, WooCommerce → Quick2Print → Test connector succeeds and the connection health shows a recent signed wake.

If your host cannot allowlist the addresses, the connector continues working through durable polling — jobs still complete, with roughly a minute of extra delay while the site has traffic.