Help troubleshooting hello world website - I can't see my site

Help
1

I have Caddy running on Digital ocean with hello world html website. From some reason I can’t see my website.
When I go to http://thecodingleague.com/ I see: “The domain thecodingleague.com is no longer parked by GoDaddy.” When I go to https://www.thecodingleague.com/ I see: “This site can’t be reached”.
Here is some more information:

A Records on digital ocean:

www.thecodingleague.com 138.68.2.56
thecodingleague.com 138.68.2.56

NS records:

thecodingleague.com ns1.digitalocean.com. Copy	
thecodingleague.com  ns2.digitalocean.com.	
thecodingleague.com ns3.digitalocean.com.

Caddyfile:

thecodingleague.com, www.thecodingleague.com {
    root /home/deploy/projects/home
    gzip
}

Output when running caddy:

Activating privacy features... done.
https://thecodingleague.com
https://www.thecodingleague.com
http://thecodingleague.com
http://www.thecodingleague.com
WARNING: File descriptor limit 1024 is too low for production servers. At least 8192 is recommended. Fix with "ulimit -n 8192".

ping thecodingleague.com

PING thecodingleague.com (50.63.202.32) 56(84) bytes of data.
64 bytes from ip-50-63-202-32.ip.secureserver.net (50.63.202.32): icmp_seq=1 ttl=52 time=43.1 ms
64 bytes from ip-50-63-202-32.ip.secureserver.net (50.63.202.32): icmp_seq=2 ttl=52 time=43.0 ms
64 bytes from ip-50-63-202-32.ip.secureserver.net (50.63.202.32): icmp_seq=3 ttl=52 time=43.5 ms
64 bytes from ip-50-63-202-32.ip.secureserver.net (50.63.202.32): icmp_seq=4 ttl=52 time=43.4 ms
64 bytes from ip-50-63-202-32.ip.secureserver.net (50.63.202.32): icmp_seq=5 ttl=52 time=43.2 ms
64 bytes from ip-50-63-202-32.ip.secureserver.net (50.63.202.32): icmp_seq=6 ttl=52 time=43.2 ms
64 bytes from ip-50-63-202-32.ip.secureserver.net (50.63.202.32): icmp_seq=7 ttl=52 time=43.1 ms

My digital ocean server is Ubuntu 16.04 and I use the Caddy personal version.

Shouldn’t I see my ip in the ping command? my server’s ip is 138.68.2.56.

Thanks!

2

DNS propagation either hasn’t reached you yet, or your computer has cached the DNS results locally.

You can use dig to issue a new DNS query. If it comes back with 138.68.2.56, you know your local host is caching the DNS and you’ll need to flush it (the method differs depending on your operating system).

If dig returns 50.63.202.32, it means your network provider’s chosen DNS resolver hasn’t been updated yet. Give it time, most DNS changes will fully propagate in under 12 hours but can take 24-48 under certain circumstances.

I like to dig @8.8.8.8 example.com to send my DNS query to Google’s public DNS, which is usually among the fastest to update.

2 Likes
3

Thank you! dig show me 50.63.202.32 which means I need to wait a bit longer. it’s already 24 hours but I’ll wait another day.

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.