Report this

What is the reason for this report?

ERR_NAME_NOT_RESOLVED Error

Posted on July 15, 2018
3166

By 3166

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
                        
                }
}

The developer cloud

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

Start building today

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