Droplet created from a snapshot not working

  • Posted October 27, 2014

I have created a droplet from a snapshot of earlier working droplet(its a django app). When I open up the IP address in the browser it just doesn’t work. I don’t understand whats wrong. Any help?


You can see that for yourself, I have provided the IP address. Its says connection was rejected.

Are you sure that it has the old IP? That should not be happening. Did you used ifconfig to check the IP?

I think the problem is with IP address. is my newly allotted IP and that of sanpshot was When I ssh into my droplet it still shows

What happens exactly when you open the page in a browser? Do you get connection refused or an error message or just a blank page?

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!

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.

It’s not entirely clear from your question, but when you say that you SSH into the server and it still shows your old IP address, do you just mean in this message:

Thank you for using DigitalOcean's Django Application. 
We have created a default Django application that can be seen from 
You can use the following SFTP credentials to upload your files (using FileZilla/WinSCP/Rsync): 
User: django

Nginx listens on public IP ( port 80 and forwards requests to Gunicorn on port 9000 
Nginx access log is in /var/log/nginx/access.log and error log is in /var/log/nginx/error.log 
Gunicorn is started using an Upstart script located at /etc/init/gunicorn.conf 
To restart your Django project, run : sudo service gunicorn restart

If so, that should be a problem. That file is created when you launch a new Django “one-click application.” That is just your initial information. If you create a snapshot, that file is not updated. There is no way for it to know the new IP.

You problem is going to lay somewhere else most likely. Are you seeing any errors in /var/log/nginx/error.log ?

You should contact the Support, they are fast and verry helpfull!