Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Can't reach a certain website

J

jones989

macrumors newbie
Original poster
Jan 19, 2013
17
0
So here it goes,

There is a certain website, creeperhost.net, that I, no matter what, cannot get on to.

1. My firewall is off.
2. I did a DNS Cache clear.
3. I tried on Firefox, Safari, and Chrome.
4. None of the proxies are check.
5. I tried changing my DNS to the Google DNS.
6. It worked on other PCs in the same network.

When I try a proxy, it works, but I want to access this website without a proxy.

When using Chrome I get this:

Code: 
Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data

I have a Macbook, 13-inch, Mid 2010 with a 2.4 GHz Intel Core 2 Duo and 2 GB 1067 MHz DDR3 with OS X 10.8.2.
Help?
 
Last edited:
Still having a problem. By the way, other PCs in the house connected to this website no problem.
 
jones989 said:
Still having a problem. By the way, other PCs in the house connected to this website no problem.
Click to expand...

Yes, I should have read more carefully.

Open Terminal (in Utilities) and enter

Code: 
more /etc/hosts

Please post the result.
 
jones989 said:
So here it goes,

There is a certain website, creeperhost.net, that I, no matter what, cannot get on to.

1. My firewall is off.
2. I did a DNS Cache clear.
3. I tried on Firefox, Safari, and Chrome.
4. None of the proxies are check.
5. I tried changing my DNS to the Google DNS.
6. It worked on other PCs in the same network.

When I try a proxy, it works, but I want to access this website without a proxy.

When using Chrome I get this:

Code: 
Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data

I have a Macbook, 13-inch, Mid 2010 with a 2.4 GHz Intel Core 2 Duo and 2 GB 1067 MHz DDR3 with OS X 10.8.2.
Help?
Click to expand...
I am having the same problem! Take a look at my thread.

https://forums.macrumors.com/threads/1523585/

What worked for me was creating a new account, but I haven't been able to get it working on my regular account.
 
For the traceroute,

Code: 
Traceroute has started…

traceroute to 5.133.183.28 (5.133.183.28), 64 hops max, 72 byte packets
 1  * * *
 2  * *traceroute: sendto: No route to host
traceroute: wrote 5.133.183.28 72 chars, ret=-1
 *
traceroute: sendto: Host is down
 3 traceroute: wrote 5.133.183.28 72 chars, ret=-1
 *traceroute: sendto: Host is down
traceroute: wrote 5.133.183.28 72 chars, ret=-1
 *traceroute: sendto: Host is down
traceroute: wrote 5.133.183.28 72 chars, ret=-1
 *
 4  * * *
 5  * *traceroute: sendto: No route to host
traceroute: wrote 5.133.183.28 72 chars, ret=-1
 *
traceroute: sendto: Host is down
 6 traceroute: wrote 5.133.183.28 72 chars, ret=-1
 *traceroute: sendto: Host is down
traceroute: wrote 5.133.183.28 72 chars, ret=-1
 *traceroute: sendto: Host is down
traceroute: wrote 5.133.183.28 72 chars, ret=-1
 *
 7  * * *
 8  * *traceroute: sendto: No route to host
traceroute: wrote 5.133.183.28 72 chars, ret=-1
 *
traceroute: sendto: Host is down
 9 traceroute: wrote 5.133.183.28 72 chars, ret=-1
 *traceroute: sendto: Host is down
traceroute: wrote 5.133.183.28 72 chars, ret=-1

and for the ping,

Code: 
Ping has started…

ping: sendto: No route to host
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
PING 5.133.183.28 (5.133.183.28): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8

--- 5.133.183.28 ping statistics ---
10 packets transmitted, 0 packets received, 100.0% packet loss
 
jones989 said:
For the traceroute,

Code: 
Traceroute has started…

traceroute to 5.133.183.28 (5.133.183.28), 64 hops max, 72 byte packets
 1  * * *
 2  * *traceroute: sendto: No route to host
traceroute: wrote 5.133.183.28 72 chars, ret=-1
 *
traceroute: sendto: Host is down
 3 traceroute: wrote 5.133.183.28 72 chars, ret=-1
 *traceroute: sendto: Host is down
traceroute: wrote 5.133.183.28 72 chars, ret=-1
 *traceroute: sendto: Host is down
traceroute: wrote 5.133.183.28 72 chars, ret=-1
 *
 4  * * *
 5  * *traceroute: sendto: No route to host
traceroute: wrote 5.133.183.28 72 chars, ret=-1
 *
traceroute: sendto: Host is down
 6 traceroute: wrote 5.133.183.28 72 chars, ret=-1
 *traceroute: sendto: Host is down
traceroute: wrote 5.133.183.28 72 chars, ret=-1
 *traceroute: sendto: Host is down
traceroute: wrote 5.133.183.28 72 chars, ret=-1
 *
 7  * * *
 8  * *traceroute: sendto: No route to host
traceroute: wrote 5.133.183.28 72 chars, ret=-1
 *
traceroute: sendto: Host is down
 9 traceroute: wrote 5.133.183.28 72 chars, ret=-1
 *traceroute: sendto: Host is down
traceroute: wrote 5.133.183.28 72 chars, ret=-1
Click to expand...

You aren't even reaching your router with that traceroute. Do you have any third-party apps that might be blocking access? Other posts mention issues with PeerGuardian/PeerBlock and LogMeIn.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back