[X] My Assistant

[ugordan]

BTW this problem has persisted for over a month now. For the first 10 days or so there were intermittent brief periods when I was able to access UMSF from home but this problem has been continuous from roughly February 10.

Have you tried using a proxy server to work around the problem?

[Bjorn Jonsson]

Have you tried using a proxy server to work around the problem?

Yes - it works but it's much slower than accessing UMSF 'directly'.

[ugordan]

Yes - it works but it's much slower than accessing UMSF 'directly'.

I'm told there's a huge number of public proxies out there and that they can even be searched for. Maybe you just stumbled across a bad one?

[Bob Shaw]

I'm told there's a huge number of public proxies out there and that they can even be searched for. Maybe you just stumbled across a bad one?

I don't think a proxy server is the way to go with a website which is really the front end of a database - it just adds time to the whole exercise. What *might* help more is another DNS address, in case the IP isn't being properly resolved (and if that's happening across multiple - different - DNS addresses then it surely must be Doug's hosting company which is at the root of the problem). Alternatively, you might try playing with your Hosts settings...

Here are a bunch of proxies anyway:

62.254.32.6
62.254.32.7
62.255.32.6
62.255.32.7
62.255.32.8
62.253.64.6
62.253.64.7
62.253.64.8
62.253.64.9
62.255.0.6
62.255.0.7
62.255.0.8
62.253.128.6
62.253.128.7
62.252.32.6
62.252.32.7
213.107.224.6
80.3.160.5
62.253.0.6
62.252.0.6
62.252.96.6
62.252.224.6
62.252.224.7
62.252.224.8
62.252.64.6
62.252.64.7
62.252.64.8
62.252.192.6
62.252.192.7
62.252.192.8
62.252.192.9
62.252.192.10
62.254.64.6
62.254.64.7
62.254.0.6
62.254.0.7
62.254.0.8
62.254.0.9
62.254.0.34
62.254.0.36
62.253.32.6
62.253.32.7
62.254.128.6
62.254.128.7
62.255.64.6
62.255.64.7
62.252.128.6
62.252.128.7
62.252.128.10

Bob Shaw

[paxdan]

i'm gonna add this to the this thread as it is an access problem:

since the most recent invision update UMSF crashes safari on my mac, and i mean all the time. nothing else (and i get throught a lot of other stuff) crashes safari but UMSF.

i'm currently running osx 10.3.9 (yes yes i know i need to get 10.4) and safari version: 1.3.2 (312.5).

anyone else having this problem?

[jamescanvin]

i'm gonna add this to the this thread as it is an access problem:

since the most recent invision update UMSF crashes safari on my mac, and i mean all the time. nothing else (and i get throught a lot of other stuff) crashes safari but UMSF.

i'm currently running osx 10.3.9 (yes yes i know i need to get 10.4) and safari version: 1.3.2 (312.5).

anyone else having this problem?

I've had no problems using 10.4.5, Safari Version 2.0.3 (417.8), but that doesn't really help you does it.

It has crashed Firefox (1.5) on my Linux box, but only once.

James

[Bjorn Jonsson]

I've submitted 3 more tracert's to the host. Flicking between my internet connection and a neigbours internet connection ( Plunet ADSL and NTL Cable ) - mine works, the neigbours doesnt. Who know how many people have just given up on the place - and the coincidence of this problem first appearing with a drop in total visit numbers for Feb is too much to leave un-attended - so I'm going to keep hacking at the hosting firm till they correct it.

Doug

Any news of this ? This has been a problem for over 6 weeks now and continuously for roughly a month.

[djellison]

And I'm getting nothing back from the host either. It's annoying me more than it's annoying any of you, believe me.

Doug

[Bill Harris]

And the past week or so I've been getting "The page cannot be displayed" warning:

"The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings."

It seems like the Browser times out.

--Bill


EDIT: server IP address: 209.215.191.34
client IP address: 209.214.109.58

[djellison]

I need the IP of any connection from which people can not get to the site from. As many as possible would be good. It is clearly a problem at the hosts end of the pipe, but they're attempting to deny it.

Doug

[djellison]

From the host

"Please note that the ip 10.89.23.254 is blocked in our datacentre. We have contacted them and they will unblock it as soon as possible.
And regarding the other two ips 152.163.164.30 and 62.104.210.47. Please note that these are not blocked in our servers."

If the second and third IP's are yours - try contacting your ISP.

Doug

[Bjorn Jonsson]

Everything works now and I can access UMSF from home !!?

For the first time since mid/early February. It didn't work yesterday.

For the record, tracert now returns this :

C:\>tracert www.unmannedspaceflight.com

Tracing route to unmannedspaceflight.com [72.9.234.170]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms my.router [192.168.1.1]
2 14 ms 15 ms 14 ms 217.151.181.57
3 15 ms 14 ms 14 ms 217.151.181.58
4 16 ms 16 ms 15 ms 217.151.181.62
5 17 ms 17 ms 18 ms fe2-0.core01.islandssimi.is [213.176.138.66]
6 19 ms 18 ms 19 ms fe0-0.uk-gw.islandssimi.is [213.176.138.5]
7 541 ms 500 ms 487 ms 213.176.138.254.in.is [213.176.138.254]
8 234 ms 229 ms 220 ms ae0-6.lon11.ip.tiscali.net [213.200.77.125]
9 445 ms 450 ms * so-3-1-0.lon22.ip.tiscali.net [213.200.80.30]
10 462 ms 269 ms 283 ms ldn-b2-link.telia.net [213.248.100.193]
11 546 ms 535 ms 455 ms ldn-bb1-pos0-1-0.telia.net [213.248.74.1]
12 355 ms * 519 ms nyk-bb1-pos0-2-0.telia.net [213.248.65.90]
13 576 ms 580 ms 563 ms ash-bb1-pos6-0-0-0.telia.net [213.248.80.69]
14 251 ms 270 ms 265 ms atl-bb1-pos5-0-0.telia.net [213.248.80.142]
15 311 ms 310 ms 321 ms globalnet-103907-atl-bb1.c.telia.net [213.248.90.54]
16 355 ms 368 ms 373 ms atl-core-a-tgi2-1.gnax.net [209.51.149.105]
17 668 ms 664 ms 777 ms L3-ATL-5.gnax.net [209.51.131.94]
18 184 ms 185 ms 185 ms star.dnsprotect.com [72.9.234.170]

Trace complete.

[Guest_Analyst_*]

Whatever has been done: It works from home for the first time for weeks. THX!

Analyst

[DFinfrock]

Yes!!!!! It is working for me, too.

David

[Bjorn Jonsson]

Well, this only worked for a few hours . Now I can no longer access UMSF from home .

C:\>tracert www.unmannedspaceflight.com

Tracing route to unmannedspaceflight.com [72.9.234.170]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms my.router [192.168.1.1]
2 15 ms 15 ms 14 ms 217.151.181.57
3 14 ms 15 ms 15 ms 217.151.181.58
4 16 ms 16 ms 17 ms 217.151.181.62
5 18 ms 17 ms 18 ms fe2-0.core01.islandssimi.is [213.176.138.66]
6 19 ms 19 ms 19 ms fe0-0.uk-gw.islandssimi.is [213.176.138.5]
7 505 ms 500 ms 544 ms 213.176.138.254.in.is [213.176.138.254]
8 257 ms 233 ms 230 ms ae0-6.lon11.ip.tiscali.net [213.200.77.125]
9 558 ms 543 ms 554 ms so-3-1-0.lon22.ip.tiscali.net [213.200.80.30]
10 574 ms * 225 ms ldn-b2-link.telia.net [213.248.100.193]
11 598 ms 591 ms 600 ms ldn-bb1-pos0-1-0.telia.net [213.248.74.1]
12 798 ms 729 ms 739 ms nyk-bb1-pos0-2-0.telia.net [213.248.65.90]
13 689 ms 662 ms 632 ms ash-bb1-pos6-0-0-0.telia.net [213.248.80.69]
14 186 ms 188 ms 190 ms atl-bb1-pos5-0-0.telia.net [213.248.80.142]
15 676 ms 622 ms 624 ms globalnet-103907-atl-bb1.c.telia.net [213.248.90.54]
16 622 ms 595 ms 626 ms atl-core-a-tgi2-1.gnax.net [209.51.149.105]
17 327 ms 320 ms 325 ms L3-ATL-5.gnax.net [209.51.131.94]
18 * * * Request timed out.
19 * * * Request timed out.
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 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.