Explore information related to 330 content decoding failed


Nginx upstream timed out error - Fix it Now ?


This article covers methods to resolve Nginx upstream timed out error. Basically, this error happens as a result of server resource usage and software timeouts.

A possible issue here could be that PHP is using too much RAM and the PHP FPM process gets killed. 


Therefore, do the following to fix this nginx error:

1. Make sure that there is enough RAM on the server, to check that you could use the top, htop or free -m commands.

2. Make sure that the PHP memory limit is not too high compared to the actual available memory on the Droplet. 

For example if you have 1GB of RAM available your PHP memory limit should not be more than 64MB otherwise only a few processes could consume all of your memory.

3. Optimize your website by installing a good caching plugin, that way you would reduce the overall resource usage on the server.

4. Delete any plugins that are not being used. Generally speaking, it is always recommended to try and keep the number of your plugins as low as possible.

5. Consider using a CDN like Cloudflare, that way it would offload some of the heavy liftings from your Droplet. 

Read More



330 Content Decoding Failed - Nagios Web browser error


This article covers how to fix 330 Content Decoding Failed Nagios browser error. Basically, this error occurs when an HTTP request's headers claim that the content is gzip encoded, but it is not. 

To fix this error:

The Apache web server requires zlib.output_compression to be configured to On in the /etc/php.ini file.

Execute the following command to open the file in vi:

vi /etc/php.ini

When using the vi editor, to make changes press i on the keyboard first to enter insert mode.

Press Esc to exit insert mode.

To locate the line zlib.output_compression = type the following:

/output_compression =

This should take you directly to the line. Change the setting to On:

zlib.output_compression = On

When you have finished, save the changes in vi by typing:

:wq

and press Enter.

The last step is to restart the Apache service using one of the commands below:

RHEL 7 + | CentOS 7 + | Oracle Linux 7 +

$ systemctl restart httpd.service

 Debian | Ubuntu 16/18/20

$ systemctl restart apache2.service

After the service has restarted the problem should no longer occur.

Read More




For Linux Tutorials

We create Linux HowTos and Tutorials for Sys Admins. Visit us on LinuxAPT.com

Also for Tech related tips, Visit forum.outsourcepath.com or General Technical tips on www.outsourcepath.com






Focus on your business, not your servers.

Click Here to Learn More