Hi,
I have a little problem with the SD homepage.
If I try to visit the page directly I get a timeout.
When I use a proxy server all works fine.
(My IP: 93.216.225.xxx – T-Online germany , Proxy is running on 213.239.206.82)
Dear admin, could you take a look on the httpds logfile to give me a hint how I can access SD forum without using a proxy. Thanks in advance
Kind regards
Schnoog
I’ve heard more people about that, 1 from germany, other one from France. They couldn’t visit the forum as well.
No, DNS request is handled correctly.
When I use SD IP (95.154.239.99) instead of the URI the same issue occours (can connect via proxy, not directly).
Hi Schnoog,
can you send us some pingplotter (or equivalent) output so I can track down the issue? (95.154.239.99) We’ll do the same in the reverse !
Same here, I can’t visit the forum on my pc for like 1 month. It does work on my mobile( different internet provider). A friend has exactly the same problem( we both have the same provider, www.alice.nl).
I can’t visit the homepage/forum (the whole site times out).
It works with a proxy though.
This is the error: http://imageshack.us/photo/my-images/641/wadi.png/
Pingplotter image: http://imageshack.us/photo/my-images/205/awdai.png/
My ip: 93.125.224.26
Here`s a traceroute… but even on my proxy the route breaks at 87.117.211.50 , so this is not a real hint 
ICMP ping echo seems disabled at your side
traceroute 95.154.239.99
traceroute to 95.154.239.99 (95.154.239.99), 30 hops max, 40 byte packets using UDP
1 static.88-198-32-65.clients.your-server.de (88.198.32.65) 0.703 ms 0.638 ms 0.670 ms
2 hos-tr1.juniper1.rz6.hetzner.de (213.239.229.1) 0.210 ms hos-tr4.juniper2.rz6.hetzner.de (213.239.252.129) 0.256 ms hos-tr1.juniper1.rz6.hetzner.de (213.239.229.1) 0.222 ms
3 hos-bb1.juniper4.ffm.hetzner.de (213.239.240.230) 3.426 ms 3.437 ms 3.439 ms
4 r1fra1.core.init7.net (82.197.166.85) 10.790 ms 7.833 ms 7.737 ms
5 r1ams1.core.init7.net (77.109.128.154) 10.169 ms r1lon1.core.init7.net (77.109.128.37) 17.488 ms r1ams1.core.init7.net (77.109.128.154) 10.129 ms
6 r1lon1.core.init7.net (77.109.128.150) 16.216 ms te8-4.core1.thn.as20860.net (195.66.224.207) 15.307 ms r1lon1.core.init7.net (77.109.128.150) 16.101 ms
7 te8-4.core1.thn.as20860.net (195.66.224.207) 16.382 ms 16.399 ms 593.net1.north.dc5.as20860.net (62.233.127.174) 16.122 ms
8 593.net1.north.dc5.as20860.net (62.233.127.174) 17.202 ms 17.196 ms 87.117.211.50 (87.117.211.50) 16.593 ms
9 87.117.211.50 (87.117.211.50) 17.582 ms * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Seems like your fw keeps dropping my traffic ;(
For me, I’ve no problems with the site, it’s just working. But it doesn’t seem to be very stable.
The ping request gave me the following
C:\Users\Paul>ping 95.154.239.99
Pingen naar 95.154.239.99 met 32 bytes aan gegevens:
Time-out bij opdracht.
Time-out bij opdracht.
Time-out bij opdracht.
Antwoord van 95.154.239.99: bytes=32 tijd=60 ms TTL=51
Ping-statistieken voor 95.154.239.99:
Pakketten: verzonden = 4, ontvangen = 1, verloren = 3
(75% verlies).
De gemiddelde tijd voor het uitvoeren van één bewerking in milliseconden:
Minimum = 60ms, Maximum = 60ms, Gemiddelde = 60ms
C:\Users\Paul>ping 95.154.239.99
Pingen naar 95.154.239.99 met 32 bytes aan gegevens:
Antwoord van 95.154.239.99: bytes=32 tijd=50 ms TTL=51
Antwoord van 95.154.239.99: bytes=32 tijd=48 ms TTL=51
Antwoord van 95.154.239.99: bytes=32 tijd=78 ms TTL=51
Antwoord van 95.154.239.99: bytes=32 tijd=64 ms TTL=51
Ping-statistieken voor 95.154.239.99:
Pakketten: verzonden = 4, ontvangen = 4, verloren = 0
(0% verlies).
De gemiddelde tijd voor het uitvoeren van één bewerking in milliseconden:
Minimum = 48ms, Maximum = 78ms, Gemiddelde = 60ms
Traceroute did this:
C:\Users\Paul>tracert 95.154.239.99
Traceren van de route naar 95.154.239.99 via maximaal 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 35 ms 34 ms 34 ms s529c1c01.adsl.wanadoo.nl [82.156.28.1]
3 39 ms 39 ms 38 ms V1014.dr4-asd6.nl.euro.net [194.134.158.144]
4 39 ms 40 ms 39 ms PC27.cr1-asd6.nl.euro.net [194.134.161.61]
5 38 ms 40 ms 39 ms PC18.er1-asd6.nl.euro.net [194.134.161.102]
6 40 ms 47 ms 48 ms online-telecity1.telecity3f.jointtransit.nl [217
.170.18.130]
7 39 ms 40 ms 39 ms Te3-3.ar7.AMS2.gblx.net [208.50.237.193]
8 48 ms 48 ms 47 ms IOMART.TenGigabitEthernet7-1.ar4.LON3.gblx.net [
64.211.1.190]
9 79 ms 76 ms 76 ms 202.core1.thn.as20860.net [62.233.127.11]
10 82 ms 97 ms 82 ms 593.net1.north.dc5.as20860.net [62.233.127.174]
11 70 ms 69 ms 70 ms 87.117.211.50
12 * * * Time-out bij opdracht.
13 * * * Time-out bij opdracht.
14 * * * Time-out bij opdracht.
15 * * * Time-out bij opdracht.
16 * * * Time-out bij opdracht.
17 * 48 ms 49 ms 95.154.239.99
De trace is voltooid.
I’ve enabled ICMP so we can diagnose the problem better.
Does the website work for you now?
I made a change in the week before Christmas that might have been the cause, but I revoked this change a few days ago. So it didn’t seem to fit as the cause of your problem.
I’m hoping that you guys are reporting a problem that unbeknownst to you (because of Proxy) was fixed a few days ago.
The website does work now, but 40 minuts ago it didn’t (I tried it without a proxy). Today was the first time that I used a proxy to connect to this website, so I could post an image.
Works again without proxy, thank you very much 
(3 hours ago no chance w/o proxy)
Kind regards
Schnoog
