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 nzarchitecture.net.nz . This may be caused by a misconfiguration or an attacker intercepting your connection. This issue may relate to Let’s Encrypt changes implemented on that date. The issue is triggered when url https://www.nzarchitecture.net.nz is used, but not when https://nzarchitecture.net.nz is used The issue persists, even after updating to 2.8.0 beta 7, and doing full rebuild. A consequence of the error message appearing on my landing page is that the site is flagged as no longer meeting Facebook requirements, meaning Facebook login has been disabled by Facebook.

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 effect. Edit: Actually it looks like the use of --keylength has been replaced by -k, so you’ll need the following instead: Apologies, my Github search lead me to an old fork without me noticing. --keylength is correct.

it’s an facebook issue that they need to fix. the cert is 100% legit SSL Checker Use our fast SSL Checker will help you troubleshoot common SSL Certificate installation problems on your server including verifying that the correct certificate is installed, valid, and properly trusted.

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 disappears

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 tell the average user that they can’t use ‘www’ - especially if they need to log in to see any warning to that affect…

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 without the www. 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 There are a lot of emails out there with links to the site that include the www. By ‘the place the redirect lives’ do you mean Digital Ocean in this case? (my host, and where DNS settings are managed from)

[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: [image] Set up Let’s Encrypt with multiple domains / redirects Sysadmins NOTE: @pfaffman says: This page needs to be cleaned up. There is now a new ENV setting that will let you add more hostnames. In your app.yml under your DISCOURSE_HOSTNAME line (it can go many places but that one makes sense), add DISCOURSE_HOSTNAME_ALIASES: domain.com,other.domain.com and early reports suggest that you’ll get valid certs for those domains and that accessing https://domain.com will properly redirect you to your DISCOURSE_HOSTNAME without a certificate error. If you do that an…

Facebook login was flagged as non compliant by Facebook after change to Let's Encrypt certificate system

Product Support

JammyDodger October 27, 2021, 2:16pm 11

You can add an extra line or two to your app.yml. This worked for me when I was having issues:

Topic		Replies	Views
Non www to www without certificate error Self-hosting	13	2171	January 17, 2022
LetsEncrypt working without www, not with www Product Support	11	2157	January 19, 2020
About force www to non www Product Support	29	3106	January 6, 2019
Www to non www with https Product Support	10	739	November 13, 2023
Making 'www' work with Discourse Product Support	30	3048	May 15, 2020

Facebook login was flagged as non compliant by Facebook after change to Let's Encrypt certificate system

Related topics