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.

Hi,
I had this working fine before, but then I tried to get HTTPS working. I obtained a valid certificate, but It wouldn’t load, so I removed the HTTPS settings in the Nginx file to try and just get the site to load again. My website is northvillelandscapes.com and I am receiving a ERR_NAME_NOT_RESOLVED when I attempt to visit the site. The Nginx file reboots with an OK
DNS settings on DO:
A
northvillelandscapes.com Copy directs to
165.227.113.170 Copy
3600 Copy
A
www.northvillelandscapes.com Copy directs to
165.227.113.170 Copy
3600 Copy
Here is the Nginx file that loads fine.
server {
listen 80 default_server;
listen [::]:80 default_server;
root /srv/www/northvillelandscapes.com/html;
index index.html index.htm;
# Make site accessible from http://localhost/
server_name northvillelandscapes.com www.northvillelandscapes.com;
location / {
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
try_files $uri $uri/ =404;
# Uncomment to enable naxsi on this location
}
}
009fd274aeae48f2bfbda6ef568676
Cloudstream Apk
032f50ee7f7d489db3b05e204fe139
032f50ee7f7d489db3b05e204fe139
Edward Sitarski
ebeecroft
dashan
34bcef38725b4e6eb5224ae028f17e
markatango
gouskova