Hey guys,
Just finished installing fresh discourse on a fresh subdomain on Ubuntu 22.04 LTS, with NO errors at all but got this instead of the login page:
Any ideas what went wrong??
Are you sure your dns has propagated?
1 Like
Yes, they’re pointing to correct sub besides, I’ve used this subdomain before a few weeks ago and wanted to reuse it again but had that on my face instead of the real site 
Maybe you have both the old and the new DNS entry?
1 Like
Sorry for the late reply and to follow up on this issue, I ran the command:
v-list-sys-ips
and it came up with:
IP MASK NAT STATUS WEB DATE
172.17.0.1 255.255.0.0 no shared 0 2022-11-09
15.96.43.123 255.255.255.0 no shared 2 2022-11-09
The problem is with the second IP is taking over the 2 domains.
How can I put discourse on the first IP and leave the other web-server as it is on the second one??
I also, ran these and came up good or ok:
nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successfulapachectl configtest
Syntax OK
Any help would be appreciated greatly 
That isn’t the problem here at all.
Your server doesn’t have two external IP addresses, it has two IPs in different networks. The first (172.x) is part of a private IP range and it isn’t addressable externally.
The second is the public IP assigned to your server. Your applications are correctly attached to the externally addressable IP.
To make this work you’re going to need to proxy Discourse behind the other web server, there are guides here on meta on doing this. For now I would disable the other web server and focus on getting Discourse running to your satisfaction, then configure the proxy.
1 Like