Unable to access texturadesign.lighthouseapp.com from Greek ISP
I'm in Greece, connecting from a network on the main Greek telecom provider ISP (87.203.67.47, a.k.a. athedsl-4369044.home.otenet.gr) and am unable to access our lighthouse site: https://texturadesign.lighthouseapp.com/.
In chrome I get this error: "Google Chrome could not load the webpage because texturadesign.lighthouseapp.com took too long to respond. The website may be down, or you may be experiencing issues with your Internet connection."
In curl I get this:
[q@haywire/0 live]$curl -I https://texturadesign.lighthouseapp.com/
curl: (35) Unknown SSL protocol error in connection to texturadesign.lighthouseapp.com:443
Raw connection with openssl fails too:
[q@haywire/0 live]$openssl s_client -connect texturadesign.lighthouseapp.com:443
CONNECTED(00000003)
GET / HTTP/1.1
host: texturadesign.lighthouseapp.com
depth=4 /C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust External CA Root
verify error:num=19:self signed certificate in certificate chain
verify return:0
17914:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:/SourceCache/OpenSSL098/OpenSSL098-44/src/ssl/s23_lib.c:182:
Ping fails:
[q@haywire/0 ~]$ping texturadesign.lighthouseapp.com
PING texturadesign.lighthouseapp.com (184.73.201.0): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
^C
But so does help.lighthouseapp.com:
[q@haywire/0 ~]$ping help.lighthouseapp.com
PING tenderapp.com (184.73.201.197): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
^C
Traceroute looks like this:
[q@haywire/0 ~]$traceroute texturadesign.lighthouseapp.com
traceroute to texturadesign.lighthouseapp.com (184.73.201.0), 64 hops max, 52 byte packets
1 (192.168.2.1) 965.140 ms 1.603 ms 1.396 ms
2 80.106.108.44 (80.106.108.44) 15.808 ms 17.263 ms 15.578 ms
3 79.128.245.45 (79.128.245.45) 19.065 ms 15.300 ms 16.328 ms
4 nyma-crsa-nyma7609b-1.backbone.otenet.net (79.128.226.97) 17.622 ms 19.130 ms 19.676 ms
5 62.75.3.69 (62.75.3.69) 31.866 ms 15.201 ms 16.099 ms
6 62.75.4.106 (62.75.4.106) 66.892 ms
62.75.4.2 (62.75.4.2) 107.544 ms
62.75.4.106 (62.75.4.106) 66.956 ms
7 xe-10-0-3.edge5.amsterdam1.level3.net (212.72.45.241) 74.685 ms 98.237 ms 72.266 ms
8 4.69.162.149 (4.69.162.149) 154.027 ms
4.69.162.153 (4.69.162.153) 158.301 ms
4.69.162.149 (4.69.162.149) 161.167 ms
9 ae-57-222.ebr2.amsterdam1.level3.net (4.69.153.205) 156.179 ms
ae-58-223.ebr2.amsterdam1.level3.net (4.69.153.209) 154.127 ms
ae-59-224.ebr2.amsterdam1.level3.net (4.69.153.213) 174.044 ms
10 ae-47-47.ebr2.london1.level3.net (4.69.143.78) 154.201 ms
ae-48-48.ebr2.london1.level3.net (4.69.143.82) 150.191 ms
ae-47-47.ebr2.london1.level3.net (4.69.143.78) 169.548 ms
11 ae-41-41.ebr1.newyork1.level3.net (4.69.137.66) 153.636 ms
ae-42-42.ebr1.newyork1.level3.net (4.69.137.70) 149.963 ms
ae-41-41.ebr1.newyork1.level3.net (4.69.137.66) 160.248 ms
12 ae-4-4.ebr1.newyork2.level3.net (4.69.141.18) 153.589 ms 177.965 ms
ae-10-10.ebr2.washington12.level3.net (4.69.148.50) 170.836 ms
13 ae-3-3.ebr2.washington1.level3.net (4.69.132.89) 234.692 ms 150.120 ms 153.252 ms
14 ae-82-82.csw3.washington1.level3.net (4.69.134.154) 156.336 ms
ae-62-62.csw1.washington1.level3.net (4.69.134.146) 186.526 ms 161.057 ms
15 ae-1-60.edge3.washington1.level3.net (4.69.149.17) 167.737 ms
ae-2-70.edge3.washington1.level3.net (4.69.149.81) 153.331 ms
ae-3-80.edge3.washington1.level3.net (4.69.149.145) 148.876 ms
16 amazon.com.edge3.washington1.level3.net (4.59.144.178) 197.940 ms 157.981 ms
amazon.com.edge3.washington1.level3.net (4.59.144.174) 153.497 ms
17 205.251.245.21 (205.251.245.21) 237.752 ms 159.034 ms
205.251.245.23 (205.251.245.23) 160.576 ms
18 205.251.245.41 (205.251.245.41) 151.570 ms 152.549 ms 164.890 ms
19 * * *
20 * * *
21 * * *
22 216.182.224.195 (216.182.224.195) 221.203 ms
216.182.224.203 (216.182.224.203) 151.700 ms
216.182.224.193 (216.182.224.193) 163.122 ms
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
[etc...]
If I connect via a web proxy, it works of course, but I'd rather not.
Any suggestions?
Quinn
Discussions are closed to public comments.
If you need help with Lighthouse please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Quinn Comendant on 23 Jan, 2013 06:24 PM
Also, I'd like to note that I have no problem accessing http://help.lighthouseapp.com/, while https://help.lighthouseapp.com/ has the same problem as https://texturadesign.lighthouseapp.com/. So it's an SSL issues, but why being in Greece causes a problem?
2 Posted by Quinn Comendant on 23 Jan, 2013 06:36 PM
No, I take that back: I can access https://help.lighthouseapp.com/ (albeit with a certificate warning ("Server's certificate does not match the URL"). I still can't get https://texturadesign.lighthouseapp.com/.
Support Staff 3 Posted by Tiger Team on 23 Jan, 2013 06:51 PM
Hi Quinn,
a few notes
good debugging, though!
Basically the problem is your ISP's routing setup is outdated and it looks like it can't handle IP addresses ending in zero. In the past we've solved this by having customers just contact their isp or whoever's running their network.
4 Posted by Quinn Comendant on 23 Jan, 2013 07:41 PM
Thanks Courtenay
I've emailed our ISP and look forward to their reply:
----- Forwarded message from Quinn Comendant, 23 Jan 2013 21:39:54 ----- Subject: ADSL network routing
Date: Wed, 23 Jan 2013 21:39:54 +0200
From: Quinn Comendant
To: [email blocked]
Hello
We are an OTE ADSL customer in Oia, Thira. Our IP address is 85.73.199.255. We are having a problem which seems to be related to network issues regarding IP addresses ending in "zero", such as 184.73.201.0. We are unable to access https://texturadesign.lighthouseapp.com/, and the NOC at lighthouseapp.com claims this is a common problem with some ISPs who have outdated routing setup. They suggest you will be able to correct something so this will work for us? Please let me know if this is possible. You may view the full support transcript for this issue at http://help.lighthouseapp.com/discussions/problems/11684-unable-to-access-texturadesignlighthouseappcom-from-greek-isp.
Thanks for your kind consideration,
Quinn Comendant
5 Posted by Quinn Comendant on 25 Jan, 2013 12:36 PM
Looks like this ticket is collecting comment spam.
Q
Support Staff 6 Posted by brandi on 25 Jan, 2013 06:00 PM
Quinn,
I made this discussion private after the first spam comment.
Brandi
7 Posted by Quinn Comendant on 25 Jan, 2013 07:25 PM
Can we keep it public please? I've sent links to our ISP - they may be viewing it.
Q
Support Staff 8 Posted by brandi on 25 Jan, 2013 07:32 PM
If you can provide me with the emails addresses of anyone you'd like to have privileges, I can add them to the private discussion. If you don't mind the (potential) spam, I can make it public once more. Let me know.
9 Posted by Quinn Comendant on 25 Jan, 2013 07:36 PM
Yes, just make it public. You guys need a captcha.
Q
Support Staff 10 Posted by brandi on 25 Jan, 2013 07:39 PM
We use captcha ;) It's public again.
Support Staff 11 Posted by brandi on 30 Jan, 2013 07:46 PM
Hi Quinn,
Just following up to see if you were able to learn anything from your ISP?
Best,
Brandi
12 Posted by Quinn Comendant on 03 Feb, 2013 03:50 PM
I didn't receive a reply; didn't expect one from OTE. It's Greece, after all. =\
Q
Julien closed this discussion on 19 Feb, 2013 06:33 PM.