Discourse SSL certificate empty

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. https://crt.sh/?q=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: vapingcommunity.co.uk

I ran this command:

It produced this output:

My web server is (include version): Digital Ocean

The operating system my web server runs on is (include version): Ubuntu 20

My hosting provider, if applicable, is: Digital Ocean

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):

I have possibly used up all my trys but in case there is something anyone can do, I'll post here, seems the SSL certificate is empty / not being served

1 Like

What command did you run?


I haven't, Discourse does it for you

1 Like

And why did it do it five times? Did it crash?


I didn't realise it would ask for a certificate every time I rebuilt the application

1 Like

Well... It shouldn't, if you save the certificate.

This is why you use the staging environment to make your experiments.

You'll have to wait for the rate limit to forget about you. (1 week since first issuance)


Ok, thanks for your help :+1:


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