My Discourse is down. Can't load anything

Installation
1

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
chrome791×492 10.7 KB

Screenshot 2024-08-10 114749
Screenshot 2024-08-10 1147491009×862 54.6 KB

2

No, they’re harmless. Can you please post the full rebuild log?

3

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?

4

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.

2 Likes
6

This was the only error message I found:

1
11018×391 14.8 KB

7

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

3 Likes
8

OK. Will do! I’ll contact them. Thanks, Jay!

Yes, I can connect with the console on the DigitalOcean site.

9

Nope. That’s not the one.

10

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?

11

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

12

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?

13

I don’t know. I don’t have a .yml for example–never did. I don’t even know what “two containers” entails. Any idea what to do next?

14

I have access to DIgitalOcean’s console and I can access the site through WinSCP.

15

Now I also got this from DigitalOcean:

I have reviewed the droplet and see that it is up and responding, however, the HTTP and HTTPS ports are currently closed.

> root@jump:~# nmap -Pn -p 22,80,443 69.55.54.86 Starting Nmap 7.80 ( [https://nmap.org](https://nmap.org/) ) at 2024-08-10 11:42 UTC Nmap scan report for [wespenreboards.com](https://wespenreboards.com/) (69.55.54.86) Host is up (0.23s latency). PORT STATE SERVICE 22/tcp open ssh 80/tcp closed http 443/tcp closed https Nmap done: 1 IP address (1 host up) scanned in 0.51 seconds

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

17

Basically nmap told to you that port for SSH was open — well, you knew it already. But ports 80 and 443 were closed. So no one could get in.

Why that happened… not the slightiest idea.

1 Like
18

Do you think it was “hacked?” I mean, is that theoretically possible in this case?

19

Everything is theoretically possible, but… no. Your droplet got some hickup and that’s why the firewall went down. Maybe Jay thought something like that and that’s why he suggested rebooting droplet. Or bootstrapping wasn’t succesful, but I don’t know how that could close those ports.

3 Likes
20

Thanks Jakke. Well, it’s up and running, so that is the most important. :slightly_smiling_face:

2 Likes