I changer my domain that was pointing to one droplet to another but im now getting ERR_CONNECTION_REFUSED since more than an hour, if i go directly to the ip address it work: http://139.59.225.139/
my nginx file is simple as follow:
server {
listen 80 default_server;
listen [::]:80 default_server;
root /home/crashbdx/beta.sign-art.app/dist;
index index.html;
server_name beta.sign-art.app;
location / {
try_files $uri $uri/ /index.html;
}
allow 112.206.97.9;
deny all;
}
Any idea? can it be the propagation even if it a DNS/IP lookup show the correct IP ?
Subscribe
Share
Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Sign in to AnswerThese 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.
Hello, @crashbdx
Keep in mind that all DNS changes might take up to 48 hours in order to fully update. This is due to ISP DNS cache and general DNS propagating as well. This usually happens a lot faster but will still take at least few hours to fully update.
You can check the DNS records with our DNS tool: https://www.digitalocean.com/community/tools/dns.
You can also monitor the DNS propagation using this site: https://www.whatsmydns.net/
It will show you a DNS record check from various points around the world. This will help you to see if there is a DNS misconfiguration or if it’s just the DNS slowly updating.
The website is loading fine tested from my end. if you’re still experiencing problems to access the site I will recommend you to use alternative browser and different network if possible.
Hope this helps! Regards, Alex
Look like adding certbot/ ssl made it work, or the propagation ended after i did it :)