The Original Gay Porn Community - Free Gay Movies and Photos, Gay Porn Site Reviews and Adult Gay Forums

  • Welcome To Just Us Boys - The World's Largest Gay Message Board Community

    In order to comply with recent US Supreme Court rulings regarding adult content, we will be making changes in the future to require that you log into your account to view adult content on the site.
    If you do not have an account, please register.
    REGISTER HERE - 100% FREE / We Will Never Sell Your Info

    PLEASE READ: To register, turn off your VPN (iPhone users- disable iCloud); you can re-enable the VPN after registration. You must maintain an active email address on your account: disposable email addresses cannot be used to register.

********** 404 error

GamerBear

( ̄(エ) ̄)
Joined
Apr 26, 2009
Posts
11,961
Reaction score
10
Points
38
Location
Portland
Looks like ********** is working for me. I haven't received any kind of 404 error have you tried to see if it works on another file or is it the entire website?
 
Maybe your ISP is blocking it; mine blocked http://www.megaupload.com for a while, though megaupload.com (no WWW) still worked fine. :) Try hitting both **********.de and **********.com, with and without WWW, to see if any of the four combinations lets you through.

Also, run a TRACERT **********.com (and **********.de) from the command prompt (cmd-dot-exe) to see if it's just congestion or problems along the way with your route (you'll see high time values or timeouts) - or if host can't be resolved.

Try checking your Windows "hosts" file to see if some anti-virus program or something added ********** in, which means it's blocked at your local PC and not your ISP.

Also, try hitting through http://www.anonymouse.org and see what you get.
 
Also, run a TRACERT **********.com (and **********.de) from the command prompt (cmd-dot-exe) to see if it's just congestion or problems along the way with your route (you'll see high time values or timeouts) - or if host can't be resolved.

that wouldn't end in a 404.

looking at the hosts file might be a good idea though. I smell malware.
 
that wouldn't end in a 404.

Yeah, I was thinking of some of the differing/weird methods ISPs or corporations have used to block traffic, or proxies inbetween that react weirdly (like the below). I was thinking of running the Tracert to see if he's getting all the way to the "real" ********** or being intercepted/blocked right at the ISP or along the way (DNS redirects for instance, like you said about malware, which might even change DNS servers to its own) - in any case Tracert is fun and can't hurt :) :

Some proxy servers generate a 404 error when the remote host is not present, rather than returning the correct 500-range code when errors such as hostname resolution failures or refused TCP connections prevent the proxy server from satisfying the request. This can confuse programs that expect and act on specific responses, as they can no longer easily distinguish between an absent web server and a missing web page on a web server that is present.
 
Its strange. I can access the site and all links to its files now, just as long as i add an 'S' after the http in the url.

If i try to go to page without the mod, it 404's me.

I didn't know ********** offered secure HTTP, but I tried https:// now and it works - hey, what do you know? :) But HTTP and HTTPS use different port numbers, so it's possible your ISP, an overzealous firewall/antivirus/child filter, some malware, etc. is blocking ********** on the standard HTTP port 80, but they didn't bother for HTTPS which defaults to 443. Who knows, maybe they had some denial-of-service attack and won't serve pages to a certain IP range for a period of 24 or 48 hours until it passes. Could be a bunch of different things. You can still try my suggestions in my original reply. Glad you have the workaround.
 
I didn't know ********** offered secure HTTP, but I tried https:// now and it works - hey, what do you know? :) But HTTP and HTTPS use different port numbers, so it's possible your ISP, an overzealous firewall/antivirus/child filter, some malware, etc. is blocking ********** on the standard HTTP port 80, but they didn't bother for HTTPS which defaults to 443..

mitchymo, you didn't mention whether you use some firewall or antivirus. IF that is happening on an ISP level it would be quite a concern for me and i would ask them about it, and even (depending on their answer) change the ISP.
 
Others are seeing it as well - interestingly, they're all from the UK. So maybe it's an ISP in common?
 
Back
Top