"Content Encoding Error" after logon

[Ric41]

Server

• FOG Version: 1.20
• OS: Debian 8.6

Client

• OS: Windows 7

Description

Hi,
Since few hours, i have a “Content Encoding Error” error after login. I can access to all pages (it seems) except the homepage. While this appear, I just tried the Quick image boot menu on a laptop, that doesn’t do anything (can’t find image storage). I was also backup a indows xp image on another pc. I have the problem on all the pc i tried to logon, on FF and IE (not tried other browser). Does anyone know what’s the problem ?

[Tom Elliott]

I don’t know what you’re referring to. Maybe a picture could help? Maybe an error log?

[Ric41]

what do u want as picture ?

[george1421]

@Ric41 A screen shot of the actual error, so the devs can see the placement and conditions of the error (with the understanding that you are using 1.2.0).

Browser used + version, client OS used when the error was generated. Is the language USA or some other format. Are other questions that come to mind.

[Ric41]

there is nothing to see, the page can’ load.! here is a screenshot : https://postimg.org/image/aq1hnpqhv/
same problem on firefox and ie. I was on a win7 laptop while the error appear, on firefox. Same error on another pc (win xp and firefox too). the dashboard is inaccessible. I use the english language in fog, and usa in firefox (portable version).

[Wayne Workman]

My first recommendation would be to rerun the fog installer. If it works after this, I’d recommend you moving to the latest FOG release, 1.3.0.

[Ric41]

the upgrade is planned, i’ll do this monday. I’ll try to rerun the install script after the current task are finished

[Wayne Workman]

@Ric41 I am reluctant to believe that upgrading without solving the original problem will work.

[Ric41]

Hi,
I just relaunched the install script, but still the error. I’ll take a look in the db.

—edit—
it’s not the db

[Tom Elliott]

What’s in the apache error logs?

[Ric41]

i found the cause. It was a typing error in the php.ini…
thanks for the help

[george1421]

@Ric41 Please explain what you found just in case someone else see a similar error.

[Ric41]

it was a typing error in the timezone, that i modified the same day.

[george1421]

@Ric41 Thank you for posting the cause/results.