Composer error: Failed to decode response: Failed to decode zlib stream
If you've experienced this error using Composer, there are several ways on how to solve this.
1. Verify whether the Amasty repository is installed and whether the authentication keys are valid. More information on this can be found in our Composer User Guide.
2. Check whether the server have access to the internet. The below command can help with it:
curl -I https://amasty.com
3. Check whether the required zlibc library is installed on the server. The next command will either install it or will show that this library is already installed:
sudo apt-get install zlibc
4. Check whether the zlib.output_compression setting is enabled in the php.ini file. It can be checked with this command:
php -i | grep "zlib.output_compression"
Related Articles
Composer error: Command "require" failed. You must be using the interactive console to authenticate
This error appears when Composer is unable to locate the PHP version with which it can work. The located version can be either not supported or not found at all. To help composer find the PHP version that is being used by Magento, it is required to ...Composer error: SSL certificate problem: certificate has expired
curl error 60 while downloading https://composer.amasty.com/enterprise/packages/module-page-speed-tools-1.0.4-ee.zip: SSL certificate problem: certificate has expired This error appears due to an outdated or not supported SSL certificate. The ...I’m trying to install the module via composer, but the package is not found. How to resolve it?
Composer is the dependency manager that allows you easily download the required files on your server. The files are located on a remote server, or a repository, that you need to add to the list of “known” ones and authenticate to using the username ...Composer doesn’t allow me to install the latest update of the module. Is there a solution for it?
There are two possible reasons why the composer is not fetching the latest version of the module. The first one is that the module package is loaded from caches - composer cannot see the latest available version, so it loads the latest that is ...I’ve updated the modules via composer and I got the error Amasty/Base has been already defined.
For Amasty modules, there are two possible ways of installation/update: via composer and via a direct file upload. Depending on the initial installation method, the module files will be located in a specific directory. Each installation method has ...
Announcements
Already Done in Q1'23
Brand new extensions We launched a coming soon page for the new Back Forward Cache extension. It restores the recently visited page when the customer clicks 'Back' or 'Forward' browser options, thus ensuring faster page load speed. Subscribe to the releaseRoadmap | What to expect in Q1'23
New features and improvements Improved Layered Navigation generate SEO-friendly URLs for multi-select Category filter; better speed performance of the Apply filters button; improve Category list load time. Special Promotions Pro optimize data types inAlready Done in Q4'22
New Amasty services Make sure your site is well-performing with our E-commerce QA testing service. Let our specialists check various elements of your website and get the issues fixed. The service is available for any e-commerce platform (Magento, Shopify,Roadmap | What to expect in Q4'22
New features and improvements Elastic Search better performance of synonyms; REST API support. Product Labels enhanced extension performance with a lot of products on the page. Blog Pro posts migration from one Magento instance to another; email notificationsAlready done in Q3'22
New solutions Our new SaaS tool - Website SEO Health Check. Discover the most severe SEO mistakes which can damage your website. Available as part of Pro and Premium SEO Toolkit. New features and improvements Import and Export NEW we added the possibility