Message boards :
Questions and problems :
BOINC has troubles handling proxy on Linux (Ubuntu 12.04)
Message board moderation
Author | Message |
---|---|
Send message Joined: 7 Feb 14 Posts: 3 |
Hi ! I use BOINC 7.2.33 x64 on Ubuntu LTS 12.04. My institution filters outgoing internet connection through a proxy. I tried to configure the proxy settings using BOINC Manager, going to Tools -> Options -> Proxy HTTP. I checked the "Connect using a HTTP proxy server" box, entered server address and port and my institutional login and password. But this doesn't work, BOINC can't reach the internet. If I set no proxy settings in BOINC but instead open a terminal and export the http_proxy environment variable, then start BOINC from the same terminal, everything works fine. Does anyone have an idea why BOINC behaves this way ? I am happy though I could find a workaround and use BOINC anyway. Thanks in advance, Mathieu |
Send message Joined: 29 Aug 05 Posts: 15484 |
Does your institution allow something like BOINC? Best ask them for permission first. Then you'll want to check http://boinc.berkeley.edu/wiki/Client_configuration, more specifically the <force_auth>auth_method</force_auth> option. You can also set up your proxy through here, with the <proxy_info> option. |
Send message Joined: 20 Nov 12 Posts: 801 |
Could you enable <http_debug> and <proxy_debug> log flags. See Client configuration. Also, I hear some proxies work with HTTP 1.0. You can force BOINC to use that with <http_1_0> option. |
Send message Joined: 7 Feb 14 Posts: 3 |
The cc_config.xml file was not present ; settings were stored in client_state.xml. So, if I create cc_config.xml, add proxy settings and enable http and proxy debug, I get the following :
For me, it's got no obvious meaning ... |
Send message Joined: 20 Nov 12 Posts: 801 |
Did you try the <force_auth> option? I'm guessing that it's the gss-negotiate that's failing here so something other than that. You didn't say if you tried with <http_1_0>? |
Send message Joined: 7 Feb 14 Posts: 3 |
Did you try the <force_auth> option? I'm guessing that it's the gss-negotiate that's failing here so something other than that. Wow ! You're good, adding this line to cc_config.xml solved the problem : <force_auth>basic</force_auth> You didn't say if you tried with <http_1_0>? I didn't, because of that line : [http] [ID#1] Received header from server: HTTP/1.1 100 Continue Thanks very much ! |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.