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 --…

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 …

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 dig…

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 sett…

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

SSL working on root, but not on www

Ondersteuning

pfaffman (Jay Pfaffman) 30 december 2021 om 15:14 30

Setting up Let’s Encrypt with Multiple Domains is a solution for this.

Topic		Antwoorden	Weergaven
Problem in installing Let's Encrypt SSL for www and non-www Self-hosting	10	4800	3 december 2019
LetsEncrypt working without www, not with www Support	11	1923	19 januari 2020
SSL is not valid for www.domain.com Self-hosting	22	515	15 januari 2025
Non www to www without certificate error Self-hosting	13	1914	17 januari 2022
Making 'www' work with Discourse Support	30	2442	15 mei 2020

SSL working on root, but not on www

Gerelateerde topics