Avatar for Username

Mozilla サポートの検索

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.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

With a valid certificate and no unencrypted elements, I am getting gray triangle on my site in Firefox. Why?

  • 4 件の返信
  • 4 人がこの問題に困っています
  • 3 回表示
  • 最後の返信者: jeremiah.t

jeremiah.t
jeremiah.t
more options
My site is getting a gray triangle icon despite the lack of any other elements that could be construed as unencrypted. While trouble shooting the issue, I created a page that contains only one line of text in a

tag and I am still getting the gray triangle. The certificate is valid and other browsers have no issue with the site. Certificate is SHA1, RSA 2048, and expires in August of 2015. According to research SHA1 should still be good until January of 2016. Is there something else that I am missing?

My site is getting a gray triangle icon despite the lack of any other elements that could be construed as unencrypted. While trouble shooting the issue, I created a page that contains only one line of text in a <p> tag and I am still getting the gray triangle. The certificate is valid and other browsers have no issue with the site. Certificate is SHA1, RSA 2048, and expires in August of 2015. According to research SHA1 should still be good until January of 2016. Is there something else that I am missing?

すべての返信 (4)

jeremiah.t
jeremiah.t 質問者
more options

The URL for my test is here:

https://www.directinn.com/ssltest.html

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

Firefox 36 will display a gray exclamation triangle if (1) there is mixed content in the page -- that's not new -- or (2) the server is configured to use RC4 as the encryption cipher and Firefox isn't able to negotiate a stronger cipher -- this is new in Firefox 36.

Unfortunately, Firefox doesn't have a direct error message on this; it just points to #1 and #2 above in general terms. If you open the page in Chrome and click the padlock in the address bar, you usually can find the RC4 issue buried in the Connection information. An example is attached for reference.

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

Oh, thanks for the URL. You also can view this report (link broken for posting):

https://www.ssllabs.com/ssltest/analyze.html?d=directinn.com

In the Configuration section, there are two issues:

(1) TLS 1.0 is the highest protocol. This will cause the server to be inaccessible in Firefox 37.

(2) RC4 is the only cipher option. This is generating the warning in Firefox 36.

この投稿は jscher2000 - Support Volunteer により に変更されました

jeremiah.t
jeremiah.t 質問者
more options

Thanks, jscher2000.

Both of your replies provide good information for me to use to move forward on finding the solution.