New Discourse forum www domain is not SSL certified

Help
21

Here are some of the ACME Clients ACME Client Implementations - Let's Encrypt

Actually

is a web server.

And

is an Operating System.

3 Likes
22

Sorry, how can I check via console?

23

Please see this link Set up Let’s Encrypt with multiple domains / redirects - #82 by JimPas - Sysadmins - Discourse Meta I think it will help, and this too Set up Let’s Encrypt with multiple domains / redirects - #95 by JimPas - Sysadmins - Discourse Meta

I am getting the feeling that under the covers Discourse is using https://certbot.eff.org/ and the relevant documentation would be User Guide — Certbot 3.1.0 documentation

2 Likes
24 
Requesting a certificate for www.bloxburg.com
Encountered exception during recovery: certbot.errors.MisconfigurationError: nginx restart failed:
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Unknown error)
nginx: [emerg] bind() to [::]:80 failed (98: Unknown error)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Unknown error)
nginx: [emerg] bind() to [::]:80 failed (98: Unknown error)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Unknown error)
nginx: [emerg] bind() to [::]:80 failed (98: Unknown error)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Unknown error)
nginx: [emerg] bind() to [::]:80 failed (98: Unknown error)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Unknown error)
nginx: [emerg] bind() to [::]:80 failed (98: Unknown error)
nginx: [emerg] still could not bind()
nginx restart failed:
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Unknown error)
nginx: [emerg] bind() to [::]:80 failed (98: Unknown error)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Unknown error)
nginx: [emerg] bind() to [::]:80 failed (98: Unknown error)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Unknown error)
nginx: [emerg] bind() to [::]:80 failed (98: Unknown error)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Unknown error)
nginx: [emerg] bind() to [::]:80 failed (98: Unknown error)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Unknown error)
nginx: [emerg] bind() to [::]:80 failed (98: Unknown error)
nginx: [emerg] still could not bind()

Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

What should I do? I requested but it failed.

25

At this point kindly wait for more knowledgeable Let's Encrypt community volunteers to assist. :slight_smile:

3 Likes
26

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.

Requesting a certificate for www.bloxburg.com
Encountered exception during recovery: certbot.errors.MisconfigurationError: nginx restart failed:
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Unknown error)
nginx: [emerg] bind() to [::]:80 failed (98: Unknown error)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Unknown error)
nginx: [emerg] bind() to [::]:80 failed (98: Unknown error)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Unknown error)
nginx: [emerg] bind() to [::]:80 failed (98: Unknown error)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Unknown error)
nginx: [emerg] bind() to [::]:80 failed (98: Unknown error)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Unknown error)
nginx: [emerg] bind() to [::]:80 failed (98: Unknown error)
nginx: [emerg] still could not bind()
nginx restart failed:
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Unknown error)
nginx: [emerg] bind() to [::]:80 failed (98: Unknown error)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Unknown error)
nginx: [emerg] bind() to [::]:80 failed (98: Unknown error)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Unknown error)
nginx: [emerg] bind() to [::]:80 failed (98: Unknown error)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Unknown error)
nginx: [emerg] bind() to [::]:80 failed (98: Unknown error)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Unknown error)
nginx: [emerg] bind() to [::]:80 failed (98: Unknown error)
nginx: [emerg] still could not bind()

Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
27

Hi @vhp100,

Please show the output of each of the following commands

  • sudo certbot --version
  • sudo certbot certificates
  • sudo nginx -T that is a capital T
3 Likes
28

@vhp100 Please do not start new threads for the same problem. It is helpful to know the history for anyone who wishes to help. I moved your new thread to this one.

4 Likes
29

Also here is a recent Discourse community topic that seems relevant SSL is not valid for www.domain.com - Installation - Discourse Meta

2 Likes
30

Why do you want www.domain to be covered? Your Discourse server should already be running on a subdomain of bloxburg.com, not the apex domain. See:

Select a subdomain such as discourse.example.com or talk.example.com or forum.example.com for your Discourse instance.

...and if you're doing that, you wouldn't want www.talk.bloxburg.com anyway.

It has everything to do with Discourse, because Discourse by default obtains and manages your certificate.

5 Likes
31

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.