Since around September 30th 2021 (as far as I can tell) my site has been generating certificate errors your connection is not private NET::ERR_CERT_COMMON_NAME_INVALID’ security warning. This server couldn’t prove that it’s www.nzarchitecture.net.nz ; its security certificate is from nzarchitect…

The content is right but indentation is important in the yml file, so that needs to be corrected: after_ssl: - replace: filename: “/etc/runit/1.d/letsencrypt” from: /--keylength/ to: “-d www.nzarchitecture.net.nz --keylength” You will need to rebuild for it to take ef…

it’s an facebook issue that they need to fix. the cert is 100% legit https://www.sslshopper.com/ssl-checker.html#hostname=nzarchitecture.net.nz

That seems similar to… https://meta.discourse.org/t/configuring-google-login-for-discourse/15858/239

The thing is that even I see these errors when including ‘www’ in the url I paste/type into browser - so even though there is no actual risk, users are being hit with worrying warnings. with or without the Facebook compliance issue. Facebook meanwhile refuse to review the matter until the error dis…

in your config file /var/discourse/containers/app.yml what is your DISCOURSE_HOSTNAME: set to ?

[image] Paul_King: The issue is triggered when url https://www.nzarchitecture.net.nz is used, but not when https://nzarchitecture.net.nz is used If you real site is under the non-www domain, you must register the non-www domain in the Facebook system. Can’t mix and mingle that.

app.yml shows DISCOURSE_HOSTNAME: nzarchitecture.net.nz

[image] Falco: If you real site is under the non-www domain, you must register the non-www domain in the Facebook system. Can’t mix and mingle that. OK, I suppose that makes sense - but from a DNS point of view one is an alias of the other (or so I believed) - and it is is going to be hard to…

It’s not really an “alias” but a redirect. And you need to properly configure a redirect, which includes having a certificate in place for the place the redirect lives. For example, our partners at communiteq provide a service for that at https://www.forcewww.com/

[image] Falco: It’s not really an “alias” but a redirect. And you need to properly configure a redirect, which includes having a certificate in place for the place the redirect lives. Until recently, this had never been a problem - no Facebook warning, and no certificate warnings with or with…

[image] Paul_King: Is there any way to get the default free Let’s Encrypt’ certificate to certify both options? Keen not to complicate things with extra certificates to manage and extra cost You can add an extra line or two to your app.yml. This worked for me when I was having issues: …

La connexion Facebook a été signalée comme non conforme par Facebook après le changement vers le système de certificat Let's Encrypt

Soutien

IAmGav (Gavin Perch) Octobre 27, 2021, 1:26 2

C’est un problème Facebook qu’ils doivent résoudre.

Le certificat est 100 % légitime.

1 « J'aime »

Sujet		Réponses	Vues
Non www to www without certificate error Self-hosting	14	1839	Février 16, 2022
LetsEncrypt working without www, not with www Support	12	1846	Février 18, 2020
About force www to non www Support	30	2784	Décembre 10, 2021
Www to non www with https Support	10	535	Novembre 13, 2023
Making 'www' work with Discourse Support	30	2257	Mai 15, 2020

La connexion Facebook a été signalée comme non conforme par Facebook après le changement vers le système de certificat Let's Encrypt

Sujets connexes