Waiting for 127.0.0.1...

[Xen]

Installed Folding@Home for the first time 3 or 4 days ago. At first everything seemed to work fine, for a few hours, then I started having problems with Web Control. I initially used Chrome, until the page started to constantly refresh itself, and a message appeared at the bottom saying "Waiting for 127.0.0.1...". So I moved to Safari. That stopped the constant page refreshing, but when I clicked on "See Stats", I got a "Bad Gateway" message. I tried on Firefox and got exactly the same thing. I then tried removing the firewall, and that made no difference.

Any ideas?

[Joe_H]

The problem with Chrome is known, Google changed something within it a few months ago and now Web Control doesn't work well. Sometimes clearing Chrome's cache helps.

As for Safari, I find on recent versions of it I can get Web Control to work by changing the https in the URL to http.

[Xen]

Thanks but it didn't work. I'll continue to try to find a solution elsewhere, but I confess I'm disappointed. If your web software doesn't work with what I understand is the single most popular web browser, there's an argument you should fix it.

[John_D]

Um, given the Bad Gateway being overloaded, and given that I will bet that a proxy was set which points to the computer's default NIC, which should not be needed of number set 127.0.0.1. In fact, it is possible that a loop was caused which caused the NIC to hang. Leave the port defaulted at 8080 though, it needs to be there. saying ant more about this would be guessing, but that exact thing happened in Cisco class.

I have noted that the default proxy is set to 127.0.0.1 by default though.

[bruce]

FAHControl or WebControl are both available to manage what FAHClient is doing. Those processes communiate with each other by sending message through your TCP/IP services which loop back into another part of your computer by way of your NIC.

If FAHControl or WebControl cannot contact FAHClient using that method, you'll see that message. Either FAHClient is no longer running or a firewall is blocking that connection. My first guess is that FAHClient is NOT running. Reboot and see if that starts everything correctly. If that, too, fails, reinstall using he same userid that's going to run FAH.

[RandyGrot]

thank you

[RandyGrot]

I have the same problem Waiting for 127.0.0 Bad Gateway.. How do I fix?