Shifted droplet by snapshot but even after entering the same records cannot access my website .DNS problem or need to do changes in droplet?

April 17, 2018 308 views
Nginx Applications DNS Control Panels Networking Ubuntu 16.04

I'm sorry for wrong IP address on the previous question so here I ask it properly. I have accepted your answer in previous question.I have updated my new IP address at bigrock and in my droplet record. So, here is my question.

We recently created a droplet out of snapshot that we had from another account. Since our client wants to access from new DO account. We shifted it to a new account by a snapshot. So, I created a snapshot and I filled in all the record entry same as they were on the other account.(All information is same and except the obvious IP address )

I have purchased my domain name from "bigrock.in" , I also edited my IP address in the record type "A" there.

What else do I need to do to make my website running again?
even a little idea would be great.

I also restarted nginx on this droplet.

These are my records if it helps(there are two txt files too which I haven't included here )

**CName | HOSTNAME - www.aksout.com | value - aksout.com.

CNAME | HOSTNAME - email.aksout.com | Value - mailgun.org.|

MX | HOSTNAME - aksout.com | VALUE- mxa.mailgun.org.

MX | HOSTNAME - aksout.com | VALUE - mxb.mailgun.org.

A | HOSTNAME - aksout.com | Value - 139.59.36.53

NS | aksout.com|ns2.digitalocean.com.

NS | aksout.com|ns3.digitalocean.com.

NS | aksout.com|ns1.digitalocean.com.**

1 comment
  • Due to urgent requirements, I would be happy even if I can just access my website with my IP. Just want it to fix, need help urgently. Thank you in advance, I really appreciate any kind of help

2 Answers
theonlysaxena April 18, 2018
Accepted Answer

I'm writing my own answer. The firewall was blocking the 443 .

Ok. Your DNS records appear to be resolving correctly based on the information here. Your server at 139.59.36.53 however, while responding to ping requests is not responding to web requests.

I would recommend logging into your droplet via SSH (This service appears to be up and running) and attempt to start or restart your web service with:

service nginx restart;

If the service fails to start, check the log file at /var/log/nginx/error.log for more information on what problem was encountered.

Have another answer? Share your knowledge.