Skip to main content
/

Site Navigation

Your Account

Choose Language

Website problems under Debian 8.4.0

This happens on Debian 8.4.0 on a Linux machine. I am not doing anything custom to it. The thing I think might be doing it is Debian depreciated Iceweasel for Firefox ESR at some point. Mine has been updated, so it has the Iceweasel->Firefox ESR change applied. This is not an issue in Chromium.

Block Image

Block Image

Answer this question I have this problem too

Is this a good question?

Score 0
7 Comments

Hi @nick! Thanks so much for your input. We are currently looking into this problem for you.

by

Let me know when to try again. So far I am surviving on Chromium, as much as I despise Chrome's RAM and CPU usage in general.

by

Hi @nick, I am trying to reproduce this issue. I don't currently have access to a Debian machine, but I have Firefox ESR installed on Mac OS X and was trying various things. So far the only way for me to reproduce the issue has been to disable images and stylesheets; is it possible that is how the browser is currently configured? Also, could you give me a list of the add-ons that are installed? I was able to find the ABP, Greasemonkey, and NoScript add-ons visible in your screenshot, but I haven't found the outer two. One other thought: is it possible the network is blocking CloudFront where we host our stylesheets? Thanks!

by

I tried Firefox ESR 45 on ArchLinux (Sorry, I don't have a Debian box with me right now) with NoScript on and everything looked okay. The lock icon in Firefox looked completely green in your screenshot, so it doesn't look like there are any SSL certificate problems with cloudfront either.

by

I tried enabling the essential JS bits too, @copperwall. I just didn't think to include those screenshots. I don't think it's stylesheets being blocked, because it works in Chromium but not FF.

by

Show 2 more comments

Add a comment

1 Answer

Most Helpful Answer

Seems like the stylesheets are being blocked by your browser.

My guess would be that one of your add-ons is at fault.

An easy way to check is to open up your browser's network inspector and find what's happening to the stylesheets.

Was this answer helpful?

Score 3
Add a comment

Add your answer

Nick will be eternally grateful.