Question

Unable to access my domain "This site can't be reached"

I’ve setup my DO server with nginx. I was able to access the url www.jan-xv.online yesterday. I need help in figuring it out as to why I would get # This site can’t be reached whenever I go to my url www.jan-xv.online


Submit an answer


This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

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.

Bobby Iliev
Site Moderator
Site Moderator badge
August 20, 2024
Accepted Answer

Hi there,

As far as I can see you are getting a connection refused on both port 80 and 443.

This is usually caused by either your webserver not running or your firewall blocking the access to those ports.

What you could do is to follow the steps from this guide here on how to troubleshoot common Nginx problems, and mainly:

  1. Check Your Nginx Server Status:

    • Ensure that your Nginx server is running properly. You can check the status with the following command:

      sudo systemctl status nginx
      
    • If Nginx is not running, you can start it with:

      sudo systemctl start nginx
      
    • If there are errors in the Nginx configuration, you can test the configuration to see if there are issues:

      sudo nginx -t
      

      Feel free to share the output of the above commands if you need further assistance.

  2. Check Firewall Rules:

    • Ensure that your server’s firewall isn’t blocking HTTP/HTTPS traffic. You can check the firewall rules using:
      sudo ufw status
      
    • If HTTP (port 80) and HTTPS (port 443) are not allowed, you can allow them using:
      sudo ufw allow 'Nginx Full'
      
  3. Check DNS Settings:

    • Verify that your domain’s DNS settings are correctly pointing to the correct IP address of your DigitalOcean Droplet. You can use a tool like DNS Checker to see if the DNS propagation is complete.
  4. Check the Droplet’s IP Address:

    • Make sure the IP address (209.38.17.137) is correct and matches the one configured in your DNS settings.
  5. Check Server Logs:

    • Look at the Nginx logs for any errors that might provide a clue:
      sudo tail -f /var/log/nginx/error.log
      
    • This log might indicate issues with your server’s configuration or other problems.

Let me know how it goes!

- Bobby

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Featured on Community

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
Animation showing a Droplet being created in the DigitalOcean Cloud console