Ive completed lentsencrypt setup and its working good… but problem is, everything is ok until i try with www msg is “this server is not secured” how can i fix this?

You know what to do. Now you understand that the certificate must match the host name you want to use.

can you please, point me to the part of recert ? i do it with acme.sh, what command :smiley:

Edit: I thought that you were using the Discourse Let’s Encrypt module. If you used acme.sh, then just use it again and enter both host names as suggested below.

i did that, but when i tried to enter www.example.com, i got, this server is not secure, procedure… so next logical step is to reissue certificate and enter www.example.com instead of example.com how do i do that? root@crypto:/var/discourse# /var/discourse/shared/standalone/letsencrypt/acme.sh --cron --home “/var/discourse/shared/standalone/letsencrypt” [Mon Jan 30 23:20:32 UTC 2017] Renew: ‘example.com’ [Mon Jan 30 23:20:32 UTC 2017] Skip, Next renewal time is: Fri Mar 31 10:41:13 UTC 2017 [Mon Jan 30 23:20:32 UTC 2017] Add ‘–force’ to force to renew. [Mon Jan 30 23:20:32 UTC 2017] Skipped example.com [Mon Jan 30 23:20:32 UTC 2017] Renew: ‘www.example.com’ [Mon Jan 30 23:20:32 UTC 2017] Skip, Next renewal time is: Fri Mar 31 18:54:09 UTC 2017 [Mon Jan 30 23:20:32 UTC 2017] Add ‘–force’ to force to renew. [Mon Jan 30 23:20:32 UTC 2017] Skipped www.example.com from what i can see here, it skipped www.example.com ? [image] Screenshot Captured with Lightshot

do you have www in an A record on your dns? You must have a dns A record on your dns with www pointing to your ip address, some domain registrars/Zone records would automatically point www to your ip even if you don’t have www set as an A record, if that is the case it means there is a redirect, so if you put in your browser www.exmaple.com, your dns is redirecting it to you ip just on example.com, and because your server listens on port 80 and 443, any requests coming in would be served whether it was on www or example.com. Also from what I can see, with letsencrypt you need to do a new certificate issue and not a renew, with renew letsencrypt will check if the certificate you have is due for renewal if its not it will just exit and do nothing.

Thanks for clearing that for me, @dionbeukes tell me, should i totaly remove ssl from app.yml and rebuild to http… then start new procedure of SSL setup. Or there is a recert command with acme.sh ?

I’m following this thread and find that I have the same problem and the answers given here and elsewhere (after spending quite some time reading what’s on the forum) are really not clear to beginners like myself. A quick description of my setup and the issue: The discourse hostname (hosted on digital oceans) is example.com It has LetsEncrypt and this works fine when going to https://example.com On my DNS (which is hosted by dreamhost) I have an A record pointed to the digital oceans IP On my DNS I also have a CNAME record for * pointed to the same IP address Until I read this post I also had DNS record for A with www pointed to the same IP address I am having the same issue as the OP in that everything works perfectly for https://example.com and has a security warning for https://www.example.com Is the comment from @dionbeukes saying that the problem is likely to be the A record with www causing problems? I just want to clarify what is meant when you say “You must have a dns A record on your dns with www pointing to your ip address”. Is that as in “you must do this” or as in “this must explain why you have a problem”? Many thanks

Hi, Thanks for your email, Ive not been on the forum for a while, I don’t know exactly what your problem or issue is. If you explain in detail what hapoens and what doesn’t and what you want to achieve I will reply with an answer explaining exactly what you should and shouldn’t do.

Hi, Sorry, I read your post a few times. So your DNS is not the issue, because your subdomains and www all gets directed to the right ip address. The reason why you get a security warning for your www subdomain means the following. When a request gets directed to your server, depending on your settings, I presume you want all requests securely served. https://example.com works, but https://www.example.com gives a warning. You must list all your sub domains on letsencrypt. Either you must do a catch all meaning *.example.com etc, I don’t do that to minimise the possibility of random subdomiains getting sexurely served instead I list all of the sub domains I want securely served. www.example.com, shop.example.com etc etc, reissue your letsencrypt certificate with all the right subdomains and your warning will go away. I’m not sure if letsencrypt does a catch all certificate, rather specify each subdomain you want to be served by the same certificate. Hope my explanation is clear enough, Please email me again if you have more issues and your solution in the end.

Did you enable let’s encrypt in app.yml or did you run it yourself?

SSL working on root, but not on www

Product Support

pfaffman (Jay Pfaffman) Décembre 30, 2021, 3:14 30

Mise en place de Let’s Encrypt avec plusieurs domaines est une solution pour cela.

Sujet		Réponses	Vues
Problem in installing Let's Encrypt SSL for www and non-www Self-hosting	10	4977	Décembre 3, 2019
LetsEncrypt working without www, not with www Product Support	11	2151	Janvier 19, 2020
SSL is not valid for www.domain.com Self-hosting	22	866	Janvier 15, 2025
Non www to www without certificate error Self-hosting	13	2167	Janvier 17, 2022
Making 'www' work with Discourse Product Support	30	3047	Mai 15, 2020

SSL working on root, but not on www

Sujets connexes