Going to my domain (new-world.online) brings up:

Unable to connect
Firefox can’t establish a connection to the server at new-world.online.

Pinging it on CMD-Promt brings up:
Reply from bytes=32 time=91ms TTL=54

On my GoDaddy domain the hostnames are set to:
I’ve left them 48 hours GoDaddy has confirmed they’ve been updated.

I’ve set @ to go to my droplet IPv4. And my CName * to point to my domain (@)
All set.

Typing in the IP:
Works and takes you to my site using the reverse proxy.
The reverse proxy has the domain set as new-world.online and is listening on 80 and connecting to the node app on port 8080.

I know this works because works and not only proving the proxy works and it’s the domain:

$ORIGIN new-world.online.
$TTL 1800
new-world.online. IN SOA ns1.digitalocean.com. hostmaster.new-world.online. 1467468106 10800 3600 604800 1800
new-world.online. 1800 IN NS ns1.digitalocean.com.
new-world.online. 1800 IN NS ns2.digitalocean.com.
new-world.online. 1800 IN NS ns3.digitalocean.com.
new-world.online. 1800 IN A
.new-world.online. 1800 IN CNAME new-world.online.


These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

1 answer

@maydongs - First, make a CNAME record in your DNS for www with value new-world.online. In addition or alternatively, you could also make a catch-all CNAME record of * (that’s a star character) to handle all subdomains. Next, you need to modify your nginx server block to have a server_name value with both new-world.online and www.new-world.online, then restart nginx. Good luck.

Submit an Answer