"This site can’t be reached"


(Auryn Macmillan) #1

Continuing the discussion from Connection Refused after DigitalOcean Droplet Upgrade?:

I’ve just finished a the setup of a new discourse instance on a fresh server running ubuntu 16.04, but for some reason I can’t seem to access the site in a browser (“This site can’t be reached” error in chrome) nor is the server returning pings (100% packet loss).

docker stats app shows the app running, and I have tried both restarting docker and rebooting the machine with no luck.

I have no issues using SSH to log in to the server remotely. Any help would be greatly appreciated.


(Jeff Atwood) #2

You followed our official install guide, to the letter?

  • Did you deviate in any way on any of the steps?

  • Did you add anything extra not listed in our steps?


(Auryn Macmillan) #3

not to the letter, it’s on an azure server. But other than that, yeah to the letter.


(Kane York) #4

And you’re pinging the same IP that you’re SSHing into?


(Auryn Macmillan) #5

yeah pinging the same server I was SSHing into, bizarre huh. Anyway, I’ve scratched that server and just spun one up on digitalocean for now. I’ll have another go with the original setup when it’s not time sensitive. Thanks for getting back to me though guys.