Syncing with HTTP Auth #
Often HTTP authentication is used on staging sites to avoid uninvited visitors.
This will block the Clerk importer as well and display a 401 Unauthorized error in the sync log.
You can easily verify the importer by inserting the authentication info in the import URL like below, in Data Sync at my.clerk.io:
https://USER:OASS@dandomain.clerk.io/api/6155349/28
Common sync errors #
When importing data with Clerk.io’s DanDomain App, 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:
http://USER:PASS@dandomain.clerk.io/api/6155349/28
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.
Also check your public key, private key and import url are correct for the store you are operating within my.clerk.io
In some cases (if you are on an older dandomain version), this error will also be shown if you are using different language-domains and each have different IDs. In this case make sure the IDs for each store are corresponding to the ones in your dandomain backend.
What if I have already whitelisted but the same error still occurs?
There are a few instances when you have whitelisted the importer’s IP address, and the error still persists, then we recommend you look into these parts:
The authentication part of the body may be removed from the request from the shop’s server.
Rate limit for the server in regards to cloudflares.
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 extension is either:
Not installed at all
A cache causes the link to not be initialised
First make sure that you have installed the app correctly.
Second, be sure to empty your webshops cache before trying a new import.
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:
500 Internal Server Error #
This error mean that your server encountered an internal error and were not able to specify which error happened.
In these cases you can check your Server Log to identify which process crashed and why. In most cases its simply because of a product with an invalid attribute, or a function that is called wrongly in the webshop. If the later is happening, then we suggest to contact our tech support team for this part.
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.
Upgrading to Clerk.js 2 #
Clerk.js 2 is a faster and much more flexible version of our JavaScript library that makes installing Clerk.io on any webshop a breeze.
However, since the two versions work slightly differently, you need to follow these steps to successfully upgrade.
The two main differences in Clerk.js 2 is that the Designs in my.clerk.io use the Liquid templating language, but they can also easily be created using the Design Editor.
Step 1: Converting Designs #
Since Clerk.js 2 has a different approach Designs, you need to create new ones.
You can create your Clerk.js 2 Designs in one of two ways:
1. Use the intuitive Design Editor to create new Designs, as described in the following points.
2. Convert your old Designs. Follow this guide to see how to do it.
1.1 Start by going to my.clerk.io -> Recommendations / Search -> Designs and click New Design:
1.2 Follow the design set up wizard and select your design type and give your design a n ame (we recommend adding " V2" so its obvious that you are using Clerk.js2).
1.3. In the Design Editor, click any of the existing elements like the name, image, button etc. to edit it, or add new elements to the Design to add more information about products.
1.5. Lastly, go to Recommendations / Search -> Content and change your Clerk.io Content to use your new Design.
1.6. Click Update Content. This will temporarily cause them to not show up on your webshop, until you are done with Step 2. Choose the new Design for all Content that should be updated.
1.9. There! You are now ready to switch over to Clerk.js 2.
Step 2: Switch to Clerk.js 2 in the DanDomain App #
Next you need to activate Clerk.js 2 in the DanDomain Classic app.
2.1. Login in to your DanDomain Classic backend and go to the Clerk.io App in the sidemenu.
2.2. Under General click and check the box next to Brug Clerk.js 2 and click Save:
