My SSL is not valid for www.domain.com but it is with domain.com How would I make it secure with www? I have the free SSL you get upon self hosting discourse

Because it is created only for apex, or you are referring it wrong where ever you are trying to terminate it. [图片] good: I have the free SSL you get upon self hosting discourse Discourse creates SSL when installed. And it’s by Lets Encrypt. So perhaps you should ask from what ever company now gave it to you. I don’t totally understand why to bother.

Because when you visit www.mysite.com, it prompts with “This site is unsecure, do you wish to continue” type of message, then it redirects to the SSL version (https). I’ll ask Lets Encrypt on any solutions.

You have to create it for www too. If you create it by manually you have to use something like certbot certonly --nginx -d domain.com -d www.domain.com. Basically every sub-domain needs its own. I don’t know how it is now, but wildcard certificate (same for apex and every subdomains) didn’t work too well when created using Lets Encrypt. But again. You don’t need to worry that, because Discourse does it for you — except if your DNS settings are wrong or some other reason when your forum is unreachable.

Sorry I don’t exactly understand, DNS works fine I guess, its just a URL redirect. www → https://domain.com this part says www.domain.com doesn't support a secure connection You are seeing this warning because this site does not support HTTPS But when using domain.com its fine. Should I try certbot certonly --nginx -d domain.com -d www.domain.com?

I don’t know what you should try, Idon’t even know what you are trying to do, how and where. All I try to say is: you need different certificates for apex and www, or your sites in web server are configurated wrong you don’t need to do anything because Discourse creates SSL certificate for you when setting up a forum

There’s a topic on this: [图片] 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…

Thank you. after_ssl: # tell letsencrypt what additional certs to get - replace: filename: "/etc/runit/1.d/letsencrypt" from: /--keylength/ to: "-d site.com -d www.mysite.com --keylength" - replace: filename: "/etc/runit/1.d/letsencrypt" from: /--fullchainpath/ to: "-d site.com -d www.mysite.com --fullchainpath" So this should make the www go to mysite.com? Or is it the opposite way around?

No. It gives to you two certificates. One for apex, one for www.

If your hostname is site.com then you have it right. And that seems to be the case. It’s generally recommended that your site be at www.site.com and have the apex domain redirect to the www. What I would do is change your hostname to www.site.com and do it the other way around. [图片] Jakke Flemming: It gives to you two certificates. One for apex, one for www. I think that it gives one certificate that is valid for both.

Hello, I am bumping this because I thought I fixed it yesterday, but now when accessing www.mysite.com I am getting a non SSL redirection still. The apex has a SSL, just not www. Even though I applied this in my app.yml in hooks: after_ssl: # tell letsencrypt what additional certs to get - replace: filename: "/etc/runit/1.d/letsencrypt" from: /--keylength/ to: "-d mysite.com -d www.mysite.com --keylength" - replace: filename: "/etc/runit/1.d/letsencrypt" from: /--fullchainpath/ to: "-d mysite.com -d www.mysite.com --fullchainpath"

SSL 对 www.domain.com 无效

产品支持安装

merefield (Robert) 2025 年1 月 10 日 17:44 9

有一个关于这个的帖子：

话题		回复	浏览量
Problem in installing Let's Encrypt SSL for www and non-www Self-hosting	10	4963	2019 年12 月 3 日
SSL working on root, but not on www Product Support	28	4692	2021 年12 月 30 日
LetsEncrypt working without www, not with www Product Support	11	2130	2020 年1 月 19 日
Non www to www without certificate error Self-hosting	13	2147	2022 年1 月 17 日
About force www to non www Product Support	29	3085	2019 年1 月 6 日

SSL 对 www.domain.com 无效

相关话题