Hi, sometimes a forum has mixed content warnings. See now Letsencrypt: [Bild] Let's Encrypt Community Support Let's Encrypt Community Support Some favicons - http://alohadentalgroup.com/assets/icons/favicon.ico Found in https://sjc4.discourse-cdn.com/letse…

That favicon URL isn’t hosted in Discourse, are you using Discourse? What’s the URL for the installation? Do you have force_https enabled? If so reupload your icons. If not enable it then re-upload.

[Bild] Stephen: What’s the URL for the installation? Do you have force_https enabled? I don’t know, I’m not an administrator of the Letsencrypt forum. But if there is a local option, I will ask in the internal Regular-forum. PS: Thanks moving

The warning is nothing to worry about. One of the users on Let’s Encrypt site added a URL in http, in this topic Issues running certbot command - Help - Let's Encrypt Community Support . For this reason the browser warns (rightly) that there is mixed content.

[Bild] dax: The warning is nothing to worry about. Mixed content warnings are always bad. It’s possible to add cookies via http that are used with the next https connection. So forum software should never initiate http connections. Especially in a forum that talks about “My certificate is wr…

[Bild] JuergenAuer: http://alohadentalgroup.com/assets/icons/favicon.ico That favicon isn’t available over HTTPS. The mixed content warning isn’t ideal, but it’s preferable to user confusion over why their links don’t work.

[Bild] Stephen: That favicon isn’t available over HTTPS. I know. But it’s possible that a man in the middle uses such a browser initiated http connection to add a cookie vie http. Later, the cookie is sent from the browser via https - and the man in the middle knows the session cookie. That …

[Bild] supermathie: The browser isn’t sending its cookies for the forum site to another site, HTTP or HTTPS. That’s not the problem. That would be a browser bug. A man in the middle can add a cookie in the http://alohadentalgroup.com connection with the domain alohadentalgroup.com, with the …

Gemischte Inhalte Warnungen

Produktunterstützung

Stephen (Stephen) 11. September 2020 um 10:05 2

Diese Favicon-URL wird nicht von Discourse gehostet. Verwendest du Discourse? Wie lautet die URL der Installation?

Ist force_https aktiviert?

Wenn ja, lade deine Icons erneut hoch. Wenn nein, aktiviere es und lade sie dann erneut hoch.

Thema		Antworten	Aufrufe
Apple touch icon causes mixed content warning Product Support	7	1072	26. Februar 2019
Insecure favicon with mixed content warnings Product Support	0	1150	1. Oktober 2021
Discourse not aware of SSL termination (mixed content) Self-hosting	7	2054	8. August 2019
After running setup wizard with Let's Encrypt, favicon not loading over HTTPS Bug	3	1162	2. April 2019
Mixed content warning due to favicon not being saved Product Support	0	413	4. Mai 2021

Gemischte Inhalte Warnungen

Verwandte Themen