We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

SSL Issues with my site & Firefox

  • 1 个回答
  • 0 人有此问题
  • 3 次查看
  • 最后回复者为 cor-el

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)

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.