See how to get Data Sync running if your server returns an error
When importing data with Clerk.io's WooCommerce plugin, the webshops server is responsible for sending the product- category- and sales-data to Clerk.io.
However in some cases, the servers configuration might stop the import from getting access, causing an error in Data Sync.
Below is a list of the most common errors and how to fix them.
401 Server Error: Unauthorized
This error happens if your webshop/dev environment requires HTTP authentication to access it.
This is solved simply by inserting the Username and Password as part of the Import URL:
403 Server Error: Forbidden
This error happens if your server blocks the importer from accessing it. In most cases you simply need to whitelist the importers IP address to give it access.
The latest IP address can be found here.
404 Server Error: Not Found
This error happens if the importer could not access the link that sends us data from the webshop. In most cases it happens because the plugin is either:
Not installed at all
A cache causes the link to not be initialised
WooCommerce permalinks are set to Post name instead of Month and name
First make sure that you have installed the plugin correctly.
Second, be sure to empty your webshops cache before trying a new import.
If it still doesn't sync properly, go to Settings => Permalinks and change the Common Settings to Month and name and press Save:
429 Server Error: Too Many Requests
This error happens if your server denies the importer access because of too many incoming requests.
You can fix this by setting the request limit higher, for your server or by setting Page Size to a higher value in the Clerk.io importer, causing the importer to make fewer, bigger requests:
If you are using the host provider Byte.nl, the importer usually returns this error because of their rate limiter. In this case, simply contact Byte.nl and ask them to whitelist the importers User-Agent "clerk".
500 Internal Server Error
This error means that your server encountered an internal error and was unable to specify which error happened.
In these cases you can check your Server Log to identify which process crashed and why. In most cases it's simply because of a product with an invalid attribute, or a function that is called wrongly in the webshop.
An example of such an error could occur once you upgrade both WooCommerce and Klarna. In this instance, the problem is created by the 'woocommerce-gateway-klarna' plugin which does not upgrade.
If this happens to you go to
and change it to:
503 Server Error: Service Unavailable
This error is usually temporary, and is caused by the server being too busy to handle the request. Try again a bit later.
If the issue continues to happen, it could mean that the server is overloaded with processes, and is close to maximum capacity.
Check the server load, to identify if this is the case.
Invalid response returned from the WooCommerce API
This error usually happens, if WooCommerce's Debugging has been activated. This is never a good idea to have activated on a live-setup because it slows down pages, and potentially shows error messages in the frontend.
The sync issue happens if WooCommerce encounters an error while generating the product-data for the import.
This can be solved by deactivating Debugging in wp-config.php by setting define(WP_DEBUG', false).
This guide explains it in more detail:
And this guide explains an alternate workaround:
Errors will still be logged even when not in Debug Mode, but they will be logged to a file instead.