Title: Encode Error?
Last modified: October 25, 2023

---

# Encode Error?

 *  Resolved [Bruno Cantuaria](https://wordpress.org/support/users/cantuaria/)
 * (@cantuaria)
 * [2 years, 7 months ago](https://wordpress.org/support/topic/encode-error/)
 * Hello,
 * A few users are complain that sometimes the page load this way:
 * ![](https://i0.wp.com/diariodegoias.com.br/wp-content/uploads/2023/10/Imagem-
   do-WhatsApp-de-2023-10-23-as-10.32.27_1c631f6f.jpg?ssl=1)
 * I couldn’t replicate and the issue seems really rare, but 4 users complained 
   this week. After a page reload it fixes.
 * Can this be an issue caused by LiteSpeed? Maybe something wrong with LiteSpeed
   + Cloudflare?
 * Thanks for any input.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fencode-error%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

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

 *  Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [2 years, 7 months ago](https://wordpress.org/support/topic/encode-error/#post-17151185)
 *     ```wp-block-code
       <IfModule LiteSpeed>
           SetEnv no-brotli
           SetEnv no-gzip 1
       </IfModule>
       ```
   
 * please try add this to your htaccess, then purge all , purge CF cache.
 *  Thread Starter [Bruno Cantuaria](https://wordpress.org/support/users/cantuaria/)
 * (@cantuaria)
 * [2 years, 7 months ago](https://wordpress.org/support/topic/encode-error/#post-17152929)
 * Thanks for the feedback. I’ll play with the Brotli and Gzip for both Cloudflare
   and local to see if the issue still happens.
 * [@supervisior](https://wordpress.org/support/users/supervisior/) could you describe
   more about this encoding error when Cloudflare have a version of the cache and
   Litespeed have another? Maybe we can find something to mitigate it. Currently
   we use Cloudflare Cache because it’s simply overpowered and drastically reduces
   our server load. We’ve built internal API integration with Cloudflare to clear
   content whenever we clear LiteSpeed cache, even in special cases.
 *  Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [2 years, 7 months ago](https://wordpress.org/support/topic/encode-error/#post-17154242)
 * for unknown reason , when origin sends encoded content (gzip’ed or br’ed) , but
   CF thinks it’s not , so CF double compressed it and send to user , that lead 
   to this , I think.
 * so you could try disable compression at origin , and let CF to do the compression
   for visitors
 * and since connection between origin and CF servers are usually datacenter-grade,
   disable compression between origin/CF should not be a problem.
 *  Thread Starter [Bruno Cantuaria](https://wordpress.org/support/users/cantuaria/)
 * (@cantuaria)
 * [2 years, 7 months ago](https://wordpress.org/support/topic/encode-error/#post-17154413)
 * Thanks guys. This was very helpful. I’ll investigate further and tweak things
   and will udpate here for future reference.
 * We use this same setup for other websites (some with even more audience) but 
   didn’t had a complain yet.
 * I’ll mark this as solved by now.

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

The topic ‘Encode Error?’ is closed to new replies.

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

 * 5 replies
 * 3 participants
 * Last reply from: [Bruno Cantuaria](https://wordpress.org/support/users/cantuaria/)
 * Last activity: [2 years, 7 months ago](https://wordpress.org/support/topic/encode-error/#post-17154413)
 * Status: resolved