Every other image is loaded via HTTPS, this is the only exception. I need to fix this in order to force HTTPS site-wide. [Capture] Am I doing something wrong?

UPDATE: I managed to make the www version on FF secure as well. All I did was remove the root domain (the one without the forum install) from the list: -d example.com -d www.example.com and all I have left is the actual forum -d community.example.com -d www.community.example.com. Not sure why that h…

Yep, you can’t publish over HTTPS reliably without that setting being enabled. It’s why it warns you every time you visit the dashboard that it has to be set. As you’ve not shared your site URL we can’t look at the certificate to verify if you’ve configured it correctly, but that error suggests you…

[изображение] Stephen: that error suggests you’ve missed a subject alternate name. It’s only going to be used for the redirect, but once you’ve corrected your certificate the error will go away. Thanks for your input. So essentially I should add a redirect from the https://www version to htt…

I’m not implying anything, if you’re getting an HTTPS error for www that means you’ve configured a server directive to listen on an HTTPS URL, but the associated certificate lacks the Subject Alternate Name for WWW. Your Let’s Encrypt request will need to request any additional domains passed in usi…

Interesting but I don’t understand why it’s working in Chrome perfectly and only FF is displaying the error. Here is my app.yml ssl config: after_ssl: - replace: filename: "/etc/runit/1.d/letsencrypt" from: /-k 4096 -w \/var\/www\/discourse\/public/ to: | -d…

I’m sorry, without real details for the site to troubleshoot you’re probably on your own here. There are ways to step through the problem and identify the cause, but we can’t even begin to employ such methods when you’re artificially limiting and redacting aspects of your setup.

The only thing I masked was the actual website name: example. The rest of the details are not redacted in any way.

They are, because I can’t inspect the headers and redirects to a fictional URL. Good luck resolving this anyhow.

Are you using Cloudflare or some other “magically add HTTPS through trickery” service?

[изображение] codinghorror: Are you using Cloudflare or some other “magically add HTTPS through trickery” service? No, I am not. Absolutely no magic tricks.

Your symptoms are implying that firefox is being case sensitive where Chrome is not. If you add a WWW version to the let’s encrypt domain list does that make Firefox happy?

Why is the Apple Touch Icon loaded via HTTP instead of HTTPS?

Поддержка

brahn (Brahn) 18.Декабрь.2018 03:57:03 23

The certificate should list all the domains you have included, can you see them? Perhaps the certificate is not being recreated with the list of domains when you rebuild? Follow the debugging instructions in Setting up HTTPS support with Let’s Encrypt

Тема		Ответов	Просм.
Http logo urls after enabling LetsEncrypt Self-hosting	15	1436	08.06.2024
Avatar, Site Logos, and Cert Errors Self-hosting unsupported-install	61	4063	25.05.2020
Mixed Content: The page at '<URL>' was loaded over HTTPS error Support	6	7611	31.01.2022
Apple touch icon causes mixed content warning Support	9	959	30.03.2022
Problems with Force https and mixed https content Self-hosting	20	3646	02.12.2020

Why is the Apple Touch Icon loaded via HTTP instead of HTTPS?

Связанные темы