Inaccessible Page

Started by dlorde, May 22, 2010, 20:55:51

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

Gary

It works fine here as well
Damned, if you do damned if you don't

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Gary

Maybe the Russian mafia are now collecting IP addresses as we try to visit that page  :eek4:
Damned, if you do damned if you don't

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Bill

A few replies- OK on NTL Cable, EasyNet and Be, not on BT.

Looks like a routing problem?
Bill
BQMs-  IPv4  IPv6

Gary

Quote from: Rik on May 23, 2010, 11:09:23
Proxy time! :)
a fine idea, although I didn't see the r when I first read that  ;D
Damned, if you do damned if you don't

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Bill

OK on Plusnet and TalkTalk (That's a switch!)
Bill
BQMs-  IPv4  IPv6

Rik

Quote from: Bill on May 23, 2010, 11:12:04
Looks like a routing problem?

I'd expect that to affect everyone, though, Bill.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Bill

Quote from: Rik on May 23, 2010, 11:13:54
I'd expect that to affect everyone, though, Bill.
Sorry, I meant "A problem with a router", that only a few people are going through.

I don't know much about routing  ???
Bill
BQMs-  IPv4  IPv6

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

I've alerted support to this thread.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Bill

Thought I'd already posted this...

traceroute confluence.jetbrains.net
traceroute to confluence.jetbrains.net (184.73.234.255), 64 hops max, 52 byte packets
ec2-184-73-234-255.compute-1.amazonaws.com (184.73.234.255)  0.807 ms  0.342 ms  0.317 ms


Where did that IP come from, and what happened to the steps in the middle, eg my router?

If I use the IP given earlier (that resolves correctly in the address bar):

traceroute 89.163.94.178
traceroute to 89.163.94.178 (89.163.94.178), 64 hops max, 52 byte packets
1   (192.168.1.1)  0.764 ms  0.321 ms  0.244 ms
telehouse-gw4-lo2.idnet.net (212.69.63.99)  27.013 ms  26.675 ms  26.785 ms
telehouse-gw3-g0-1-400.idnet.net (212.69.63.243)  175.559 ms  153.491 ms  53.871 ms
te312-1188.brc4.spb.obit.ru (79.142.92.100)  64.995 ms  65.759 ms  66.351 ms
gw-cust-webplus.obit.ru (217.79.3.74)  70.707 ms  64.618 ms  65.336 ms
6  195.131.253.3 (195.131.253.3)  65.516 ms  65.093 ms  65.039 ms
gw.intellij.net (195.5.138.42)  66.450 ms  65.791 ms  66.252 ms
8  * * *
Bill
BQMs-  IPv4  IPv6

Rik

I get this, Bill:

tracert 89.163.94.178

Tracing route to mail2.intellij.net [89.163.94.178]
over a maximum of 30 hops:

 1     2 ms    <1 ms     1 ms  192.168.1.254
 2    14 ms    15 ms    14 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
 3    13 ms    11 ms    13 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 4    53 ms    53 ms    51 ms  te312-1188.BRC4.spb.obit.ru [79.142.92.100]
 5    51 ms    51 ms    51 ms  gw-cust-webplus.obit.ru [217.79.3.74]
 6    52 ms    51 ms    51 ms  195.131.253.3
 7    53 ms    53 ms    52 ms  gw.intellij.net [195.5.138.42]
 8    55 ms    55 ms    53 ms  mail2.intellij.net [89.163.94.178]

Trace complete.

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

DorsetBoy


Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

DorsetBoy

Quote from: Rik on May 23, 2010, 13:19:01
Weirder and weirder.

Especially as the analysis shows zero errors.  I can access the site from either IP (Russia or USA). The ping/tracert timing out is no issue as they have probably disallowed them to prevent DDOS issues. The Amazon AWS server is used for dns and is working correctly.

Why some people cannot access it is very odd.

Bill

Quote from: DorsetBoy on May 23, 2010, 13:26:29
Why some people cannot access it is very odd.

Still a few replies coming in on tbb; seems to be the same for various ISPs, not just IDNet.
Bill
BQMs-  IPv4  IPv6

dlorde

Have there been any developments with this strange problem?

I've tried numerous DNS servers and can't access the site from here through IDNet, although I've had no problem from work (different ISP).

If it helps, the main site, www.jetbrains.net is accessible, but www.jetbrains.net/confluence redirects to http://confluence.jetbrains.net, and it seems to be this that is inaccessible.

Should I raise it as a support issue?

Rik

Well, all three work for me, so I'd wonder about local issues, eg firewall.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

DorsetBoy

Which browser are you using?

www.jetbrains.net/confluence redirects to http://confluence.jetbrains.net

1) They are using an http address, not a www. and 2) the redirect is to a sub domain ,so they have probably moved the pages to a new folder.

Your browser settings or firewall may be preventing access to http addresses.


Glenn

Works ok here too

[attachment deleted by admin]
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

pctech

Could be that IPs have been spoofed and added to a block list on the server.


dlorde

Well, I've tried with Chrome, Internet Explorer, and Firefox, and I've tried turning off security and disabling the firewall and changing the DNS, but no joy yet.

Thanks for the responses though.

Rik

Try going through:

http://www.hidemyass.com/

If it works, your IP address would seem to be blocked.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.