Interesting, the url sometimes redirects sometimes does not
It doesn’t, what’s happening is this:
https://www.fstdesk.com/xyz exists in DNS but no certificate exists -> INVALID
Chrome knows that there’s no certificate for www.fstdesk.com but has a feature called SSLCommonNameMismatchHandling which will check for a version without the www and redirect there.
If you try a different browser like safari you will also see the error for http://www.fstdesk.com/
Chrome effectively tricked you into believing you had a redirect which was failing in certain cases, where no redirect exists and instead a feature just made it look like some but not all https://www addresses were valid.
it works. .
Only in Chrome, look at Safari:
If we sidestep the browser completely and talk to your server using cURL we get:
* Server certificate: * subject: CN=fstdesk.com * start date: Jan 1 20:57:46 2019 GMT * expire date: Apr 1 20:57:46 2019 GMT * subjectAltName does not match www.fstdesk.com * SSL: no alternative certificate subject name matches target host name 'www.fstdesk.com'
So how can i add www.fstdesk.com for letsencrypt. Thanks for help.
Setting up Let’s Encrypt with Multiple Domains offers some hints, but it’s not exactly what you’re looking for. You’ll need to modify those instructions to do what you want.
thank you Jay Pfaffman
i can not solve the problem. any support please. Thanks
In my browser, there is no issue. I can easily browse over HTTPS non-www version.
Did I missed anything?
Problem is with https://www.fstdesk.com
4 Oca 2019 Cum 21:19 tarihinde Ultra Noob via Discourse Meta email@example.com şunu yazdı:
As a normal user, everything seems fine to me.
What exactly are you expecting to achieve? Sorry, I didn’t get anything.
try below link please. still there is problem
Use something other than Chrome
same on Pale Moon…
You have a typo in the URL. (the ! exclamation point before the “l” in login).
Also, even with the correct URL, Safari is giving an invalid certificate warning.
it is an old link which used before discourse with another script.
How can i solve this issue ? Must i install letsencrypt again with www version of my domain ? or …
Personally I would use a registrar redirect for either @ or www and forget about the https edge case.
Just pick whichever you have used in the past or publicised and stick with it.
You can go to the trouble of editing the yml, issuing a SAN cert and configuring redirects but it’s rarely truly necessary.
Yes. If you want https to work for multiple host names you have to reconfigure let’s encrypt as I suggested above.
I’ve done it before but as suggested above unless you have published another https address that you now want to change it’s largely unnecessary.