Cant access a specific website

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › Cant access a specific website

martyyn

1971 posts

Uber Geek

ID Verified

#140853 22-Feb-2014 15:01

I wasn't sure where to put this but this seemed the most appropriate forum.

I was merrily exploring a friends website with windows in Chrome on the site, their cpanel and their webmail. I tried to log into the whm and it timed out. Then the other three all errored as well. I didnt change anything, I was just looking, honest :)

Chrome just tells me 'Oops! Google Chrome could not connect to'.

I can get anywhere else I like but not this one site. Down for everyone tells me it's up too and my phone on 3G can connect to it so its obviously something local.

I have rebooted the PC, rebooted the switch/router it's connected to, rebooted the Thomson router, cleared the cache/cookies etc, tried ipconfig /flushdns, tried FF but still nothing. It's the same with the other PC's, none of them can see it either.

What have I done locally to break it ?

dwl

371 posts

Ultimate Geek

#992355 22-Feb-2014 15:28

Perhaps it is a DNS issue with record in limbo from your ISP connection DNS servers. Have you compared IP addresses returned from local vs others that work?

martyyn

1971 posts

Uber Geek

ID Verified

#992357 22-Feb-2014 15:32

I understand what you're saying, but how do I check them ?

When I ping the address I get a Request timed out. Pinging other sites is fine.

They have just had a server upgrade (via digiweb) and they asked me to check everything after the migration. I didnt get very far before I couldnt access it. But the ping is the new server address. The migration was a couple of days ago and I've had no trouble checking their site this week, until now.

dwl

371 posts

Ultimate Geek

#992365 22-Feb-2014 15:50

martyyn: I understand what you're saying, but how do I check them ?

When I ping the address I get a Request timed out. Pinging other sites is fine.

They have just had a server upgrade (via digiweb) and they asked me to check everything after the migration. I didnt get very far before I couldnt access it. But the ping is the new server address. The migration was a couple of days ago and I've had no trouble checking their site this week, until now.

I assume that if it is timing out you are getting an IP address returned for the hostname. The question is whether it is the same IP address from locations that work and don't work. Using ping example which reveals IP address:

C:\Windows\system32>ping stuff.co.nz
Pinging stuff.co.nz [203.57.145.102] with 32 bytes of data:

Is the IP address consistent across devices from different locations? The mention of a "new server address" might be an issue.

martyyn

1971 posts

Uber Geek

ID Verified

#992367 22-Feb-2014 15:54

Pinging the host/domain name (which returns the new ip address) gives me request timed out errors.
Pinging the new ip address gives me request timed out errors.

Pinging the old ip address returns no with no errors at all.

I've just tried to log into the old server with /cpanel at the end and I can log in with no problems. Same with using /webmail.

I wonder if this means they are doing something with it at the moment.

Cheers

webwat

2036 posts

Uber Geek

Trusted

#992489 22-Feb-2014 18:26

The new server may not be pingable. Do you get a web page from the same server when you put the IP address into Chrome? Put that IP address into your phone and see if you get any web page. To confirm that its a DNS problem, try putting your primary DNS as 8.8.8.8 into your computer's network settings for a while. Thats the google DNS, and your current DNS should return the same IP address as that. Slingshot had some DNS issues recently...

Time to find a new industry!

dwl

371 posts

Ultimate Geek

#992531 22-Feb-2014 19:45

If you are now getting consistent results from different places then more likely the server end. If you still have some different responses from different places (e.g. other device locations will work with hostname/new IP address) then it could be more complicated.

The web is getting more confusing with CDNs and Cloud service providers. For example the same hostname might return different IP addresses from different locations simply because the server has been linked to a cloud provider. When changes are being made it is often interesting to see the global view from DNS propagation checkers like this tool although there is only one node in NZ. And anycast is another story...

Hope you get it sorted.

edit: grammar

mattwnz

20164 posts

Uber Geek

#992544 22-Feb-2014 20:37

Sounds like a problem with the hosting and they are blocking your IP. Some of the cheap ones may automatically block the IP if it detects something not normal. Is it hosted overseas? I would contact the host for support.

Sharesies

Trade NZ and US shares and funds with Sharesies (affiliate link).

martyyn

1971 posts

Uber Geek

ID Verified

#995745 27-Feb-2014 19:18

mattwnz is on the ball.

It turns out I had incorrectly entered a password when trying to access the WHM (which I was already in the site , cpanel and webmail) and it locked me out for 24 hours !

dwl

371 posts

Ultimate Geek

#995783 27-Feb-2014 20:36

martyyn: mattwnz is on the ball.

It turns out I had incorrectly entered a password when trying to access the WHM (which I was already in the site , cpanel and webmail) and it locked me out for 24 hours !

Thanks for following up with the cause. 24 hours is a long time to wait.

mattwnz

20164 posts

Uber Geek

#995865 27-Feb-2014 21:54

martyyn: mattwnz is on the ball.

It turns out I had incorrectly entered a password when trying to access the WHM (which I was already in the site , cpanel and webmail) and it locked me out for 24 hours !

That doesn't sound right for you to be locked out for 24 hours simply for entering a incorrect password. It should have redirected you to a page explaining that you had been locked out, so you could get it unlocked..

martyyn

1971 posts

Uber Geek

ID Verified

#999452 5-Mar-2014 13:49

It may not have been 24 hours, but I tried it the next day and it was all fine. When I asked they said it was a temporary block because I'd entered an incorrect password a couple of times and they had noticed I wasn't the usual person/IP logging in.

I will have to pay more attention to my typing !