Report this

What is the reason for this report?

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

Posted on April 17, 2018

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.**



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

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.

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.

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.