Hello, I have a site and the bloxburg.com is certified, but www.bloxburg.com is not.
I am using Discourse and have a Ubuntu 22.04.5 LTS.
(edited to use actual domain name)
Hi @vhp100, did you request both domain names (i.e. the with www and the without www)?
2 Likes
Hey, I registered without www im pretty sure, but I think there's 2 certificates on the server.
If you can give instructions on what to do to apply it to www or a way to check that'll be great help.
Thanks.
1 Like
We won't be able to give specific advice without more info from you. Please answer as much as you can from the form you should have been shown when posting in Help.
Also note that domain.com is a valid domain. But, I am guessing probably not yours. Please do not use other peoples domains. Use example.com if you must but actual domains allow us to be more thorough.
========================
Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
3 Likes
My domain is: bloxburg.com
I ran this command: Discourse setup set it up automatically
My web server is (include version): Ubuntu 22.04.5 LTS.
I can login to a root shell on my machine (yes or no, or I don't know): Yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel): No
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): N/A, don't have certbot installed. But Discourse gives a free Lets Encrypt on the setup.
1 Like
@MikeMcQ If you need any more details let me know
1 Like
Sorry, I misunderstood your original post. This is probably a better question for the Discourse forum.
Did you follow these instructions: Install Discourse in production with the official supported instructions - Self-Hosting - Discourse Meta
Those instructions also suggest where to best get help with any problems.
Some volunteer(s) here may help anyway. I never setup a Discourse forum so can't offer specifics.
3 Likes
I've tried all discourse help threads.
Are there not any simple commands that I can give SSL certificate to WWW? Or if I wanted to attach a different SSL certificate to it, how would I do that?
Getting a cert is one thing. Configuring your web service (in this case Discourse) to use it is quite another. As I understand it, Discourse handles all of that for you.
Running a forum is fairly involved with a significant learning curve. You would do well to start out with a reliable standard install.
2 Likes
What is a reliable standard install? So the instructions really differ from a normal site and discourse?
I have access to the console, I've been trying to fix this for a week now, I don't know why its so hard to make WWW with SSL.
Hi @vhp100,
Here is a list of issued certificates crt.sh | bloxburg.com
Previously you had requested wildcard certificates which would cover bloxburg.com and *.bloxburg.com (that would cover www.bloxburg.com).
But recently certificates are only for bloxburg.com and that does not cover www.bloxburg.com.
3 Likes
Hello, thank you, what are the solutions to cover www?
Either of these should do it.
- Add back the wildcard domain
*.bloxburg.comin addition to the already presentbloxburg.com - Add the domain
www.bloxburg.comin addition to the already presentbloxburg.com
2 Likes
Technically I don't know how to do this, the wildcard wasn't setup for me. It was the landing page for the domain by Namecheap.
the www. has a A record pointing to the server IP address, but that doesn't have a SSL.
Can you instruct on what to do further please? Some commands/technical info to make it work for WWW would be really helpful, thank you.
Sadly NO; I've never setup Discourse.
Adding to Mike's comment
I suggest looking to
- Getting Started with Discourse - Part 1: Discourse Setup Getting Started with Discourse - Part 1: Discourse Setup
- And their community forum https://meta.discourse.org/
3 Likes
This has nothing to do with Discourse, can I have instructions just like any other Lets Encrypt configuration for the subdomain www?
What ACME client is being used?
3 Likes