Folding Forum

PS For those getting the 407 error, could you do a test for us? Could you run the 6.20 client in uniprocessor mode and see if you get the same 407 error? If you do or don't would be useful info for us (6.22 is based off of 6.20).

The proxy password scrambling was corrupting config files, and had to be removed. So you will have to delete your config file and reconfigure if you move from 5.x to 6.x.

Well, if this might be helpful... Just as a workaround one may try to install additional "cascading" proxy. I used CCProxy.

We only support the basic HTTP proxy protocol in the 6.x clients. If you have a more elaborate (Microsoft) proxy setup, I would recommend either the 5.x client and the IE settings (warning: may or may not work either, they kept changing the APIs) or to use proxy software, and I can second Galahad's CCProxy recommendation, it's nice.

Just a reminder... if you are in a situation where you need to use an HTTP proxy to get on the web, you are probably _ALSO_ in a situation where your boss or the IT guys may not react 100% kindly to Folding@home (or Solitare), so be sure you have the blessings of the powers that be - since we're not talking about home cable/DSL modems here.

I don't need any more emails from freaked out IT departments in my lifetime, and neither does Vijay. Only 14 days since the last one

Beberg wrote:We only support the basic HTTP proxy protocol in the 6.x clients. If you have a more elaborate (Microsoft) proxy setup, I would recommend either the 5.x client and the IE settings (warning: may or may not work either, they kept changing the APIs) or to use proxy software, and I can second Galahad's CCProxy recommendation, it's nice.

Just a reminder... if you are in a situation where you need to use an HTTP proxy to get on the web, you are probably _ALSO_ in a situation where your boss or the IT guys may not react 100% kindly to Folding@home (or Solitare), so be sure you have the blessings of the powers that be - since we're not talking about home cable/DSL modems here.

I don't need any more emails from freaked out IT departments in my lifetime, and neither does Vijay. Only 14 days since the last one

Yes, my workplace have a proxy and the coworkers in the networking infrastructure (I'm in the IT staff as well, Senior Tech support) are pretty nervous about that so it's forbidden for everyone. Myself, I only get permission for pre-production machines for testing purpose (while helping the science at the same time) so make sure you get the proper permission to run it.

Not to be a pain or anything but how is this issue coming along for resolution?

Thanks,

Broken

Since the client hasn't been updated (still 6.22), there is nothing new about this issue.

You can still use the v5.9x based on the old core that should work.

Maybe it could be listed in the Known Bugs posting then? It seems to be missing from that.

BrokenWolf

VijayPande wrote:PS For those getting the 407 error, could you do a test for us? Could you run the 6.20 client in uniprocessor mode and see if you get the same 407 error? If you do or don't would be useful info for us (6.22 is based off of 6.20).

I have done this and the 6.20 uniprocessor client also has the same problem. Both the console, console as a service and the gui client.

BrokenWolf

I've asked Adam to look into this. The problem here is that your proxy may be different and it's hard to debug it when we don't have access to it. We are looking into our options.

To look into proxies that are not working with basic auth (Microsoft protocol is covered above) we need to know the proxy software you are using, the version, and the configuration (pass through, caching proxy, etc). Without this information there is nothing we can do to look into it.

If running Folding@home is against your company IT policy, do not ask the IT dept for this info, they will wonder why you are asking.

I'm part of the IT organization so it is not a problem for me to get more details. We have 2 different style proxy systems. For our everyday use/normal users we have the NetCache (Blue Coat) proxies (handled by our Network Security group) that also cache the data. I get the 407 error on those as well as the Microsoft ISA 2004 SP3 (soon to be 2006) that my group admins. I don't know the exact config as I only know enough about ISA to be dangerous. I know it is also a caching proxy.

I can not get the client to connect even on the initial setup of the client with a -configonly switch. It does not connect with my domain account information or a local test account on one of the proxies on either the NetCache or ISA. I get the 407 errors and it never gets a client ID.

The Linux 6.02 SMP client (we have quite a few of these running in VMware on some dev and test hosts) works fine with either the NetCache or the ISA proxies (domain account or local test) as do the 5.91 SMP and 5.04 console clients.

If I knew what exact info you would like me to I can do my best to find it (I do have view access on the ISA servers).

Broken

Good mornig Everybody,

I'm Brazilian and at first I'd like to say say that I'm sorry about my English.

I'm new at Folding@home and I'm having a problem with Proxy configuration. I've installed the Folding@home client in some computers but I realized that the ones under proxy are unable to pass through it. I cheched my username and password, proxy server addres and port and they are all correct.

Does somebody know what I can do to fix this problem?

I'm the Network Administrator at the place I work for and I'll take a look at my Proxy Server. If I realize something that can be usefull I'll keep you guys informed.


Below I put a part of the Log file so you can check it.

"# Windows CPU Systray Edition

Folding@Home Client Version 6.20

[11:36:04] - Ask before connecting: No
[11:36:04] - User name: pollyanderson (Team 150794)
[11:36:04] - User ID not found locally
[11:36:04] + Requesting User ID from server
[11:36:25] - Couldn't send HTTP request to server
[11:36:25] + Could not connect to Primary Assignment Server for ID
[11:36:46] - Couldn't send HTTP request to server
[11:36:46] + Could not connect to Secondary Assignment Server for ID
[11:36:46]
+ Could not get ID from server. Retrying...
[11:36:53] - Couldn't send HTTP request to server
[11:36:53] (Got status 407)
[11:36:53] + Could not connect to Primary Assignment Server for ID
[11:36:54] - Couldn't send HTTP request to server
[11:36:54] (Got status 407)
[11:36:54] + Could not connect to Secondary Assignment Server for ID
[11:36:54]
+ Could not get ID from server. Retrying..."

There is a known bug in v6 client with proxies with authentication

There is one possible workaround you could try : set up a "local" proxy on the machine without authentication, and configures your FAH client to connect to it ... then set up the "local" proxy to authenticate to the regular proxy. If you have many clients, you might only install one "local" proxy, and set your clients to connect to it.

toTOW wrote:There is a known bug in v6 client with proxies with authentication

There is one possible workaround you could try : set up a "local" proxy on the machine without authentication, and configures your FAH client to connect to it ... then set up the "local" proxy to authenticate to the regular proxy. If you have many clients, you might only install one "local" proxy, and set your clients to connect to it.

Ok. I did it. Maybe this problem is related with the configurations of the proxy server. I'll take a look at my Squid.conf and try to discover something to help the people who is passing through the same problem.

Any news, please keep me aware. I'll do the same.

Thank you