A question can only have one accepted answer. Are you sure you want to replace the current answer with this one?
You previously marked this answer as accepted. Are you sure you want to unaccept it?
Write for DigitalOcean
You get paid, we donate to tech non-profits.
Find and meet other developers in your city.
Contribute to Open Source
I have been wasted lot of my time because of droplet issue. Digitialocen team is working or sleeping?
Add comments here to get more clarity or context around a question. To answer a question, use the “Answer” field below.
Are you sure you have Ubuntu installed?
You can check for sure in the terminal by running the following command:
You can type !ref in this text area to quickly search our full set of tutorials, documentation &
marketplace offerings and insert the link!
Hi Everyone! I'm using [this](https://www.digitalocean.com/community/tutorials/how-to-serve-flask-applications-with-gunicorn-and-nginx-on-ubuntu-16-04) to deploy my flask app. However I'm running into a 502 Gateway Error. I have looked at several posts, and I have not found a solution.
I have already added the extra slashes in the .ini file:
and that didn't work. After checking the error logs, we found that we're getting a
"upstream prematurely closed connection while reading response header from upstream client". We're guessing that we need to increase the timeout, but that didn't work for us.
Any help would be appreciated!
This is the last code, and I can't use NGINX or nothing to have it serving :(
I have my personal site hosted at www.aaronbarfoot.com, on a domain purchased from Google domains. I followed the digital ocean tutorials to direct the droplet to the domain and setup ssh on the site and all has been running well for several days. Since yesterday the site has been not showing on safari. It went back on for a few hours last night. Then again this morning it was showing that the DNS server could not be found. Also on chrome the site only works with www and not when I visit aaronbarfoot.com. Are there any settings that I could change to fix this issue?
It looks like the doctl CLI does not support creation of a new droplet based on a snapshot. Is there any other way to achieve the same?
doctl compute droplet create <droplet-name> [droplet-name ...] [flags]
--enable-backups Backup droplet
--enable-ipv6 IPv6 support
--enable-private-networking Private networking
--format string Columns for output in a comma separated list. Possible values: ID,Name,PublicIPv4,PrivateIPv4,PublicIPv6,Memory,VCPUs,Disk,Region,Image,Status,Tags
--image string Droplet image (required)
--no-header hide headers
--region string Droplet region (required)
--size string Droplet size (required)
--ssh-keys value SSH Keys or fingerprints (default )
--tag-name string Tag name
--tag-names value Tag names (default )
--user-data string User data
--user-data-file string User data file
--volumes value Volumes to attach (default )
--wait Wait for droplet to be created