Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

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

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

SSL certificate not fully recognized

  • 1 baphendule
  • 0 zinale nkinga
  • 10 views
  • Igcine ukuphendulwa ngu zeroknight

more options

My webite https://www.tanzaniabirds.net/alphabetical1.htm#gsc.tab=0 has an SSL certificate. The website shows as secure on Edge, Chrome and Safari but not on Firefox. The message on the Firefox secure symbol says parts of the page such as photos are not secure. This website is practically all photos taken by me and friends. What can be done to make it show as secure on Firefox? Thanks.

My webite https://www.tanzaniabirds.net/alphabetical1.htm#gsc.tab=0 has an SSL certificate. The website shows as secure on Edge, Chrome and Safari but not on Firefox. The message on the Firefox secure symbol says parts of the page such as photos are not secure. This website is practically all photos taken by me and friends. What can be done to make it show as secure on Firefox? Thanks.

All Replies (2)

more options

In your header you have the line `<link rel="SHORTCUT ICON" href="http://www.tanzaniabirds.net/favicon.ico">`, telling Firefox to load the favicon via http. Firefox detects these kind of http subresources on a https site as "mixed content" and warns the user about them. You can read more about that here. The easiest solution would be to just update all subresources on your site to use https. Alternatively, you can also instruct Firefox to automatically "upgrade" those subresources to https through the upgrade-insecure-requests content security policy.

more options

The favicon.ico href needs to be changed to "https".