Hello support team, My Discourse page at https://wespenreboards.com/ is down. We can’t even pull up the login page. I have had a problem with certificates before, but that doesn’t seem to be the case this time. I ran the update commands in the DigitalOcean droplet console, but it did not solve the problem. cd /var/discourse git pull ./launcher bootstrap web_only && ./launcher destroy web_only && ./launcher start web_only I have attached a console screenshot and the Chrome page of what happens when I type in the forum URL. There are a lot of WARNINGS in the console text. Does that have anything to do with it? I am a novice on these things. Can someone help me with this, please? Thanks a lot, Wes Penre [chrome] [Screenshot 2024-08-10 114749]

[image] WesPenre: There are a lot of WARNINGS in the console text. Does that have anything to do with it? No, they’re harmless. Can you please post the full rebuild log?

Hi Richard. How do I copy and paste the entire console log? It can’t be done the normal way by just copying and pasting, apparently. Is there a simple way to copy and paste it?

I’m sorry, I can help you with debugging Discourse but not with something that seems an issue with your computer or with the Cloud platform that you’re using. Alternatively, you can scroll through the log and look for something that is an error, and screenshot that.

This was the only error message I found: [1]

You can still connect to the console? The site is nonresponsive, suggesting that it’s not got network connectivity. If discourse were down you’d still get a refused to connect message, not a timeout. You might restart the droplet. Open a ticket with digitalocean.com

OK. Will do! I’ll contact them. Thanks, Jay! Yes, I can connect with the console on the DigitalOcean site.

It gives only one ping. After that… nothing. So, I’m not sure Discourse is the issue, but something else. Is there some firewall on?

No, no firewall. Nothing has changed. The only thing I did was to run the following to make sure my certificate doesn’t run out: cd /var/discourse git pull ./launcher bootstrap web_only && ./launcher destroy web_only && ./launcher start web_only It was after that someone noticed the forum was down and emailed me. It’s unclear if it was running those commands that did it or if the forum was down before that. But I don’t know why running this would create this problem, though. I contacted DigitalOcean, and they sent me this: Hello Wes, Thanks for getting back in touch and for that additional information. What kind of console he used is not really relevant to what happened in our Droplet after he got there. I noticed you used the command “./launcher start up”. Instead, try the default command “./launcher start app”. If this does not work, you should reach out to your developer, because it would indicate that discourse was set up in a non-standard way, unique to him. I ran the start app and got the following msg: [3-1]

I don’t know anything about two container setup but as I see this you destroyed earlier app and if something goes wrong with rebuilding you can’t use old one. But… are those containers up and running?

My Discourse is down. Can't load anything

Product Support Self-hosting

WesPenre (WesPenre) August 10, 2024, 12:42pm 16

I ran the destroy/rebuild web_only again, and now it works, suddenly. I ran it twice earlier today to no avail. But not it works, which is great.

Thanks guys,
Wes

Topic		Replies	Views
Forum down, troubleshooting help needed Self-hosting	18	849	August 9, 2023
Discourse Went Down Suddenly. No one can log in Self-hosting two-container	22	1256	July 24, 2023
My Discourse is Down. Certificate Issue? Self-hosting	23	2294	February 22, 2023
I can't start a Discourse Self-hosting	42	2387	December 13, 2023
Discourse has stopped opening Self-hosting	36	6416	August 8, 2016

My Discourse is down. Can't load anything

Related topics