cant access two separate domains on web16.
cant access the cp for one of the accounts (does not finish loading) and the other account cp shows “unknown” quota data.
Can’t trace to or ping 173.0.129.96
web16 is up, but there looks to be an issue on the tmp partition, so if your app hits that it may be an issue, we are rebooting it in a moment now to resolve, but tried several options. Actually just saw this we checked a lot and did not see any down, so were working on trying to fix without reboot.
Can’t ping or trace may be more of a local issue for you? It is up/has been up here.
We’ve rebooted it now..
can’t access from two different ip’s on my end. Verizon wireless, and hotel wifi. Can access other jodo servers/sites, but not those.
it is up.
It was working just moments before, we rebooted it.
C:\Users\steph_000>ping web16.jodoshared.com -n 50
Pinging web16.jodoshared.com [173.0.129.96] with 32 bytes of data:
Reply from 173.0.129.96: bytes=32 time=10ms TTL=60
Reply from 173.0.129.96: bytes=32 time=18ms TTL=60
Reply from 173.0.129.96: bytes=32 time=30ms TTL=60
Reply from 173.0.129.96: bytes=32 time=12ms TTL=60
Reply from 173.0.129.96: bytes=32 time=11ms TTL=60
Reply from 173.0.129.96: bytes=32 time=13ms TTL=60
Reply from 173.0.129.96: bytes=32 time=9ms TTL=60
Reply from 173.0.129.96: bytes=32 time=9ms TTL=60
Reply from 173.0.129.96: bytes=32 time=9ms TTL=60
Reply from 173.0.129.96: bytes=32 time=9ms TTL=60
Reply from 173.0.129.96: bytes=32 time=18ms TTL=60
Reply from 173.0.129.96: bytes=32 time=11ms TTL=60
Reply from 173.0.129.96: bytes=32 time=13ms TTL=60
Reply from 173.0.129.96: bytes=32 time=11ms TTL=60
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 173.0.128.42: Destination host unreachable.
Request timed out.
Reply from 173.0.128.42: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Reply from 173.0.128.42: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Reply from 173.0.128.42: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 173.0.128.42: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 173.0.128.42: Destination host unreachable.
Request timed out.
Reply from 173.0.128.42: Destination host unreachable.
Ping statistics for 173.0.129.96:
Packets: Sent = 50, Received = 21, Lost = 29 (58% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 30ms, Average = 13ms
C:\Users\steph_000>ping web16.jodoshared.com -n 50
Pinging web16.jodoshared.com [173.0.129.96] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 173.0.128.42: Destination host unreachable.
Request timed out.
Reply from 173.0.128.42: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Reply from 173.0.129.96: bytes=32 time=10ms TTL=60
Reply from 173.0.129.96: bytes=32 time=11ms TTL=60
Reply from 173.0.129.96: bytes=32 time=11ms TTL=60
Reply from 173.0.129.96: bytes=32 time=9ms TTL=60
Reply from 173.0.129.96: bytes=32 time=11ms TTL=60
Reply from 173.0.129.96: bytes=32 time=11ms TTL=60
Reply from 173.0.129.96: bytes=32 time=10ms TTL=60
Reply from 173.0.129.96: bytes=32 time=13ms TTL=60
Reply from 173.0.129.96: bytes=32 time=12ms TTL=60
Reply from 173.0.129.96: bytes=32 time=11ms TTL=60
Reply from 173.0.129.96: bytes=32 time=20ms TTL=60
Reply from 173.0.129.96: bytes=32 time=13ms TTL=60
Reply from 173.0.129.96: bytes=32 time=10ms TTL=60
Reply from 173.0.129.96: bytes=32 time=11ms TTL=60
Reply from 173.0.129.96: bytes=32 time=9ms TTL=60
Reply from 173.0.129.96: bytes=32 time=15ms TTL=60
Reply from 173.0.129.96: bytes=32 time=9ms TTL=60
Reply from 173.0.129.96: bytes=32 time=12ms TTL=60
Reply from 173.0.129.96: bytes=32 time=11ms TTL=60
Reply from 173.0.129.96: bytes=32 time=19ms TTL=60
Reply from 173.0.129.96: bytes=32 time=13ms TTL=60
Reply from 173.0.129.96: bytes=32 time=15ms TTL=60
Reply from 173.0.129.96: bytes=32 time=11ms TTL=60
Reply from 173.0.129.96: bytes=32 time=22ms TTL=60
Reply from 173.0.129.96: bytes=32 time=44ms TTL=60
Reply from 173.0.129.96: bytes=32 time=11ms TTL=60
Reply from 173.0.129.96: bytes=32 time=16ms TTL=60
Reply from 173.0.129.96: bytes=32 time=12ms TTL=60
Reply from 173.0.129.96: bytes=32 time=9ms TTL=60
Reply from 173.0.129.96: bytes=32 time=9ms TTL=60
Reply from 173.0.129.96: bytes=32 time=11ms TTL=60
Reply from 173.0.129.96: bytes=32 time=11ms TTL=60
Reply from 173.0.129.96: bytes=32 time=10ms TTL=60
Reply from 173.0.129.96: bytes=32 time=10ms TTL=60
Reply from 173.0.129.96: bytes=32 time=15ms TTL=60
Ping statistics for 173.0.129.96:
Packets: Sent = 50, Received = 37, Lost = 13 (26% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 44ms, Average = 13ms
It did a little fsck on the reboot so took longer than just a reboot.
some things reported fixed from users.
I can now access the site pages by verizon connection, not by other connection.
cp of one of the accounts looks/behaves more normally now, the other still hangs after partial page load.
s
orry, the issue with the cp is on a completely separate account. the cps for the two accounts in question seem to be ok now.
So there does seem to be an unrelated connection issue there.
web16 is still down… no response on web or ftp.
Edit:
Well, no. Looks like the tracert times out very early on my ISPs network. Other servers go through okay. I’ll look at it for a while to see if that fixes it, then…
okay, I just spent over an hour chatting with AT&T. They say the server is blocked from AT&T servers, and insist it’s not them that’s doing it. I can’t access web14 or web16, either on AT&T or on my phone, which is on Sprint network. They said I need to get in touch with the host and ask them who can unblock it. So… wtf?
The only concrete suggestion they have is for you to call 1-877-722-3755 and ask for a Tier2 representative, though I personally wouldn’t hold out much hope for any joy there. Meanwhile, at least web14 and 16 are offline as far as a fair number of people in the US are concerned. Tracert works fine from lots of other networks, but not from here.
Tracert on AT&T doesn’t get too far.
1 <1ms 192.168.1.1
2 8ms adsl-108.204…sbcglobal.net [108.204…]
3 8ms dist2-vlan60.lgtpmi.ameritech.net [65.42.245.243]
4 * Request timed out.
That’s it.
I had a customer reporting this same issue, using ATT Business DSL connection last week.
I have not heard from them, so I’d assume it was resolved?
We talked to ATT on this, and got unblocked, but they are a pain.
2 domains on one account had malware on them, and they blocked the entire IP due to that. We cleared up the malware, but they have a pretty bad policy here.
They don’t even make a report to abuse dept, they just block it without any actions.
The malware was on unmaintained joomla accounts.
JUST FYI, sprint doesnt do this, are you sure you weren’t connected maybe to att wifi at that point?
However, through this we did get a direct line to their network operations network backplane team that is responsive.
I’m on an ATT DSL connection right now (residential), and I can’t get any Web16 sites to load.
-After going through a full reboot/modem reset/cache flush on this ATT DSL connection (and getting another email from a client!) I did send a trouble ticket via email to resllersupport@jh - couldn’t get the helpdesk page to load! (resellerdesk.jodohost.com) : BCK-77018-287
FWIW here’s a couple of Trace Routes:
Here’s web17
Tracing route to web17.vdghosting.net [173.0.129.102]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms home
2 31 ms 25 ms 25 ms x
3 27 ms 27 ms 27 ms 70.159.210.122
4 43 ms 27 ms 27 ms 70.159.210.119
5 29 ms 29 ms 27 ms 12.81.32.148
6 27 ms 27 ms 27 ms 12.81.32.41
7 27 ms 25 ms 27 ms 74.175.192.134
8 35 ms 37 ms 39 ms cr1.nsvtn.ip.att.net [12.122.148.14]
9 39 ms 39 ms 35 ms cr2.attga.ip.att.net [12.122.28.105]
10 35 ms 37 ms 33 ms attga02jt.ip.att.net [12.123.22.153]
11 35 ms 39 ms 35 ms 192.205.35.170
12 56 ms 55 ms 64 ms grande.TenGE10-2.br02.dal01.pccwbtn.net [63.218.23.126]
13 49 ms 51 ms 51 ms xe-0-0-0-0.core01.gf01.dllstx.grandecom.net [24.155.121.82]
14 54 ms 53 ms 53 ms xe-0-0-1-0.aggr08.wacotx.grandecom.net [24.155.121.42]
15 53 ms 55 ms 53 ms 24-155-191-116.static.grandenetworks.net [24.155.191.116]
16 53 ms 53 ms 53 ms 173.0.128.42
17 53 ms 53 ms 53 ms 173.0.129.102
And here’s web16
Tracing route to web16.vdghosting.net [173.0.129.96]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms home
2 26 ms 25 ms 25 ms x
3 28 ms 27 ms 29 ms 70.159.210.122
4 28 ms 27 ms 27 ms 70.159.210.119
5 28 ms 27 ms 27 ms 12.81.32.144
6 53 ms 25 ms 25 ms 12.81.32.47
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
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.
21 * * * Request timed out.
Are there any updates on this issue? E-mails are turning into phone calls now!
I didn’t get a reply ticket BCK-77018-287 - if I need to I’ll open a new one.
Also, I do have access to at least one machine on ATT DSL, so I can run additional Trace Routes if needed - and I might be able to get remote access to another network also using ATT.
Thanks!
The issue is complex, they are blocking sites that may have malware impact, BY IP. Right now, we are doing an AV scan on web16 and moving items that are detected, we’ve done this on windows side in past but not on linux, however with the recent outbreak in joomla attack bots it has some malware on some domains, and being cleaned up/off.
Thanks for the efforts - I was doing some reading and there are quite a few examples of AT&T blocking servers and even subnets in their battles!
It’s too bad it’s so difficult - you’d think that at the AT&T / JodoHost level there would be better communication AND cooperation!
If it looks like it’s not going to happen fairly soon, can you notify us so we can start moving sites off of Web16?
In my local area (Nashville, TN) AT&T absolutely dominates the ISP market, so while this might not have a huge nationwide impact, for me and my clients it’s basically like being shut down!
I am sorry about that, the biggest issue in the matter is that ATT is doing with without sending abuse notices. We asked for them on Friday, maybe Thursday, we got a reply, but haven’t been updated about it, and whatever malware one network tech was blocking there, seems to have blocked it again because we wernet sent an abuse notice to remove it, and the others didn’t know.
Frankly, ATT is being quite irrational in blocking entire subnets (not here, but sometimes) for what is a normal abuse channel issue, if reported. Once last year they blocked all access on att to a server, because some customer here sent a spam. We had already removed customer 3 days prior to the block, but they didn’t do a report at time of block, so we didn’t know what the cause was.
oh yes, timeframe, we are hoping unblocked today. We are in communications with them now.