Can someone help. Seems this forum is unreachable in my region. Impossible to connect without using a vpn.
I am currently using vpn to post this.
Trace route command shows normal as shown below. Ping directly (without vpn) to talkchess.com also shows it is reachable.
-
-
-
6 196 ms 195 ms 202 ms sl-mst50-pa-.sprintlink.net [160.81.100.13]
7 193 ms 191 ms 191 ms sl-crs1-sj-be14.sprintlink.net [144.232.15.56]
8 197 ms 196 ms 195 ms sl-mst31-sj-be13.sprintlink.net [144.232.15.245]
9 192 ms 200 ms 192 ms 99.82.178.80
10 196 ms 198 ms 196 ms 52.93.141.17
11 187 ms 188 ms 187 ms 54.240.242.21
12 * * * Request timed out.
13 257 ms 254 ms 253 ms 52.93.129.101
14 * * * Request timed out.
15 251 ms 251 ms 250 ms 52.93.239.15
16 248 ms 248 ms 248 ms 52.95.2.49
17 254 ms 297 ms 249 ms 52.95.1.136
18 245 ms 245 ms 245 ms 52.95.1.111
19 262 ms 249 ms 304 ms 52.95.3.126
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 269 ms 257 ms 257 ms aws-chess.wpcomp.com [3.13.56.189]
Trace complete.
ping talkchess.com
Reply from 3.13.56.189: bytes=32 time=256ms TTL=38
Reply from 3.13.56.189: bytes=32 time=256ms TTL=38
Reply from 3.13.56.189: bytes=32 time=256ms TTL=38
Reply from 3.13.56.189: bytes=32 time=287ms TTL=38
Ping statistics for 3.13.56.189:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 256ms, Maximum = 287ms, Average = 263ms
Any tips or directions so I can connect directly to this forum without going via vpn?
I told my wife that a husband is like a fine wine; he gets better with age. The next day, she locked me in the cellar.
MikeGL wrote: ↑Sun Apr 12, 2020 8:27 pm
Can someone help. Seems this forum is unreachable in my region. Impossible to connect without using a vpn.
I am currently using vpn to post this.
Trace route command shows normal as shown below. Ping directly (without vpn) to talkchess.com also shows it is reachable.
-
-
-
6 196 ms 195 ms 202 ms sl-mst50-pa-.sprintlink.net [160.81.100.13]
7 193 ms 191 ms 191 ms sl-crs1-sj-be14.sprintlink.net [144.232.15.56]
8 197 ms 196 ms 195 ms sl-mst31-sj-be13.sprintlink.net [144.232.15.245]
9 192 ms 200 ms 192 ms 99.82.178.80
10 196 ms 198 ms 196 ms 52.93.141.17
11 187 ms 188 ms 187 ms 54.240.242.21
12 * * * Request timed out.
13 257 ms 254 ms 253 ms 52.93.129.101
14 * * * Request timed out.
15 251 ms 251 ms 250 ms 52.93.239.15
16 248 ms 248 ms 248 ms 52.95.2.49
17 254 ms 297 ms 249 ms 52.95.1.136
18 245 ms 245 ms 245 ms 52.95.1.111
19 262 ms 249 ms 304 ms 52.95.3.126
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 269 ms 257 ms 257 ms aws-chess.wpcomp.com [3.13.56.189]
Trace complete.
ping talkchess.com
Reply from 3.13.56.189: bytes=32 time=256ms TTL=38
Reply from 3.13.56.189: bytes=32 time=256ms TTL=38
Reply from 3.13.56.189: bytes=32 time=256ms TTL=38
Reply from 3.13.56.189: bytes=32 time=287ms TTL=38
Ping statistics for 3.13.56.189:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 256ms, Maximum = 287ms, Average = 263ms
Any tips or directions so I can connect directly to this forum without going via vpn?
That is too bad, that you were blocked for so long. You will have to take it up with Sam, Mike. He is the only one who can clear your location from being blocked at least I think that is what is happening, see the thread about that. The site was also slow in responding to any new posts for me, or a post I wanted to make took so long it timed out but that was only yesterday.
Debugging is twice as hard as writing the code in the first
place. Therefore, if you write the code as cleverly as possible, you
are, by definition, not smart enough to debug it.
-- Brian W. Kernighan
