My Discourse is Down. Certificate Issue?

Hi,

When people try to log in, depending on the browser, they get the following messages:

BRAVE:

This site can’t be reached

The webpage at https://wespenreboards.com/ might be temporarily down or it may have moved permanently to a new web address.

ERR_FAILED”

FIREFOX:

"Warning: Potential Security Risk Ahead

Firefox detected an issue and did not continue to wespenreboards.com. The website is either misconfigured or your computer clock is set to the wrong time.

It’s likely the website’s certificate is expired, which prevents Firefox from connecting securely. If you visit this site, attackers could try to steal information like your passwords, emails, or credit card details."

Has a certificate expired? If so, what do I do?

My URL is, wespenreboards.com/

Thanks,
Wes Penre

1 Like

Looks like your Let’s Encrypt cert expired today. I suggest reviewing the document below—especially the Debugging section:

1 Like

Hi Arman,

Thanks for the reference. Sorry, but this tech language is like Greek to me. I read the instructions, but I’m at a loss. Don’t even know where to start. I have no foreknowledge. Not sure what to do…

I didn’t even know I had a certificate. Isn’t there an easy way to just update it?

1 Like

How did you build your site at first?

2 Likes

I didn’t. A Discourse Support person built it for me. And I am hosted by Digital Ocean. But that person is no longer a Discourse Support person.

1 Like

I just noticed that my Discourse does not have an app.yml file, so I created one (see screenshot). However, the new yml file does not show up in the directory (again, see screenshot). What to do? Should I enter certain information to the file? If so, what should I add?

Hi @WesPenre :slight_smile:

If I remember rightly, you have a two-container set-up so you won’t have an app.yml, as neither of your containers are called app.

Have you done a rebuild of your Discourse recently? I think letsencrypt should use that as an opportunity to renew your certificates.

If you’re on a two-container set-up I think you can do this by using the ‘access console’ on your Digital Ocean droplet page for an easy way to SSH into your server, and then:

cd /var/discourse
git pull
./launcher bootstrap web_only && ./launcher destroy web_only && ./launcher start web_only
6 Likes

Thanks, JammyDodger! Running it now, and we’ll see what happens.

1 Like

It’s finished, but I still cannot log into wespenreboards.com/ .

1 Like

Seems to be working fine for me so far? Secure connection, plus I have just signed up to test and you should see me in the approval queue.

3 Likes

Yay! Now I see your request! Do you want me to make you an Admin, so you can check it all out?

1 Like

It seems like everything is working as intended, so you can probably just delete that test account. :slight_smile: I don’t think the admin UI will tell me anything useful in this case (though we can always sign me up for another one in the future if you need something else :+1:)

Though, just to check, is everything working as expected now?

2 Likes

OK, sounds good regarding your test account. I’ll delete it… I will check now if everything seems to work, and I’ll be back here…

2 Likes

Yes, it’s working again! I really, really appreciate this, JammyDodger. Thanks a lot!

2 Likes

Oh, one last question. Why did the certificate expire? Will it expire again in the future?

1 Like

Never mind… It seems like I should have upgraded to Beta 4 earlier and that was probably the problem.

2 Likes

yes it will :grin:

but rest assured, renewal should be automatic

6 Likes

There are also a couple of bits in this topic that you might find useful to keep your server uptodate:

Just remember that you don’t have an app.yml as you have a two-container set-up, so the commands in Step 2 would be the ones from above:

cd /var/discourse
git pull
./launcher bootstrap web_only && ./launcher destroy web_only && ./launcher start web_only
9 Likes

Very helpful, thank you!

3 Likes