Return to Jive Software

Skip navigation
Up to Discussions in Support
2,367 Views 3 Replies Last post: Sep 2, 2008 6:47 PM by jbrose RSS
jbrose Novice
jbrose
363 posts since
Nov 25, 2002
Currently Being Moderated

Aug 26, 2008 7:23 AM

CS 2.5 - Admin - HTTP 502 Bad Gateway: Content Encoding Error

Not sure if this is my client's network or an issue on your end, but I get this message with every page in the admin app (I don't get this on the normal application side).

 

HTTP 502 Bad Gateway: Content Encoding Error (content_encoding_error)

HTTP 502: Server response could not be decoded using encoding type returned by server.
This is typically caused by a Web Site presenting a content encoding header of one type, and then encoding the data differently.
todd.west Jive Employee
todd.west
15,926 posts since
Jul 14, 2008
Currently Being Moderated
Aug 26, 2008 3:43 PM in response to: Josh Brose
Re: CS 2.5 - Admin - HTTP 502 Bad Gateway: Content Encoding Error

Hi Josh,

 

I have never seen this issue before so I am leaning towards a network issue on your end. Have you attempted to load the admin console in another other web browser? What about trying on another network (if possible)? What application server is this running on? I will keep searching for a possible cause but this is a pretty rare error. Also, if you could post the logs from your <jiveHome>/logs/ folder that could provide some insight. Thanks.

 

-Todd

todd.west Jive Employee
todd.west
15,926 posts since
Jul 14, 2008
Currently Being Moderated
Sep 2, 2008 4:54 PM in response to: Todd West
Re: CS 2.5 - Admin - HTTP 502 Bad Gateway: Content Encoding Error

Hi Josh,

 

I haven't heard from you in a while, any updates on this situation?

 

-Todd

jbrose Novice
jbrose
363 posts since
Nov 25, 2002
Currently Being Moderated
Sep 2, 2008 6:47 PM in response to: Todd West
Re: CS 2.5 - Admin - HTTP 502 Bad Gateway: Content Encoding Error

This seemed to have been cleared up by sticking with internal CS through the entire process (not mixing it with community)... it also cleared up the problems I was having with the "Status" widget and the problems with the Org Charts.

More Like This

  • Retrieving data ...

Bookmarked By (0)

To better serve our customers we have included functionality to automatically follow up on a case after it has been idle for more than 5 days, and then auto close after an additional 3 days of inactivity. Choose No to acknowledge that this case will remain idle for longer than 5 days.
Making cases public allows other customers to learn from the solution of the case. It can also be used to gain feedback from others in the community. Ask our Support Engineers for more info, but we encourage you to make your cases public.