Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

FetchError in request to ES: FetchError: invalid json response body

See original GitHub issue

Current behavior

Sometimes (completely random) the API will just return a blank page when it’s supposed to return an elasticsearch response. This will cause an error page and the error to be logged to our loggin software. In the last 3 weeks this has happened about 23.5k times so it happens quite often.

I saw that a new API project (storefront-api) will be used for a future release of VSF but I can’t test if it also happens there because putting that API on a production environment and changing all our api extensions is just too much work.

Expected behavior

It should get a valid response or request it again if the data was invalid.

Steps to reproduce the issue

This only happens on a production API and it doesn’t output any errors to the logs. It just returns a 200 response with a blank page. The most occurrences have happened on this API endpoint:

api/catalog/vue_storefront_magento_1/attribute/_search

Can you handle fixing this bug by yourself?

Which Release Cycle state this refers to? Info for developer.

Pick one option.

This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.