frequent_export_errors
Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
frequent_export_errors [2019/05/23 14:56] florian [Import Issues] |
frequent_export_errors [2020/05/13 14:41] franz |
||
---|---|---|---|
Line 5: | Line 5: | ||
==== Export Issues ==== | ==== Export Issues ==== | ||
- | \\ | ||
- | === HTTP response status code 404 === | + | <note tip>In many cases an export error is just a temporary problem, that is being caused by a server that is not reachable for a short period of time. Because of this starting a manual export oftentimes can fix the problem. |
+ | The manual export can be found [[https://account.findologic.com/#/app/search-navigation/import-export|here]].</note> | ||
- | * Check if the Export URL is correct. This can be done by opening it directly in a browser. | + | \\ |
- | * If the URL can be opened in the browser, check if the protocol (http or https) is correct. | + | |
- | + | ||
- | \\ | + | |
=== HTTP response status code 401 === | === HTTP response status code 401 === | ||
Line 29: | Line 26: | ||
* If the Export URL is reachable from the browser, the FINDOLOGIC server might be black listed. Check those configurations or contact the FINDOLOGIC support. | * If the Export URL is reachable from the browser, the FINDOLOGIC server might be black listed. Check those configurations or contact the FINDOLOGIC support. | ||
* If the page cannot be opened, the defined user has not the required permissions. Please set these permissions accordingly. | * If the page cannot be opened, the defined user has not the required permissions. Please set these permissions accordingly. | ||
+ | * If Cloudflare is used the Browser Integrity Check has to be disabled for the export URL. | ||
- | \\ | + | \\ |
+ | |||
+ | === HTTP response status code 404 === | ||
+ | |||
+ | * Check if the Export URL is correct. This can be done by opening it directly in a browser. | ||
+ | * If the URL can be opened in the browser, check if the protocol (http or https) is correct. | ||
+ | |||
+ | \\ | ||
=== HTTP response status code 50x === | === HTTP response status code 50x === | ||
Line 36: | Line 41: | ||
A status *50x* can have many reasons. Usually they occur, if there is something going wrong at the shop`s webserver. | A status *50x* can have many reasons. Usually they occur, if there is something going wrong at the shop`s webserver. | ||
* As this status may result from your webserver being busy, try to start the export at another time. | * As this status may result from your webserver being busy, try to start the export at another time. | ||
- | * If this issue persists, please check you server logs for more details. | + | * If this issue persists, please check your server logs for more details. |
\\ | \\ | ||
Line 79: | Line 84: | ||
\\ | \\ | ||
+ | |||
+ | === Cloudflare and the Findologic export === | ||
+ | |||
+ | If you are using Cloudflare the user-agent FINDOLOGIC is blocked by default. This will cause the export to fail. The Cloudflare feature blocking the user-agent is the Browser Integrity Check. | ||
+ | There are two ways to disable the Browser Integrity Check in the Cloudflare Backend. | ||
+ | |||
+ | \\ | ||
+ | |||
+ | * Specifically for the export URL (recommended): Create a new Page Rule for the export URL, that disables the Browser Integrity Check. | ||
+ | \\ | ||
+ | {{:cloudflare_page_rule.png?800|}} | ||
+ | |||
+ | \\ | ||
+ | |||
+ | * Globally: In the Firewall Settings, set the Browser Integrity Check to `OFF` | ||
+ | \\ | ||
+ | {{:firewall_cloudflare.png?800|}} | ||
+ | |||
+ | \\ | ||
+ | |||
+ | ---- | ||
+ | |||
** | ** | ||
If you are still experiencing problems with the import/export process or if you got an error message that is not listed here, please contact [[support@findologic.com|support@findologic.com]]. ** | If you are still experiencing problems with the import/export process or if you got an error message that is not listed here, please contact [[support@findologic.com|support@findologic.com]]. ** |