I cant access priuschat. need help.

[TheForce]

For the past few days I have been unable to access priuschat.com from my home network. I know priuschat has has some issues the past few days but and this is a big BUT, I can access the website fine from work or if I use a proxy from my home PC. When I try a trace route on the domain it looks like I get all the way to the host then it drops out. I will post the trace route results below. I can even login to my web hosts shell access and use lynx to get on priuschat. Using my web hosts shell access I can do a trace route from there and the server responds fine. Its almost like my IP or something has been banned from the server level and when I try to connect I just get rejected. Does anyone have any idea on whats going on? Is this some kind of DNS routing issue that I have to wait for it to fix its self?


My trace route from my home computer.

C:\>tracert priuschat.com

Tracing route to priuschat.com [72.52.166.5]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms theforce.mshome.net [192.168.0.1]
2 12 ms 12 ms 13 ms cpe-76-181-160-1.columbus.res.rr.com [76.181.160.1]
3 8 ms 12 ms 20 ms gig2-4-562.crvloh1-ybr1.columbus.rr.com [24.95.86.89]
4 8 ms 7 ms 15 ms srp9-1.clmboh1-rtr1.columbus.rr.com [65.25.129.189]
5 23 ms 20 ms 17 ms network-065-025-137-253.columbus.rr.com [65.25.137.253]
6 23 ms * * gig0-3-0.mtgmoh1-rtr0.columbus.rr.com [24.95.81.213]
7 27 ms 30 ms 26 ms te-3-2.car1.Cincinnati1.Level3.net [4.78.216.13]
8 38 ms 35 ms 36 ms ae-5-5.ebr2.Chicago1.Level3.net [4.69.132.206]
9 39 ms 41 ms 41 ms ae-21-54.car1.Chicago1.Level3.net [4.68.101.98]
10 45 ms 41 ms 42 ms WBS-CONNECT.edge5.Chicago1.Level3.net [4.71.182.14]
11 48 ms 39 ms 41 ms lw-core1-ge3.rtr.liquidweb.com [209.59.157.10]
12 41 ms 45 ms 40 ms lw-core3-ge1.rtr.liquidweb.com [209.59.157.86]
13 42 ms 39 ms 41 ms lw-dc2-dist1-ge1.rtr.liquidweb.com [209.59.157.98]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
I cut it short of the 30 hops

Here is the trace route from my web host.

[dawber]$ traceroute priuschat.com
traceroute to priuschat.com (72.52.166.5), 30 hops max, 38 byte packets
1 ip-67-205-4-1 (67.205.4.1) 209.881 ms 3.425 ms 20.160 ms
2 border20.ge4-4.newdream-8.lax.pnap.net (216.52.220.145) 0.439 ms 0.361 ms 0.362 ms
3 core2.t2-1-bbnet1.lax.pnap.net (216.52.255.2) 118.238 ms 1.104 ms 198.152 ms
4 GigabitEthernet3-0.GW2.LAX15.ALTER.NET (157.130.236.109) 0.716 ms 0.712 ms 0.566 ms
5 0.so-1-0-0.XL1.LAX15.ALTER.NET (152.63.117.90) 0.780 ms 0.785 ms 0.805 ms
6 0.so-6-1-2.XT1.CHI2.ALTER.NET (152.63.66.9) 54.237 ms 54.174 ms 55.783 ms
7 POS6-0.GW9.CHI2.ALTER.NET (152.63.69.161) 53.426 ms 53.374 ms 53.217 ms
8 liquidwebOC12-gw.customer.alter.net (65.207.234.198) 64.468 ms 64.297 ms 64.058 ms
9 lw-core2-ge4.rtr.liquidweb.com (209.59.157.26) 64.529 ms 64.671 ms 64.990 ms
10 lw-core4-ge2.rtr.liquidweb.com (209.59.157.114) 64.124 ms 64.592 ms 64.532 ms
11 lw-dc2-dist2-ge2.rtr.liquidweb.com (209.59.157.110) 64.147 ms 64.192 ms 64.377 ms
12 72.52.166.5 (72.52.166.5) 63.971 ms 64.405 ms 64.167 ms

[efusco]

Same issues for me from all browsers, IPs and PCs I've tried. From work, during the day it seems better, then it all goes to hell at some point.

Danny's out of town and is going to be migrating to a brand new souped up server probably this week.

[apriusfan]

Interesting traceroute data. Based on TheForce's dataset, it would appear that there are some problems with liquidweb. There could be problems with the server that is hosting PC, which in turn is causing a delay at liquidweb. Presumably, diagnostics were run that confirmed the bottleneck is the server that is hosting PC. I would hate for Danny to plunk down $ for a new server and the problems continue because of a bottleneck in liquidweb.

[efusco]

I send Danny an e-mail linking to this thread.

[TheForce]

Well at least I'm not the only one having issues. I guess I will just have to surf PC with a proxy at home for now.

[ZC1]

Liquidweb is having issues, not to mention the server which is hosting this site. I checked it myself. (I'm a networking Pro).

Spotty accessibility, double posts, lack of refreshes, ping or traceroute times high or not responding, .etc...

Danny will be happy, I'm sure, when PriusChat.com moves!
Me too!

ZC1

[apriusfan]

Originally Posted by ZC1

Liquidweb is having issues, not to mention the server which is hosting this site. I checked it myself. (I'm a networking Pro).

Spotty accessibility, double posts, lack of refreshes, ping or traceroute times high or not responding, .etc...

The question is whether the liquidweb issues are independent of the server hosting priuschat.com. If they are (independent), then a faster server may or may not help (most likely won't help). I don't have separate (from priuschat.com) experience with liquidweb, so can't comment.

Originally Posted by ZC1

Danny will be happy, I'm sure, when PriusChat.com moves!
Me too!

I imagine that quite a few people will be happy.... Me among them.

[TheForce]

I'm thinking it is liquidweb's problem because I'm at work right now and PC is loading perfectly fine. I'm connected to my home PC from work and priuschat still will not load unless i go through a proxy. I think it has something to do with the traffic routing.

[Danny]

I think the problems might have something to do with the fact that the group who manages our server through LiquidWeb went ahead and started some DNS changes so that when the server move is accomplished, there will be less downtime. You can try accessing the site directly via the IP address to be sure:

http://72.52.166.5/forums/

If it still won't come up using the IP address, then it must be another issue. I'm not sure what can be done to fix the issue in the short-run, but hopefully the server move will happen very soon.

[efusco]

Originally Posted by Danny

I think the problems might have something to do with the fact that the group who manages our server through LiquidWeb went ahead and started some DNS changes so that when the server move is accomplished, there will be less downtime. You can try accessing the site directly via the IP address to be sure:

http://72.52.166.5/forums/

If it still won't come up using the IP address, then it must be another issue. I'm not sure what can be done to fix the issue in the short-run, but hopefully the server move will happen very soon.

Danny, I'm having no problem with the site today at all...very fast and smooth.
But when I tried that direct IP the site came up fine, but trying to login gave me the following message:
In order to accept POST request originating from this domain, the admin must add this domain to the whitelist.