Yola Gateway errors with Telkom ISP

[Dev()n]

Does anyone know why Yola published sites are not working on Telkom???
They work on all other ISP's. I have no idea why Telkom would block it...

 

[Joker]

Traceroute?

 

[Vhata]

Hi,

I run Operations at yola.com, and we've been struggling with this issue since the weekend. It's not our servers, since everybody else can see the sites fine, but every hosting provider between our affected users and our sites claim that they are not blocking anybody and that it must be somebody else.

If anybody here is getting errors trying to load Yola sites (try http://www.natashamfreeman.com/ as an example), we would really appreciate a traceroute (or, ideally, a tcptraceroute on port 80) from your machine to our sites, so we can find out who is blocking you.

Sorry about this - we're working on it as hard as we can. You can mail me at [email protected] if you're having the issue and want to help debug it.

Cheers,
-Jonathan Hitchcock
Yola Operations

 

[Srack0verflow]

Tracing route to www.natashamfreeman.com [72.52.4.95]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  login.router [10.0.0.2]
  2    25 ms    25 ms    23 ms  dsl-240-**-**.telkomadsl.co.za [41.240.**.**]
  3    26 ms    25 ms    26 ms  196.43.33.86
  4    26 ms    24 ms    22 ms  196.43.33.81
  5    37 ms    34 ms    37 ms  196.43.10.130
  6    34 ms    36 ms    35 ms  196.43.33.5
  7   219 ms   217 ms   217 ms  ams-ip-dir-globalc-pos-4-0-1.telkom-ipnet.co.za
[196.43.18.38]
  8   215 ms   216 ms   213 ms  so-0-2-0.ar2.AMS2.gblx.net [64.210.21.45]
  9   225 ms   225 ms   224 ms  PROLEXIC.GigabitEthernet9-7.ar7.LON3.gblx.net [2
07.138.94.98]
 10   223 ms   222 ms   220 ms  unknown.prolexic.com [209.200.156.50]
 11   226 ms   225 ms   223 ms  www.natashamfreeman.com [72.52.4.95]

Trace complete.

doesn't show me much, the browser still gives a 'gateway timeout' though

 

[Vhata]

doesn't show me much, the browser still gives a 'gateway timeout' though

Thanks very much for that, at least we can see what's between you and our servers.

If you have tcptraceroute (which is the same as traceroute, but uses actual TCP/IP on port 80, which is what the browser uses, as opposed to UDP or ICMP, which is more just network discovery), that might shed some light too.

Another helpful thing you could do would be to telnet to 72.52.4.95 on port 80, and type/paste the following:

GET / HTTP/1.1
Host: natashamfreeman.com

Make sure you've got the blank line at the end - press enter twice for luck. This should simulate a browser request for the site, so we can see what error actually gets issued, and by what server.

Our current hunch is that one of Telkom's transparent proxies is either blocking the route to our servers, or being blocked upstream - we've opened a ticket with them, and we'll see how successful we are at clearing this up.

Thanks again for your help!

Cheers,
-Jonathan

 

[Srack0verflow]

uhm, i'm kinda shy to admit it
i don't know how to do that in win7 :blush:

 

[Vhata]

uhm, i'm kinda shy to admit it
i don't know how to do that in win7 :blush:

Don't be shy - neither do I (we use Macbooks on our desks, and Linux on our servers). There *should* be a telnet command in Windows 7's command-prompt: just type "telnet 72.52.4.95 80" and it should work. If it doesn't, my Windows knowledge is about a decade out of date, and you might have to use Putty: http://www.chiark.greenend.org.uk/~sgtatham/putty/

 

[Srack0verflow]

Don't be shy - neither do I (we use Macbooks on our desks, and Linux on our servers). There *should* be a telnet command in Windows 7's command-prompt: just type "telnet 72.52.4.95 80" and it should work. If it doesn't, my Windows knowledge is about a decade out of date, and you might have to use Putty: http://www.chiark.greenend.org.uk/~sgtatham/putty/

so goggle does teach old dogs new tricks. you have to enable the telnet client in control panel>>programs and features before you can use it

anyway, i tried pUTTY too and before i get a chance to type in the commands it gives an error that the server unexpectedly closed the connection

 

[Vhata]

I thought I should mention - we managed to resolve this in the end, a while back, after much wrangling between various upstream network providers. Thanks for your help!