Question

"This site can’t be reached" domain

I’ve recently opened my host in my browser, but it fails to load. It has worked ever since I opened it, but not today. Here’s a picture of what happens: http://i.imgur.com/WQlpnfY.png

Does anyone know the issue? Like I said, it only started happening today. By the way, the domain is an IP.

Thanks


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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

@newvoids

Did you configure your Droplet or did you use a one-click image?

@newvoids

We’d really need more information about your setup and what has been done before we’d really be able to help diagnose the issue(s).

You can start by checking your error logs and seeing what’s showing up there. Since you’re tagging this post with Apache, let’s start there:

The following paths are based on standard paths used by Ubuntu’s package manager (apt), so if you’re not using Ubuntu, they may be a little different.

1). Apache’s error.log

tail -50 /var/log/apache2/error.log

2). System Logs

tail -50 /var/log/systemlog

3). PHP Logs

tail -50 /var/log/php*.log

If you can copy those to a Pastbin or screenshot each output, I can see if there’s an issue.

Also, if you can run

top

and take a screenshot of that as well.

My initial guess, baring any misconfiguration or configuration issues, Apache may have failed, didn’t restart, and now the site is down, which could be remedied by restarting Apache. We’d still need to find the root issue though.