How to Fix Common Magento 2 Server Errors When Importing Data to Clerk.io
Note: We advice you to always update the plugin to the latest version in order to get all up to date features from Clerk.
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 often happens due to one of these reasons:
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.
You may have incorrect public key, private key and/or import url within the store in my.clerk.io
You are using Storeviews with hidden URL’s, like mywebshop.com?__store=b2b. Sometimes, these URL’s can also contain 3 underscores like this: mywebshop.com?___store=b2b
If the latter, simply include the __store parameter in the URL in Data:
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 to look into these.
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 extension 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:
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 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.
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 received
This error usually happens if your webshop is using a redirect system, to send customers to different domains.
If this is the case, you simply need to use the full URL when importing in my.clerk.io: