Unable to access web site

Community support
#1

Ok, here’s the problem. I have a small website hosted on 000webhost (which, by the way, has been MUCH better than the last free host I used). A couple of days ago, I noticed my website wouldn’t load. It’s a “page cannot be displayed” type of error, so it’s not a code/permissions/404 problem. I’ve seen a few posts on here about temporary bans (2000+ connections/day), so I figured I’d give it a day or two (even though I’m pretty sure my site wouldn’t get anywhere near 2000+ connections/day from my IP or anyone elses) . Well, it’s a few days later now, and unfortunately, it still doesn’t work.

I thought it might be DNS related (I have a free subdomain), but I’ve since ruled that out. A name lookup against my subdomain returns 31.170.161.156 (from my DNS cache and from 000webhost’s DNS servers). Not sure which 000webhost server that IP corresponds to, but cpanel says my site is on server41 (with a different IP of 31.170.160.105).

After some more testing, I figured out the following:

[LIST]
[]I can’t access my site from my PC or from another PC on my local network
[]I can access my site through a web browsing proxy.
[]I can access my site if I edit my host file and point my subdomain to 31.170.160.105.
[]I can access my site if I connect to my neighbors open wifi (which undoubtedly, they’ve left open because security is just too much of a bother :rolleyes:). My neighbor uses a different ISP and a DNS lookup for my subdomain to their DNS server resolves to 31.170.161.156.
[]I can’t access ANY sites (not just mine) ending in webege.com that resolve to 31.170.161.156.
[]I do not have any IPs configured in the “Deny Access” list.
[/LIST]

So, unless I missed something, I’m left with two possibilities:

[LIST=1]
[]My ISP is blocking access to 31.170.161.156.
[]31.170.161.156 is blocking my IP.
[/LIST]

So, is there any reason why my IP would be blocked for this long on a single 000webhost server?

If not, I guess I’m left with the first conclusion. I kind of doubt my ISP will care one bit about this problem (it’s one of those large corporations that doens’t mind stepping on a few customers here and there), so if that’s the case, is there some way I can get my site moved to a different server or have the host record for my subdomain pointed to the other IP?

Thanks in advance for any assistance.

#2

Hi,

I can access your site perfectly ok, and your sub-domain resolves to the IP 31.170.161.156 on my ISP.

It appears that, the issue is one of the listed possibilities, either a site hosted on the same IP as yours has been reported to your ISP for whatever reason and they have blocked the IP, or the 000webhost server has blocked your IP.

A suggestion though… If you are assigned Dynamic IP address by your ISP (most connections are for security and due to the lack if IPv4 addresses), try unplugging your router overnight, thus ensuring the DHCP assignment of your IP expires, then reconnect, you should be assigned a new IP, hence eliminating the 000webhost server blocking your IP.

  • A quick edit… Your site cannot be moved to a different IP as the TLD name is tied to server. The server may have 2 IPs but resolves to the 105 address as failover (maybe). The only other fix is the manual HOST file edit :slight_smile:
#3

mopedmaniac,

Thanks for the information. I tried leaving my router unplugged overnight (8+ hours), but it still pulled the same IP address from my ISP :(. From looking on some other forums, it looks like my ISP may hand out IPs based on some sort of device ID (possibly the MAC address) on the modem (which they provided). I’m pretty sure it’s changed at least once since I subscribed, but I think it may change based on a fixed time (i.e. swap every 6 months or something of the like).

I tried running a trace route to 31.170.161.156, and here’s what I got:

Tracing route to 31-170-161-156.main-hosting.com [31.170.161.156]
over a maximum of 30 hops:

(First 10 hops omitted)

11 33 ms 33 ms 32 ms cr1.attga.ip.att.net [12.122.141.186]
12 30 ms 30 ms 30 ms attga02jt.ip.att.net [12.123.22.25]
13 30 ms 30 ms 30 ms 192.205.36.238
14 30 ms 30 ms 31 ms te0-0-0-1.mpd22.atl01.atlas.cogentco.com [154.54.3.145]
15 30 ms 30 ms 30 ms te8-8.ccr01.atl04.atlas.cogentco.com [154.54.3.170]
16 41 ms 34 ms 35 ms 38.122.46.90
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 41 ms 47 ms 41 ms dtr01ahvlnc-tge-3-4.ahvl.nc.charter.com [96.34.67.175]
23 40 ms 40 ms 40 ms 68-115-195-86.static.spbg.sc.charter.com [68.115.195.86]
24 40 ms 40 ms 45 ms 67.23.161.251
25 40 ms 40 ms 40 ms ashv1.main-hosting.com [208.69.231.10]
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

I tried the same on my neighbors WIFI, and the last hop successfully connects to 31-170-161-156.main-hosting.com [31.170.161.156]. So, now I’m leaning towards the second of the two possibilities.

I have no idea why my IP would be blocked by the 000webhost server. However, since this probably only affects me, I’ll just work around it by putting an entry in my hosts file. My ISP should give me a new IP eventually, and I’ll try it again then.

Once again, thanks for the help.

#4

Can you see your site using a proxy? www.hidemyass.com
Just to add that the site in your profile works fine for me.

#5

Shock,

I can access my site through a web browsing proxy.

The problem appears to be some sort of IP blocking rule that’s preventing my IP from accessing 31.170.161.156. Since I can get to my site on 31.170.160.105, I’ve changed my hosts file accordingly.

#6

ComputerGuy, I have been having the same problem, with the same IP addresses.

After numerous conversations with my ISP (Comcast), I have learned that another site hosted on server41 has been flagged as a phishing site. As of today, that site has been taken down, and the Comcast agent told me that my site will be back up within 24 hours.

Hopefully we’ll both be back up tomorrow!

#7

My site is now visible via Comcast!

#8

Olive,

I can access my site now as well (on the correct IP). My ISP is AT&T, but I guess they share the same block list . Thanks for letting me know. :slight_smile:

#9

A post was split to a new topic: Unable to Access Web Site (NEW)