Is this a discourse or dns issue

Поддержка Самостоятельное хостинг
1

I went through the installation on my Linux machine, I went thru the ./discourse-setup and all went well, it said it would take a few minutes for the bootstrap stuff to set up, I have my website setup to make the IP address of my VPS go to forum.origingaming.net I created that A Name around a day ago, whenever I go to my website it says:

# This site can’t be reached

**forum.origingaming.net**  is currently unreachable.

ERR_CONNECTION_FAILED

Is this due to me installing discourse wrong or is it an issue with my DNS?

2

‘A’ record looks fine … DNS seems to have propagated … the issue is on your server I suggest.

The HTML returned is showing some basic Ember.

Are you getting any build errors?

3

I haven’t got any errors

4

Should I try to rerun the ./discourse-setup and see if I get any errors?

5

Looks like there is some kind of firewall blocking connections on port 80 & 443.
are you sure those ports are open? where is your forum hosted?

6

I’m using SkySilk VPS, I’ll try to open those ports, don’t remember doing that

7

Ok, I allowed those ports via ufw, does that take time to update?

8

You allowed for incoming right?
It should be instant.
Though it still reports connection refused to me.

9

I did

ufw allow 84
ufw allow 443

In the terminal, is there something else I need to do?

It returned Rule Updated (v6) for both of them

10

What does it return with sudo ufw status

11

Status: inactive

(20 chars)

12

Should I enable it via sudo ufw enable?

13

So it’s not UFW! try contacting your customer support if they have some other network based firewall in place.
Ps: is your IP 64.190.xxx.xxx ??

Don’t complicate things by adding another variable, let it be disabled unless it is at least online.

14

Yeah my IP starts with that, I will contact customer support now, should I ask why ufw is disabled?

15

No, You should ask them if they block public connections over port 80 & 443 with some sort of firewall, and if Yes, how to allow connections to your IP/VPS?

16

Ok, asking right now, thanks for your help btw

17

I totally missed this, Apologies about it!

What are the outputs of:

sudo netstat -peant | grep ":80 "
sudo netstat -peant | grep ":443 "
18

It said netstat command not found

EDIT:
Installing net-tools rn so I can do i

EDIT:
Apparently I can’t post any more messages because I’m a new member, so I’ll just edit this

When I did the netstat for “:80 “ it returned nothing, same with 443

19

If the IP works but not the domain name it’s a dns problem.

20

Jay, not so sure … both domain and IP address are returning the same HTML for me.