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.

詳しく学ぶ

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

SSL Issues with my site & Firefox

  • 1 件の返信
  • 0 人がこの問題に困っています
  • 3 回表示
  • 最後の返信者: cor-el

Chris1968
Chris1968
more options

Hi all,

I have a site that I am working on for myself. Its a WordPress site using a commercial theme. The problem I have is that I am not showing as secure in the address bar when opened in Firefox. Its fine in other browsers but Firefox tells me that I have insecure content with the message " Parts of this page are not secure (such as images) " and shows the exclamation mark by the padlock in the address bar.

I have installed a plugin called SSL Insecure Content Fixer and tried various setting but without success. I have also checked my site with https://www.whynopadlock.com/ and passed with flying colours so at a bit of a loss now.

If anyone has any suggestions that would be great.

Many thanks, Chris

Hi all, I have a site that I am working on for myself. Its a WordPress site using a commercial theme. The problem I have is that I am not showing as secure in the address bar when opened in Firefox. Its fine in other browsers but Firefox tells me that I have insecure content with the message " Parts of this page are not secure (such as images) " and shows the exclamation mark by the padlock in the address bar. I have installed a plugin called SSL Insecure Content Fixer and tried various setting but without success. I have also checked my site with https://www.whynopadlock.com/ and passed with flying colours so at a bit of a loss now. If anyone has any suggestions that would be great. Many thanks, Chris

すべての返信 (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Sounds like some content gets retrieved via an http:// link. The Web Console and the Network Monitor should give more info about what file(s) this is about.

Safest is usually to leave out the protocol (http: or https:) and leave the leading '//' to let the browser choose the protocol as used for the HTML page.