The reason why Website on server cant be reached and solution

[Edison001]

During the visit, we may often encounter the situation where can not access the page. I believe that many people think that the network is dropped or server is a problem.but that is not the case after careful examination, in fact, the reason for this situation may be the DNS service fails. IE and other network settings are incorrect. Usually we encounter such a situation, how should we deal with it?

Firstly, determine whether it is routing problems.Beacuse the different places of the ISP have different DNS addresses, so there may be a router or network card that can not connect with the ISP's DNS service, if such a case, you can restart the router, replace one IP try.

Secondly, the network firewall issue, if the network firewall settings accidentally block access to IE into the list,that will be such a problem, we can directly turn off the firewall or decrease firewall security level and then see if it can recover.

Thirdly, there is a possibility that IE Trojan virus. If this happens, we have to download the software for killing.

Fourthly, we can download google browser to browse the Web, Google browser compatibility and safety factor is very high, and the temporary use less memory, open the Web page speed is very fast, very professional to browse websites in the world, but also comes with translation.

your ideas for the issues?

 

[FusedServers]

Connection/uplink, powera are main reasons servers are down. Oh forgot user error.

 

[whmcsguru]

This is one of those generic support things that is really, really hard to diagnose.

Start by using a proper browser. Chrome will give you the best description of why it can't get to the website. What does that say?

Take a look at the site's logs. cPanel, etc are very good about logging

Take a look through the server logs for the IP in question. Any blockages in there?

Take a look through the server logs for the service in question (usually http), any restarts, or issues there?

 

[MikeDVB]

Hard to know - every case is different.

I have run into a lot of weird issues over the years where a user's ISP was having issues whether it be routing or DNS.

That said DNS is most often the cause in my experience - usually missing a-records or misconfigured nameservers.

 

[24x7server]

It's mostly due to missing DNS records at your ISP's end. When you used to update the DNS records for your domain, then you'll need to make sure it's properly propagated at your ISP's end. Secondly, you can clear browser's and DNS cache.

But the provided scenario is indicating, it's totally an ISP's issue. When you'll face this trouble then first contact ISP. If there is no issue at their end, then you'll need to get in touch with your hosting provider for more details.

 

[technicalguy]

DNS is the most of the time guilty but sometimes it is nameservers misconfiguration.

 

[PeteCCS]

Hello,

When you can't browse a website and you think the issue might be between user computer and server, the best is to use tracert command line.
If possible the two ways, from your computer to your server and from your server to your computer.
This command will tell you where the packet is lost then you will know which one of your internet provider or your hosting company you have to contact.