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

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

Hello everybody,
I have a problem with my droplet DSN configuration. Five days ago I bought a new domain on Godaddy and I set it up in order to point the droplet ip out by configurating the nameservers:
my domain: www.marcolorenzetti.dev droplet ip: 161.35.227.204
ns1.digitalocean.com ns2.digitalocean.com ns3.digitalocean.com
The propagation has gone well as I received an email by GoDaddy saying so, but as you can see, the requests to the domain above retrive a error (sometimes showing a 404 bad request).
What is weird is that I can reach out my website only by Tor browser (not always actually) and this is uncomprensible for me. Nevertheless, this suggest me that the problem is in my network configuration on Digital Ocean but I can’t figure out waht is it.
I belive I created a proper record on it, this is my download zone:
$ORIGIN marcolorenzetti.dev. $TTL 1800 marcolorenzetti.dev. IN SOA ns1.digitalocean.com. hostmaster.marcolorenzetti.dev. 1602252637 10800 3600 604800 1800 marcolorenzetti.dev. 1800 IN NS ns1.digitalocean.com. marcolorenzetti.dev. 1800 IN NS ns2.digitalocean.com. marcolorenzetti.dev. 1800 IN NS ns3.digitalocean.com. www.marcolorenzetti.dev. 3600 IN A 161.35.227.204 marcolorenzetti.dev. 3600 IN A 161.35.227.204
I also check out the server configuration, I added my new domain to the ip address already listed in my Nginx config file and in my settings.py file (it’s a django project).
Last but not least, I didn’t configurate the SSL standard certificate that was included in the package. Could it be the problem? I don’t think so.
Please someone help me.
009fd274aeae48f2bfbda6ef568676
Cloudstream Apk
Ruz
Ruz
Edward Sitarski
ebeecroft
dashan
34bcef38725b4e6eb5224ae028f17e
markatango
gouskova
Andrew J Montanus