Home Network Redirects MyE28.com to 127.0.0.1 Local Host

unt0uchable · Post by **unt0uchable** » Nov 28, 2013 9:33 PM

Any idea why? It does it on any device connected to my Wi-Fi. IPad, tablet, cellular, laptop. All get the same redirect. I've tried resetting my home network, used two different routers (uverse and d link media router)

Any help would be great. Everything was working great. I hooked up the d link last Sunday and it's been fine until today I guess. My IP is 108.64.176.211 on the phone Wi-Fi.

Hope this is enough info. Thanks for any help! I must wanna browse on something larger than my phone, lol.

KegCoyote · Post by **KegCoyote** » Nov 29, 2013 1:16 AM

This sounds more like an issue on your ISP side than the the forum's servers. Possibly on your DSL/Cable/Fiber modem side, or on their side blocking you. I can't give much more help than that. Have you tried tried pinging the site? Google search 'ping (your operating system)' and it should tell you how.

unt0uchable · Post by **unt0uchable** » Nov 29, 2013 7:30 AM

I did ping the site last night and it went through, didn't time out. But, alas, I woke up this morning and I am posting this from my laptop on my home network. Who knows what was going...but now I also connected to the wifi with my cell and it is working too. Must have just been a hiccup....

Post by **Jeremy** » Nov 29, 2013 1:02 PM

Sounds like whatever DNS your router connects to got confused temporarily.

unt0uchable · Post by **unt0uchable** » Dec 04, 2013 9:46 AM

Thankfully it is now unconfused. I was worried.

Post by **tig** » Dec 09, 2013 4:22 PM

I get this almost every time I try to access mye28 from Amazon's corp network. Every rare time I'll get access.

This has been going on for about two weeks.

My meetings have become far more productive as a result, but I'm a less happy person.

It seems that enough people have seen this (and the possibly related "403 Forbidden" errors) that it is due to a problem with this site.

Post by **mooseheadm5** » Dec 09, 2013 4:26 PM

Did you mean to reply to a different post? This guy's problem was his ISP or router, and nothing to do with the MyE28 server.

Post by **tig** » Dec 09, 2013 4:46 PM

mooseheadm5 wrote:Did you mean to reply to a different post? This guy's problem was his ISP or router, and nothing to do with the MyE28 server.

Yes, because I'm getting the 127.0.0.1 behavior, not the 403 now.

The OP didn't actually do anything to fix his problem; it just started working again. He never concluded it was a home network or ISP problem, just that the problem went away.

I could have created ANOTHER 127.0.0.1 thread, in addition to this one or the other that I found. I choose to re-use an existing thread that had no clear resolution.

Post by **mooseheadm5** » Dec 09, 2013 4:52 PM

The problem here is not anything to do with MyE28 though. It is to do with your (or your company's) equipment or settings.

What happens when you use another browser?

Post by **tig** » Dec 09, 2013 5:07 PM

mooseheadm5 wrote:The problem here is not anything to do with MyE28 though. It is to do with your (or your company's) equipment or settings.

What happens when you use another browser?

The problem occurs in IE, Chrome and Firefox.

Like most networking issues like this it takes two to tango and since no other sites appear to have this problem, AND at least two other mye28 users have seen this issue, it is reasonable to believe that something in the way mye28.com is configured could be changed to fix the problem.

Post by **mooseheadm5** » Dec 09, 2013 5:22 PM

Or it could be a corporate firewall/routing issue. At least 2 out of a few thousand have reported an issue like this. Pretty small percentage.

Justin_FL · Post by **Justin_FL** » Dec 09, 2013 5:47 PM

Or it could be failure to read the actual error text pasted into his other thread and my recommendation to visit the Stop Forum Spam website to get his IP unblocked.

I'm on my phone so I can't post more details right now.

Post by **mooseheadm5** » Dec 09, 2013 5:49 PM

Justin_FL wrote:Or it could be failure to read the actual error text pasted into his other thread and my recommendation to visit the Stop Forum Spam website to get his IP unblocked.

I'm on my phone so I can't post more details right now.

I suppose it could be that too

Post by **tig** » Dec 09, 2013 6:40 PM

mooseheadm5 wrote:
Justin_FL wrote:Or it could be failure to read the actual error text pasted into his other thread and my recommendation to visit the Stop Forum Spam website to get his IP unblocked.

I'm on my phone so I can't post more details right now.
I suppose it could be that too

Or, it could be that I *did* do as you suggested. And the 403 problems have stopped. And the 127.0.0.1 problems started.

Nowhere in any of these messages did either of you suggest that the 127.0.0.1 problem is also caused by the Stop Forum Spam system, until now.

I have to assume that if this IS the case (as you seem to think it is) that I need to know what OTHER Amazon IP addresses Stop Forum Spam has blacklisted. However, the 127.0.0.1 redirect problem provides no information of the IP address that was used.

I've asked the Amazon helpdesk to look into this. Hopefully this will resolve this for me.

Guys, I appreciate you are volunteers, and I know running a site like this can be a PITA (I've done it). Thanks for all you do.

Justin_FL · Post by **Justin_FL** » Dec 09, 2013 9:12 PM

cek wrote:Or, it could be that I *did* do as you suggested. And the 403 problems have stopped. And the 127.0.0.1 problems started.

Well, that is good to know now. Did you get a reply or any indication the block was being investigated? The IP is still in the database: http://www.stopforumspam.com/ipcheck/54.240.196.186

Until it gets removed, there will be problems-- but since I'm on a PC and have FTP access I wrote a rule exempting 54.240.196.186 until SFS removes the entry. Like most blacklists it is built by submissions so the system won't be perfect.

cek wrote:Nowhere in any of these messages did either of you suggest that the 127.0.0.1 problem is also caused by the Stop Forum Spam system, until now.

I didn't say that-- there are separate root causes, but the odds of the behavior weren't lost on me. So I checked into the ZB Block config and found what was happening. The worst action ZB Block will take is serving a "503 Service Unavailable" page to IPs that end up on a behavior algorithm based 24-hour block according to a points system. But, if you continue hitting the site and adding points, after so many attempts, ZB Block will tell you to f-off with the redirect to 127.0.0.1. I didn't realize that was even an option until combing the config file just now and I don't like it (unfriendly, so redirect is now off). Designed to stop dumb bots.

The OP of this thread was blocked too and he would have first seen a 403 page with a different "Why Blocked" text but then kept trying repeatedly to load the website enough to get redirect blocked. But his block cleared itself up after the timeout period. Your (CEK) IP was listed no less than 8 times in the temporary block list, so you must have ADD and went berserk while being blocked for the SFS violation-- would have taken more than 24 hours for them to clear out

Since I'm on a computer I was able to pull the logs and resolve the OPs issue. The OP's issue was possibly from an older Android OS tablet with a really generic browser user agent that had enough in common with popular spam bots to get flagged.

Also... for anyone reading, it IS helpful to use the link from the 403 block page to send an email message about the issue. These go right into a mailbox that pushes a notification to my phone so I get them right away. I don't always check in everyday on the forum. If it wasn't for CEK posting about a separate incident I wouldn't have known of the OPs false positive triggering the block script.

Post by **tig** » Dec 09, 2013 11:01 PM

Excellent sleuthing. Thanks.

fwiw, I don't have ADD. Or at least not bad enough to look like a spammer. I suspect there ar other people at my company reading mye28 during their lunch breaks. :-)

Also, when I first saw the 403 error, I *did* submit an email. I think i got a DNR (hence my posting via my phone).