Community
Participate
Working Groups
Build Identifier: Galileo SR1 In the repository properties dialog, I get an error message in the dialog header when I try to validate the connection to https://bugs.eclipse.org/bugs: "I/O Error occurred while communicating with https://bugs.eclipse.org/bugs." The behaviour is the same for anonymous and authenticated connections. Also I tried different proxy settings (manual and native - direct will not work as I'm behind a proxy). Also the same error occurs when I try to connect against https://tasktop.com/bugs I would like to give you more information on the error, but I cannot find any entry in the error log. Some other random information that may help: - I can connect to the URLs above with a browser from my machine. - I updated from Galileo to Galileo SR1 (org.eclipse.mylyn.bugzilla_feature_3.2.2.v20090912-0400-e3x), but the error (and missing diagnostics) is the same. - When I try to refresh existing queries on Eclipse bugzilla, I get an error dialog with title "Query Sychronization Failed" and message "Check repository configuration: Network is down: create". Again, no error log entry. Reproducible: Always Steps to Reproduce: 1. Add task repository with URL https://bugs.eclipse.org/bugs 2. Hit "Validate Settings"
What type of proxy are you using? If it's an NTLM proxy you need to specify the username in the format DOMAIN\user. Note that there are some limitations: http://wiki.eclipse.org/index.php/Mylyn_FAQ#NTLM_authentication .
I would need to ask IT what kind of proxy it is, but it doesn't require authentification afaik (at least I do not need to provide credentials for the proxy anywhere else in Eclipse, in browsers, etc.). Do you absolutely need to know this? Just some more pieces of random information: - I updated Mylyn to 3.3.1 (org.eclipse.mylyn.bugzilla_feature_3.3.1.v20091215-0000-e3x), but the issue is the same. Still no details in the error log... - The message when refreshing existing queries changed to "Check repository configuration: bugs.eclipse.org"
That sounds like an NTLM proxy. Can you try entering your windows credentials in the HTTP proxy section using the configuration format described in comment #1?
Bingo! This did the trick. Thank you very much for your help! This issue is resolved, but nevertheless it might be a good idea to print stack traces into the error log in case the connection validation fails... Just my two cents.
Yes, I agree. The error handling need to be improved (see bug 207097) *** This bug has been marked as a duplicate of bug 207097 ***
Created attachment 242627 [details] ease in eclipse style ease in eclipse style
