Title: ERR_CONTENT_DECODING_FAILED
Last modified: September 10, 2017

---

# ERR_CONTENT_DECODING_FAILED

 *  [SRD75](https://wordpress.org/support/users/srd75/)
 * (@srd75)
 * [8 years, 7 months ago](https://wordpress.org/support/topic/err_content_decoding_failed-4/)
 * Hi Folks,
 * I published a post, and the post viewed fine in the browser.
 * I experimented with adding a custom field to Divi’s `single.php`, but I received
   a Chrome error when viewing the post
 * > This site can’t be reached
   > The webpage at [https://steve.doig.com.au/photography/crawley-sunrise-iii.html](https://steve.doig.com.au/photography/crawley-sunrise-iii.html)
   > might be temporarily down or it may have moved permanently to a new web address.
   > 
   > ERR_CONTENT_DECODING_FAILED:
 * I renamed `single.php` to `single.temp.php`, but the `ERR_CONTENT_DECODING_FAILED`
   error remains.
 * I have cleared the WP Super Cache cache, and the browser cache, and the Cloudflare
   cache, and the issue remains.
 * Help appreciated, Steve.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ferr_content_decoding_failed-4%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Thread Starter [SRD75](https://wordpress.org/support/users/srd75/)
 * (@srd75)
 * [8 years, 7 months ago](https://wordpress.org/support/topic/err_content_decoding_failed-4/#post-9483164)
 * To clarify, `single.temp.php` resides in the child theme’s folder.
 *  Thread Starter [SRD75](https://wordpress.org/support/users/srd75/)
 * (@srd75)
 * [8 years, 7 months ago](https://wordpress.org/support/topic/err_content_decoding_failed-4/#post-9483165)
 * Also, the issue only occurs in Chrome. The post loads fine in Edge.
 *  Thread Starter [SRD75](https://wordpress.org/support/users/srd75/)
 * (@srd75)
 * [8 years, 7 months ago](https://wordpress.org/support/topic/err_content_decoding_failed-4/#post-9483168)
 * The post loads fine in Chrome Incognito, but not in Chrome.
 * Clearing all cookies from the subdomain and domain resolves the issue. /confused.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘ERR_CONTENT_DECODING_FAILED’ is closed to new replies.

 * ![](https://ps.w.org/wp-super-cache/assets/icon-256x256.png?rev=1095422)
 * [WP Super Cache](https://wordpress.org/plugins/wp-super-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-super-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-super-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-super-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-super-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-super-cache/reviews/)

## Tags

 * [err_content_decoding_failed](https://wordpress.org/support/topic-tag/err_content_decoding_failed/)

 * 3 replies
 * 1 participant
 * Last reply from: [SRD75](https://wordpress.org/support/users/srd75/)
 * Last activity: [8 years, 7 months ago](https://wordpress.org/support/topic/err_content_decoding_failed-4/#post-9483168)
 * Status: not resolved