Any update on the Proxy issue/407 errors as of yet?
Moderators: Site Moderators, FAHC Science Team
Re: Any update on the Proxy issue/407 errors as of yet?
Please look at those squid settings...I am trying to set up squid and can't seem to get it running...
I have 20-30k ppd waiting....
I have been trying to get it running since they changed it in July....
I have 20-30k ppd waiting....
I have been trying to get it running since they changed it in July....
-
- Site Moderator
- Posts: 6359
- Joined: Sun Dec 02, 2007 10:38 am
- Location: Bordeaux, France
- Contact:
Re: Any update on the Proxy issue/407 errors as of yet?
Have you read my workaround suggestions ?
5.04 will connect, 6.23 won't
I've installed the 5.04 CPU Windows console client on a few of my machines at work and they generally run fine. I've tried installing the 6.23 CPU client and none of them can connect.
I've just installed an 8800GT in my main machine and the 6.23 GPU client also can't connect to the server.
The 5.04 client will only connect if I select the "Use IE settings" option.
The machines are all on a large corporate network with proxies and firewalls. Although I'm fairly proficient in Windows, I'm not too versed in networking. I've tried to use HTTP tunneler and Sockscap, but haven't made any headway.
Can anyone suggest any solutions?
--- Opening Log file [January 22 01:28:07 UTC]
# Windows GPU Console Edition #################################################
###############################################################################
Folding@Home Client Version 6.23
###############################################################################
###############################################################################
Launch directory: C:\Program Files\Folding@Home\Folding GPU
Executable: C:\Program Files\Folding@Home\Folding GPU\Folding@home-Win32-GPU.exe
[01:28:07] - Ask before connecting: No
[01:28:07] - User name: rtsweene (Team 33)
[01:28:07] - User ID: 3F1412B2680524EB
[01:28:07] - Machine ID: 2
[01:28:07]
[01:28:07] Loaded queue successfully.
[01:28:07] - Preparing to get new work unit...
[01:28:07] + Attempting to get work packet
[01:28:07] - Connecting to assignment server
[01:28:08] - Couldn't send HTTP request to server
[01:28:08] + Could not connect to Assignment Server
[01:28:29] - Couldn't send HTTP request to server
[01:28:29] + Could not connect to Assignment Server 2
[01:28:29] + Couldn't get work instructions.
[01:28:29] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[01:28:46] + Attempting to get work packet
[01:28:46] - Connecting to assignment server
[01:28:48] - Couldn't send HTTP request to server
[01:28:48] + Could not connect to Assignment Server
[01:29:09] - Couldn't send HTTP request to server
[01:29:09] + Could not connect to Assignment Server 2
[01:29:09] + Couldn't get work instructions.
[01:29:09] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
I've just installed an 8800GT in my main machine and the 6.23 GPU client also can't connect to the server.
The 5.04 client will only connect if I select the "Use IE settings" option.
The machines are all on a large corporate network with proxies and firewalls. Although I'm fairly proficient in Windows, I'm not too versed in networking. I've tried to use HTTP tunneler and Sockscap, but haven't made any headway.
Can anyone suggest any solutions?
--- Opening Log file [January 22 01:28:07 UTC]
# Windows GPU Console Edition #################################################
###############################################################################
Folding@Home Client Version 6.23
###############################################################################
###############################################################################
Launch directory: C:\Program Files\Folding@Home\Folding GPU
Executable: C:\Program Files\Folding@Home\Folding GPU\Folding@home-Win32-GPU.exe
[01:28:07] - Ask before connecting: No
[01:28:07] - User name: rtsweene (Team 33)
[01:28:07] - User ID: 3F1412B2680524EB
[01:28:07] - Machine ID: 2
[01:28:07]
[01:28:07] Loaded queue successfully.
[01:28:07] - Preparing to get new work unit...
[01:28:07] + Attempting to get work packet
[01:28:07] - Connecting to assignment server
[01:28:08] - Couldn't send HTTP request to server
[01:28:08] + Could not connect to Assignment Server
[01:28:29] - Couldn't send HTTP request to server
[01:28:29] + Could not connect to Assignment Server 2
[01:28:29] + Couldn't get work instructions.
[01:28:29] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[01:28:46] + Attempting to get work packet
[01:28:46] - Connecting to assignment server
[01:28:48] - Couldn't send HTTP request to server
[01:28:48] + Could not connect to Assignment Server
[01:29:09] - Couldn't send HTTP request to server
[01:29:09] + Could not connect to Assignment Server 2
[01:29:09] + Couldn't get work instructions.
[01:29:09] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
Proxy Behaviour
Been having issues getting the F@H Uni (console) client to work at our school...
We are unique in that we are subordinate to an upstream squid (ht_p basic auth) proxy (out of my control).
Then we have our own ISA2006 proxy (as plain vanilla proxy server, not transparent MS stuff).
i.e. Client ---> ISA ----> Squid ---> Interwebs
ISA does not require auth, Squid Does.
When client is configured to use proxy + auth it keeps getting 407 errors.
The ISA logs also show the 407 errors as they are coming from the upstream Squid proxy. (and before you state the obvious, yes I'm using the right credentials)
Using a browser with the same proxy settings I get OK from..
http://assign.stanford.edu:8080
http://assign2.stanford.edu
http://171.65.103.160
So it's possible...
Issue #1: I'm assuming the way the client handles the auth is failing - perhaps passing the auth to the first server, not the second? Unfortunately I don't have access to the Squid logs.
Issue #2: I tried using a little localhost java proxy program to see what was happening (google 'burpsuite') and oddly I can't the client to send any proxy requests to that either (web browser again works fine).
As a quick workaround...
Issue#3: I configured the ISA server proxy rules so that when requesting certain url's the ISA proxy will auth upstream on behalf of the client (using proxy + no auth on the client itself) and this seems to work okay for now but the list is growing - the client needs to contact ALL the url's below to get going - will there be any more i need to be aware of?
http://171.65.103.160
http://171.67.108.13
http://128.59.74.4
http://assign.stanford.edu:8080
http://assign2.stanford.edu
http://assign2.stanford.edu:80 (for some reason if you use the :80 it needs a separate rule for it..)
http://www.stanford.edu
..but of course this only helps me and doesn't fix the issue that the client does not handle proxy auth correctly
We are unique in that we are subordinate to an upstream squid (ht_p basic auth) proxy (out of my control).
Then we have our own ISA2006 proxy (as plain vanilla proxy server, not transparent MS stuff).
i.e. Client ---> ISA ----> Squid ---> Interwebs
ISA does not require auth, Squid Does.
When client is configured to use proxy + auth it keeps getting 407 errors.
Code: Select all
[02:04:41] Could not open work queue, generating new queue...
[02:04:41] - Preparing to get new work unit...
[02:04:41] + Attempting to get work packet
[02:04:41] - Connecting to assignment server
[02:04:42] - Couldn't send HTTP request to server
[02:04:42] (Got status 407)
[02:04:42] + Could not connect to Assignment Server
[02:04:42] - Couldn't send HTTP request to server
[02:04:42] (Got status 407)
[02:04:42] + Could not connect to Assignment Server 2
[02:04:42] + Couldn't get work instructions.
[02:04:42] - Attempt #1 to get work failed, and no other work to do. Waiting before retry.
Using a browser with the same proxy settings I get OK from..
http://assign.stanford.edu:8080
http://assign2.stanford.edu
http://171.65.103.160
So it's possible...
Issue #1: I'm assuming the way the client handles the auth is failing - perhaps passing the auth to the first server, not the second? Unfortunately I don't have access to the Squid logs.
Issue #2: I tried using a little localhost java proxy program to see what was happening (google 'burpsuite') and oddly I can't the client to send any proxy requests to that either (web browser again works fine).
As a quick workaround...
Issue#3: I configured the ISA server proxy rules so that when requesting certain url's the ISA proxy will auth upstream on behalf of the client (using proxy + no auth on the client itself) and this seems to work okay for now but the list is growing - the client needs to contact ALL the url's below to get going - will there be any more i need to be aware of?
http://171.65.103.160
http://171.67.108.13
http://128.59.74.4
http://assign.stanford.edu:8080
http://assign2.stanford.edu
http://assign2.stanford.edu:80 (for some reason if you use the :80 it needs a separate rule for it..)
http://www.stanford.edu
..but of course this only helps me and doesn't fix the issue that the client does not handle proxy auth correctly
-
- Posts: 179
- Joined: Sun Dec 02, 2007 6:40 am
- Location: Team_XPS ..... OC, S. Calif
Re: 5.04 will connect, 6.23 won't
I'm interested in this too...... Any ideas?..... Gurus/Mods.... please?
Peace
Peace
T.E.A.M. “Together Everyone Accomplishes Miracles!”
OC, S. California ... God Bless All
OC, S. California ... God Bless All
-
- Posts: 10179
- Joined: Thu Nov 29, 2007 4:30 pm
- Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
- Location: Arizona
- Contact:
Re: 5.04 will connect, 6.23 won't
There is a running thread with suggestions here: http://foldingforum.org/viewtopic.php?f=46&t=5477
Maybe a mod can combine this thread with that other thread, as some things are fixed, some are not yet understood fully...
Maybe a mod can combine this thread with that other thread, as some things are fixed, some are not yet understood fully...
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Tell me and I forget. Teach me and I remember. Involve me and I learn.
-
- Posts: 10179
- Joined: Thu Nov 29, 2007 4:30 pm
- Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
- Location: Arizona
- Contact:
Re: Proxy Behaviour
There is a running thread with suggestions here: http://foldingforum.org/viewtopic.php?f=46&t=5477
Edit by Mod: Threads merged.
-b
Maybe a mod can combine this thread with that other thread, as some things are fixed, some are not yet understood fully...
And the fact that this topic keeps popping up indicates either a problem with the software, or a problem with the documentation.
P.S. Welcome to the forum, dynamik.
Edit by Mod: Threads merged.
-b
Maybe a mod can combine this thread with that other thread, as some things are fixed, some are not yet understood fully...
And the fact that this topic keeps popping up indicates either a problem with the software, or a problem with the documentation.
P.S. Welcome to the forum, dynamik.
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Tell me and I forget. Teach me and I remember. Involve me and I learn.
-
- Posts: 179
- Joined: Sun Dec 02, 2007 6:40 am
- Location: Team_XPS ..... OC, S. Calif
Re: 5.04 will connect, 6.23 won't
7im...... OP's log does not indicate a 407 error as the link you mentioned tries to solve.
Will these errors be one and the same? In that case the threads should be combined; otherwise maybe not.
Just an FYI, I would just like to see a reslove.
Off Topic... could you link me to a how-to (simple and foolproof one) to show me how to go back into a Console -regular, not SMP- version (That is set to run as Service) ... so I might be able to re-configure the client? TIA
Peace
Will these errors be one and the same? In that case the threads should be combined; otherwise maybe not.
Just an FYI, I would just like to see a reslove.
Off Topic... could you link me to a how-to (simple and foolproof one) to show me how to go back into a Console -regular, not SMP- version (That is set to run as Service) ... so I might be able to re-configure the client? TIA
Peace
T.E.A.M. “Together Everyone Accomplishes Miracles!”
OC, S. California ... God Bless All
OC, S. California ... God Bless All
Re: 5.04 will connect, 6.23 won't
Thanks for the link 7im.
While it looks like there's no easy fix available, at least they are aware of it and it will hopefully be fixed in the next release.
While it looks like there's no easy fix available, at least they are aware of it and it will hopefully be fixed in the next release.
-
- Posts: 10179
- Joined: Thu Nov 29, 2007 4:30 pm
- Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
- Location: Arizona
- Contact:
Re: 5.04 will connect, 6.23 won't
Searched the fah wiki for "reconfigure" and this was the 4th or 5th link. http://fahwiki.net/index.php/I'm_runnin ... y_settingsMoneyGuyBK wrote:7im...... OP's log does not indicate a 407 error as the link you mentioned tries to solve.
Will these errors be one and the same? In that case the threads should be combined; otherwise maybe not.
Just an FYI, I would just like to see a reslove.
Off Topic... could you link me to a how-to (simple and foolproof one) to show me how to go back into a Console -regular, not SMP- version (That is set to run as Service) ... so I might be able to re-configure the client? TIA
Peace
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Re: Proxy Behaviour
In the past, some people have been able to deal with validation issues by installing a product called proxomitron. I've never used it myself, though, so don't consider this a recommendation, just a suggestion.
Older versions of squid had a maximum upload setting which prevented the uploads of larger result files. Newer versions have removed that cap. If somebody is administering an older version, I can find instructions telling you how to remove the default cap if you want them.
Older versions of squid had a maximum upload setting which prevented the uploads of larger result files. Newer versions have removed that cap. If somebody is administering an older version, I can find instructions telling you how to remove the default cap if you want them.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
Re: Any update on the Proxy issue/407 errors as of yet?
tnx 7im.
bruce: I don't beleive it's a limitation on the Squid proxy because with the workaround I have at the moment it's working OK... and only working OK because my downstream ISA proxy is in the middle authenticating to the upstream Squid proxy on the client's behalf. The problem imo seems to be with the client's (Basic) auth process.
refs:
http://en.wikipedia.org/wiki/Basic_acce ... entication
http://wiki.squid-cache.org/SquidFaq/Pr ... entication
when i get some time i'll see if i can run up a packet trace...
bruce: I don't beleive it's a limitation on the Squid proxy because with the workaround I have at the moment it's working OK... and only working OK because my downstream ISA proxy is in the middle authenticating to the upstream Squid proxy on the client's behalf. The problem imo seems to be with the client's (Basic) auth process.
refs:
http://en.wikipedia.org/wiki/Basic_acce ... entication
http://wiki.squid-cache.org/SquidFaq/Pr ... entication
when i get some time i'll see if i can run up a packet trace...
Last edited by dynamik on Fri Jan 23, 2009 2:29 am, edited 1 time in total.
Re: Any update on the Proxy issue/407 errors as of yet?
The current clients do only support basic authentication. Better proxy support has been on the "wish list" for a long time and I'm pretty sure there are still a lot of things ahead of it - - but SOMEDAY - - (maybe)
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
-
- Site Moderator
- Posts: 6359
- Joined: Sun Dec 02, 2007 10:38 am
- Location: Bordeaux, France
- Contact:
Re: Any update on the Proxy issue/407 errors as of yet?
Current client support proxies without authentication. It works fine when you only have to use a proxy IP and port. But there is a bug that prevent them from authenticating fine when a login and password are required .
Re: Any update on the Proxy issue/407 errors as of yet?
I know very little about proxies, though it would seem like a quick fix for a lot of the problems to have an option where the client could use IE settings, as version 5 had.