This morning I rebuild my discourse installation and I got a new certificate. Testing my connections on why no padlock I got an error on intermediate certificate.
Any suggestions?
AI-generated summary
Saiano reports an intermediate certificate error on their Let’s Encrypt certificate after rebuilding their Discourse installation, causing some users—particularly on enterprise networks—to see a padlock warning. David suggests the issue may stem from a recent Let’s Encrypt change and advises updating the client OS or browser. He notes that corporate proxies might be outdated and recommends testing connectivity to other sites like discourse.org or letsencrypt.org. David also points out that the ‘Why No Padlock?’ tool might be confused by the recent changes, as another scanner, SSL Labs, shows an A+ rating for the site Saiano David.
Hi Saiano, this is most likely related to a recent Let’s Encrypt change. In general, it’s a problem on the client end, not on the Discourse end. Can you try updating your client operating system and/or browser? Do things work from a different browser?
Some users cannot connect. Mostly on enterprise networks.
I’ve done the this test https://www.whynopadlock.com/results/2d52388e-f4ac-41a5-a24e-d5e10e0a001f
and got the error I mentioned.
If they’re on a corporate network, is it possible that their connection runs through a shared proxy? If so, that proxy may need to be updated. Do they get the same error when connecting to other sites like discourse.org or letsencrypt.org? If so, the issue is definitely on their end.
I think this ‘Why No Padlock?’ checker might be confused by yesterday’s Let’s Encrypt changes. Using a different scanner reports an A+ result for your site: SSL Server Test: frb.forumrossoblu.org (Powered by Qualys SSL Labs)