Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

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

Firefox won't open site which Chrome opens fine

  • 7 replies
  • 1 has this problem
  • 6 views
  • Last reply by retano

more options

I have a site which opens fine with Chrome browser, IE, Safari, Opera, but will not open with FF. Initially FF (and other browsers) is asking about security certificate which I add and save the exception. After that redirect should be performed and it is done in other browsers. But in Firefox all I see is a blank white page.

I have a site which opens fine with Chrome browser, IE, Safari, Opera, but will not open with FF. Initially FF (and other browsers) is asking about security certificate which I add and save the exception. After that redirect should be performed and it is done in other browsers. But in Firefox all I see is a blank white page.

Chosen solution

Checked with developers of the website, here is the answer: FF16.0.2 really does not want to execute a script derived from the untrusted node, even if we add the certificate to the exceptions. Obviously, some feature of the FF. Other browsers execute the script fine

So, the problem will be solved if we add (someday) a correct certificate to this website.

The issue can be closed.

Read this answer in context 👍 0

All Replies (7)

more options

Can you post a link to a public page that doesn't require authentication (log in) to access it?

more options

Unfortunately it is closed from public.

more options

What kind of certificate is this and what error do you get?

You can retrieve the certificate and check details like who issued certificates and expiration dates of certificates.

  • Click the link at the bottom of the error page: "I Understand the Risks"

Let Firefox retrieve the certificate: "Add Exception" -> "Get Certificate".

  • Click the "View..." button and inspect the certificate and check who is the issuer.

You can see more Details like intermediate certificates that are used in the Details pane.

You can also check for Net errors in the Web Console (Web Developer > Web Console; Ctrl+Shift+K)

more options

Maybe I was not clear... I already: - clicked "I understand the risks" - accepted the certificate - ticked "save it permamently"...

So, I don't see invitation to accept risks and certificate anymore, just blank page with no errors right after I enter the URL.

The certificate expires 04/2013.

I don't have errors within console, only this text: [14:53:45.500] GET https://somepage/ [HTTP/1.1 304 Not Modified 47мс]

more options

If you've accepted the certificate then you can click the Site Identity Button button on the location bar to inspect the certificate.

Do you see a response header if you click that GET entry in the web console?

Is there any page source loaded?

  • Firefox > Web Developer > Page Source
  • Tools > Web Developer > Page Source (Ctrl+U)
more options

Yes, I see the response header: Server:Microsoft-IIS/6.0Last-Modified:Mon, 23 Jul 2012 14:01:58 GMTEtag:"08f53b9db68cd1:a83"Date:Thu, 15 Nov 2012 06:57:55 GMTContent-Location:https://somepage/index.htmCache-Control:no-cacheAccept-Ranges:bytes

After CTRL+U I see some HTML code, so I guess source is loaded

more options

Chosen Solution

Checked with developers of the website, here is the answer: FF16.0.2 really does not want to execute a script derived from the untrusted node, even if we add the certificate to the exceptions. Obviously, some feature of the FF. Other browsers execute the script fine

So, the problem will be solved if we add (someday) a correct certificate to this website.

The issue can be closed.