Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Facebook not loading properly

  • 8 replies
  • 1 has this problem
  • Last reply by jscher2000

more options

The Facebook webpage loads the text without graphics. Works on Chrome and I.E. I restarted in safe mode with no luck. I attached a image of the page. All other sites I use are working properly.

All Replies (8)

more options

Issue loading image earlier. Here is the page.

more options

Hi b2spencer, do you notice the # on the end of the address in your screenshot? This can indicate that a scripted link didn't run correctly. Either JavaScript is blocked, or the expected script file is missing (not loaded). And the broken layout typically suggests that a style file didn't load or was ignored for some reason.

Could you check whether there is a pattern of files not loading. You can open the Network Monitor in the lower part of the tab using either:

  • "3-bar" menu button > Web Developer > Network
  • (menu bar) Tools > Web Developer > Network
  • (Windows) Ctrl+Shift+e

Then reload the page using Ctrl+Shift+r to bypass cached files. Firefox should start listing all the files it is requesting, along with information about whether the request was successful. For example "200" in the left column is a successful retrieval, while codes starting with 400 or higher, or a completely missing status, indicates a problem.

Do you notice any pattern of failed requests? For example, FB uses other domains for its style sheets. When I go to the home/login page, the first style sheet Firefox requests is,cross/LF9kfHywqmx.css

If you follow that link directly, do you get the expected wall of text starting with


Or is there a problem loading it?

more options

Thanks for your assistance with this issue. We followed the steps and found the errors in the screen shots. There are network 401 errors and a script error in the console referring to a .js file. Is there a browser setting to fix and allow the java script to run?

more options

I think there is some kind of filter running that is redirecting (307 = "temporary redirect") the addresses to a .mil address. Could you right-click > Open in New Tab on one of those 401 error lines and see whether the response provides more detail about what's going on?

more options

We are redirecting the traffic to our proxy to authenticate the user.... I think I've tracked down the issue to authentication. The initial request contains a cookie that allows users to authenticate with the proxy how ever the subsequent requests fail resulting in a 401 error because they do not contain that same cookie. Is there a way to force the browser to set the authentication cookie for all requests? We have set the about:config settings to .mil for the following network.negotiate-auth.trusted-uris, network.negotiate-auth.delegation-uris, network.automatic-ntlm-auth.trusted-uris.

more options

When you say the initial request, do you mean the initial request to the "first party" server ( or to the "third party" server ( If the problem is limited to third party cookies, that could be a settings issue (Firefox sets and sends third party cookies by default).

Although, most major sites use third party resources, so it would be odd if a third party cookie problem only manifested on FB. Hmm.

more options

The initial request ( gets redirected to our proxy our proxy redirects for authentication, the browser connects to the proxy and gets a request from the proxy for user credentials, the user is authenticated then the browser sets the authentication cookie and gets redirected back to with the cookie set for the proxy. When calls the "third party" that process should be the same however, it seems as if the browser does not send the authentication credentials when it gets redirected. Also this problem does exist on other sites another example is reddit.

more options

Firefox will not send a cookie -- whether passed through from FB or added by the proxy -- to a request sent to a completely different host such as It sounds as though each host needs independent authorization if everything is cookie-based. Can you check with your proxy vendor on whether there is a solution to this? Maybe there's a list of CDNs that needs updating.