Please register to participate in our discussions with 2 million other members - it's free and quick! Some forums can only be seen by registered members. After you create your account, you'll be able to customize options and access all our 15,000 new posts/day with fewer ads.
Tried to FTP onto my website tonight through Exede and then earthlink and found broken links to it and to the hosting company. Used Firefox on Exede to see if would come up and no. Then tried a proxy server and stuff came up. Used TOR and everything was fine. I know that in the past Exede had problems resolving the .gov domains. So - did the hosting company have downtime, or were there DNS issues or what? On exiting TOR, the sites are gone again.
Last edited by harry chickpea; 08-13-2013 at 10:21 PM..
Have you contacted your host to find out if they know anything about it? It's possible that your IP got blocked. Some servers (especially cPanel) will block an IP if there are too many failed password attempts.
Have you contacted your host to find out if they know anything about it? It's possible that your IP got blocked. Some servers (especially cPanel) will block an IP if there are too many failed password attempts.
That's why I asked about the earthlink connection, the other one is satellite and I have had legitimate traffic from people using satellite services hammering my server in the past for files that didn't even exist. Something like that could easily be mistaken for malicious traffic and get firewalled.
That's why I asked about the earthlink connection, the other one is satellite and I have had legitimate traffic from people using satellite services hammering my server in the past for files that didn't even exist. Something like that could easily be mistaken for malicious traffic and get firewalled.
I'm not aware of any common apps that will automatically block an IP based on repeated 404s, but that's not to say a web host couldn't write one on their own. Usually we only block IPs based on failed password attempts or spam.
Still, I think that's where OP's problem exists. Either there's a bad route between ISP #1 and his host, or ISP #1 got firewalled. The first step here should be to contact the web host and ask for assistance.
OP, try doing a traceroute to your host. In Windows, open up a command prompt and type tracert example.com where "example.com" is your hostname. It will take 20 - 30 seconds and you should get something like this:
Quote:
Tracing route to [184.82.65.12] over a maximum of 30 hops:
1 3 ms 1 ms 1 ms 192.168.43.1
2 176 ms 40 ms 39 ms 133.sub-.myvzw.com [---.---.---.---]
3 77 ms 40 ms 38 ms 242.sub-69-83-29.myvzw.com [69.83.29.242]
4 55 ms 47 ms 30 ms 33.sub-69-83-29.myvzw.com [69.83.29.33]
5 68 ms 39 ms 39 ms 49.sub-69-83-29.myvzw.com [69.83.29.49]
6 79 ms 37 ms 45 ms 194.sub-69-83-29.myvzw.com [69.83.29.194]
7 87 ms 48 ms 45 ms 192.sub-69-83-19.myvzw.com [69.83.19.192]
8 80 ms 48 ms 34 ms 201.sub-66-174-9.myvzw.com [66.174.9.201]
9 72 ms 39 ms 39 ms 216.55.43.25
10 * * * Request timed out.
11 62 ms 49 ms * 207.88.14.178.ptr.us.xo.net [207.88.14.178]
12 96 ms 100 ms 100 ms 209.220.16.206.ptr.us.xo.net [209.220.16.206]
13 75 ms 81 ms 53 ms 209.197.17.130
14 104 ms 79 ms 79 ms 209.197.17.134
15 165 ms 47 ms 57 ms xe1-01.gwy02.sctn01.hostnoc.net [64.191.108.37]
16 106 ms 166 ms 89 ms tn1-01.cor02.dupa01.hostnoc.net [64.120.184.121]
17 107 ms 47 ms 80 ms vl0202.agg01.ded.dupa01.hostnoc.net [64.120.184.170]
18 90 ms 89 ms 88 ms ec0-04.bp1202.dupa01.hostnoc.net [64.120.184.218]
19 86 ms 57 ms 73 ms vserver130.hostnoc.net [173.212.239.114]
20 79 ms 58 ms 58 ms barista.freshroastedhosting.com [184.82.65.12]
If they very last line isn't your destination address, or if it ends in * * *, then your route is broken at the step immediately above it. Post that information, and I can help you determine whether it's your host or an intermittent hop.
It was inconsistent, happened last night and seems OK today. Earthlink - pure dial up at 26 (ugh). It was having other problems as well, so after about 20 minutes fiddling it, I went back to sat. My hosting company appears to have bought space from Time Warner or use TWC as its ISP. I verified that neither it (LPChost.com) or my website had been listed as blackholed. I only remembered traceroute after I had gone to bed, thanks for the reminder. I did call Exede, got level one support, which promptly freaked out when I mentioned VPN, and couldn't understand without my repeating it that everything was FINE using a VPN, but not with normal http over their regular route. <sigh>
I was finally able to log in to make the file changes I wanted using the online control panel, but never was able to establish an FTP connection through my local client.
Satellite feed is somewhat odd in that it normally used some heavy compression and forces traffic to its own DNS servers - even if you think you are using google or freeDNS - to accomplish that. The only way around is to proxy, TOR, or VPN. (I think SSL thwarts as well, but only after the DNS lookup)
At this point, I'm tentatively chalking it up to a DNS server hiccup at Exede. A while back it wasn't able to access any .gov weather (pretty sorry for a company whose main reaison-de-etre is military support). It was one of those days yesterday where it all hits the fan. One customer had a hard drive go wonky, another had weird stuff happening with printer drivers and spoolers - which ALSO seems to have self-resolved this morning. Maybe we passed through a band of uglies in the Persiads.
I'm not aware of any common apps that will automatically block an IP based on repeated 404s, but that's not to say a web host couldn't write one on their own.
I wouldn't think it would be common on shared hosting but a lot of webmasters with their own servers go to great lengths to block scrapers and malicious traffic. I'm using APF and BFD and writing a rule for it wouldn't be that hard.
I wouldn't think it would be common on shared hosting but a lot of webmasters with their own servers go to great lengths to block scrapers and malicious traffic. I'm using APF and BFD and writing a rule for it wouldn't be that hard.
CSF is a beautiful thing. It causes a few minor headaches, but it makes a great first line of defense on a public-facing server. It's installed on all of my shared cPanel servers, along with our own tweaks and network-level protections.
Please register to post and access all features of our very popular forum. It is free and quick. Over $68,000 in prizes has already been given out to active posters on our forum. Additional giveaways are planned.
Detailed information about all U.S. cities, counties, and zip codes on our site: City-data.com.
Please register to participate in our discussions with 2 million other members - it's free and quick! Some forums can only be seen by registered members. After you create your account, you'll be able to customize options and access all our 15,000 new posts/day with fewer ads.
I'm using APF and BFD and writing a rule for it wouldn't be that hard. 
