BizPrint webhook test connection fails: Status updates stopped after earlier failures

Cause: BizPrint could not deliver a status update to the webhook, even after trying again. After that, it stops sending updates to the application. It does not start again by itself. Updates start again only when you change the Webhook URL or run a test that succeeds. Fix: Fix the cause, then test again: Fix the cause, using the other entries on this page. Open the application in the dashboard. Click Perform test connection, under Webhook Info. Updates start again when the dashboard shows Successfully connected with webhook server. Updates that were missed while the webhook was stopped are not sent again.

BizPrint webhook test connection fails: The Webhook URL is missing or wrong

Cause: The application’s Webhook URL is empty, mistyped, or out of date, for example after your store moved to a new web address. Fix: For a WooCommerce store, copy the address from the plugin: Go to WooCommerce > Print Manager in WordPress. Open the Application tab. Click inside the Webhook Url field. The plugin copies the address and shows “Copied”. Sign in to the BizPrint dashboard in another tab. Click Applications in the menu. Click your store’s application. Delete everything in the Webhook URL field. Paste the address you copied. Click Update next to the field. BizPrint tests the new address straight away. Click Perform test connection to see the result. For your own app, enter the full address of the endpoint that receives BizPrint webhooks. See Receive print job updates from BizPrint with webhooks.

BizPrint webhook test connection fails: The keys in WordPress do not match the application

Cause: Your store only accepts webhook messages for the application whose keys are saved in the plugin. The keys in WordPress belong to a different application, or were never saved. The Webhook URL must be set in the same application whose keys your store uses. Fix: Make sure you are testing the application whose keys are in WordPress: Go to WooCommerce > Print Manager in WordPress. Open the Application tab. Sign in to the BizPrint dashboard in another tab. Click Applications in the menu. Click your store’s application. Compare the Public Key in WordPress with the Public Key on the application’s page. Copy both keys from the right application into the plugin, if the keys differ. See Connect the BizPrint plugin for WooCommerce to your BizPrint account. Click Save Changes in WordPress. Click Perform test connection again. Never email the Secret Key or paste it into a chat.

BizPrint webhook test connection fails: BizPrint cannot reach your website

Cause: Your store or app must be online and reachable from the internet at its Webhook URL for BizPrint to deliver messages. It may be offline, in maintenance mode, protected by a password (common on staging sites), or something on your website or hosting may be refusing the requests. Fix: Make sure your website can be reached: Open your website from a phone on mobile data, without signing in. Check that it opens normally. Take it out of maintenance mode, if it is in it. Contact your hosting provider or BizPrint support, if you are not sure why it cannot be reached. Click Perform test connection again. Your store or app must be able to receive messages from the internet at its webhook address. Do not turn off a firewall or any other security feature to try to fix this.

BizPrint webhook test connection fails: The application uses the Legacy API

Cause: Webhooks work only with the REST API. Applications that use the older Legacy API do not have them. Fix: Move to the REST API: Move your store to the REST API. See Move the BizPrint plugin for WooCommerce from the Legacy API to the REST API. When you migrate from the plugin, it sends its webhook address to BizPrint for you. Run the test. See Test the webhook connection for a BizPrint application.

BizPrint webhook test connection fails

Q: BizPrint webhook test connection fails: Your website’s clock is wrong

Cause: Your store accepts webhook messages only for a short time after BizPrint sends them. If your website’s server clock is set ahead of the real time, your store treats every message as too old and refuses it. Fix: Get the clock corrected: Ask your hosting provider to check that your website’s server uses the correct time. Click Perform test connection again. Contact BizPrint support, if it still fails.

This page helps when the webhook test for a BizPrint application fails with Error connection to webhook server., or when a red warning triangle appears next to an application in the BizPrint dashboard. It is for WooCommerce store owners who use the BizPrint plugin for WooCommerce, and for developers whose own app receives BizPrint webhooks.

A webhook is a web address on your store or app. BizPrint sends a message to it when a print job changes status, for example when it finishes printing. A failing webhook does not stop printing: your printers keep printing new jobs. Only the job status updates to your store or app stop. So do not reprint or retry any job because of a webhook error. Check the printer and the job’s status in the dashboard instead.

To run the test, see Test the webhook connection for a BizPrint application. When the test fails, the dashboard may show a short technical reason before Error connection to webhook server., such as a message that ends with a status code. The entries on this page say which reason usually goes with which cause.

Status updates stopped after earlier failures

Symptom: A red warning triangle shows next to the application in the My Applications list or on the Applications tile of the dashboard home page, and your store or app no longer gets job status updates.

Cause: BizPrint could not deliver a status update to the webhook, even after trying again. After that, it stops sending updates to the application. It does not start again by itself. Updates start again only when you change the Webhook URL or run a test that succeeds.

Fix: Fix the cause, then test again:

Fix the cause, using the other entries on this page.
Open the application in the dashboard.
Click Perform test connection, under Webhook Info.

Updates start again when the dashboard shows Successfully connected with webhook server. Updates that were missed while the webhook was stopped are not sent again.

The Webhook URL is missing or wrong

Symptom: The test fails and the reason says Webhook URL has not specified, or ends with status code 404, or the address in Webhook URL is not your store’s current address.

Cause: The application’s Webhook URL is empty, mistyped, or out of date, for example after your store moved to a new web address.

Fix: For a WooCommerce store, copy the address from the plugin:

Go to WooCommerce > Print Manager in WordPress.
Open the Application tab.
Click inside the Webhook Url field. The plugin copies the address and shows “Copied”.
Sign in to the BizPrint dashboard in another tab.
Click Applications in the menu.
Click your store’s application.
Delete everything in the Webhook URL field.
Paste the address you copied.
Click Update next to the field. BizPrint tests the new address straight away.
Click Perform test connection to see the result.

For your own app, enter the full address of the endpoint that receives BizPrint webhooks. See Receive print job updates from BizPrint with webhooks.

The keys in WordPress do not match the application

Symptom: The test fails and the reason ends with status code 401.

Cause: Your store only accepts webhook messages for the application whose keys are saved in the plugin. The keys in WordPress belong to a different application, or were never saved. The Webhook URL must be set in the same application whose keys your store uses.

Fix: Make sure you are testing the application whose keys are in WordPress:

Go to WooCommerce > Print Manager in WordPress.
Open the Application tab.
Sign in to the BizPrint dashboard in another tab.
Click Applications in the menu.
Click your store’s application.
Compare the Public Key in WordPress with the Public Key on the application’s page.
Copy both keys from the right application into the plugin, if the keys differ. See Connect the BizPrint plugin for WooCommerce to your BizPrint account.
Click Save Changes in WordPress.
Click Perform test connection again.

Never email the Secret Key or paste it into a chat.

Your website’s clock is wrong

Symptom: The test fails and the reason ends with status code 400, although the Webhook URL and keys are right.

Cause: Your store accepts webhook messages only for a short time after BizPrint sends them. If your website’s server clock is set ahead of the real time, your store treats every message as too old and refuses it.

Fix: Get the clock corrected:

Ask your hosting provider to check that your website’s server uses the correct time.
Click Perform test connection again.
Contact BizPrint support, if it still fails.

BizPrint cannot reach your website

Symptom: The test fails with a reason about a timeout, a connection that was refused, or an address that could not be found. Or your website shows a maintenance page, a login prompt, or a block page when you open it from another network.

Cause: Your store or app must be online and reachable from the internet at its Webhook URL for BizPrint to deliver messages. It may be offline, in maintenance mode, protected by a password (common on staging sites), or something on your website or hosting may be refusing the requests.

Fix: Make sure your website can be reached:

Open your website from a phone on mobile data, without signing in.
Check that it opens normally.
Take it out of maintenance mode, if it is in it.
Contact your hosting provider or BizPrint support, if you are not sure why it cannot be reached.
Click Perform test connection again.

Your store or app must be able to receive messages from the internet at its webhook address. Do not turn off a firewall or any other security feature to try to fix this.

The application uses the Legacy API

Symptom: The application’s page in the dashboard has no Webhook URL field and no Webhook Info section, so you cannot run the test. Its API Version shows Legacy API.

Cause: Webhooks work only with the REST API. Applications that use the older Legacy API do not have them.

Fix: Move to the REST API:

Move your store to the REST API. See Move the BizPrint plugin for WooCommerce from the Legacy API to the REST API. When you migrate from the plugin, it sends its webhook address to BizPrint for you.
Run the test. See Test the webhook connection for a BizPrint application.

Still stuck? Contact BizPrint support at https://getbizprint.com/support/.