Featured AI Products
Compute
Build, deploy, and scale cloud compute resources
Containers and Images
Safely store and manage containers and backups
Managed Databases
Fully managed resources running popular database engines
Management and Dev Tools
Control infrastructure and gather insights
Networking
Secure and control traffic to apps
Security
Help protect your account and resources with these security features
Storage
Store and access any amount of data reliably in the cloud
Browse all products
AI/ML
CMS
Data and IoT
Developer Tools
Gaming and Media
Hosting
Security and Networking
Startups and SMBs
Web and App Platforms
See all solutions
Community
Documentation
Developer Tools
Get Involved
Utilities and Help
Become a Partner
Marketplace
Pricing

- Community
- DigitalOcean
- Community
- DigitalOcean

"The site can't be reached" on my friend's computer

Posted on January 30, 2017

Hi. I created a portfolio website but one of my friends can’t access it and the error says “This site can’t be reached. www.iamraymund.com took too long to respond”.

I asked my other friends but the website is working on their side. I test it also to the other geographical location using geopeeker, it is working fine as well.

I checked ufw setting but http traffic was already enabled in port 80. Does it have anything to do with it?

What could be the problem?

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!

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.

Jonathan Tittle

January 30, 2017

Accepted Answer

@iamraymund

Your website is definitely active on my end as well – loaded pretty much instantly.

How long as it been since you set the DNS for your domain? In some cases, it can take anywhere from just a few minutes up to 24-36 hours for DNS to fully resolve.

Looking beyond DNS, are they able to connect to any other websites without issues? It’s not all that uncommon to see ISP’s heavily caching pages that have been previously visited. If they’ve visited your site before on another provider and then revisited on the new, they may simply need to flush their cache and/or restart their modem. It seems trivial, but it’s common with a lot of ISP’s.

Given that I can access the site on my end, that tells me that your web server is responding to requests on Port 80 (HTTP), so it doesn’t seem like there’s any real issues other than potentially a local issue for your friend.

The developer cloud

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

View all products

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.