| Mylyn Github task repository responds with connection refused [message #818526] |
Sun, 11 March 2012 15:48  |
Rob Winch Messages: 1 Registered: March 2012 |
Junior Member |
|
|
The company I work for has purchased github enterprise and has the latest version deployed over http. When I try to configure a new task repository Mylyn Github repository type, I get an error stating "Error validating settings: Connection refused".
If I copy the Server url into a browser I am able to connect just fine. I am also able to connect to github.com with the connector.
When I looked at the FAQ it states that all requests are made over HTTPS [1]. So my question is, does the API strictly use HTTPS even if the URL that is configured is HTTP? If so, can this be relaxed in order to support deployments that are using only HTTP? If not, any suggestions for how to proceed?
[1] wiki.eclipse.org/EGit/GitHub/UserGuide#Frequently_Asked_Questions_.28FAQ.29
|
|
|
|
|
| Re: Mylyn Github task repository responds with connection refused [message #998270 is a reply to message #841871] |
Wed, 09 January 2013 12:36  |
Jeremy Welch Messages: 1 Registered: January 2013 |
Junior Member |
|
|
I'm having this issue as well. My company's GitHub Enterprise implementation doesn't support HTTPS connections (don't ask me why, I have no idea), only HTTP and GIT/SSH.
I'd love to integrate Mylyn Tasks and the Issues from my project's repo, but I get a "Error validating settings: Connection refused: connect" error when I try to validate settings.
Server: http:// github. local.domain/me/project.git # Spaces added to fool BB editor
Label: me/project issues
User ID: me
Password: mypasswd
Disconnected: No
Anonymous: No
Save Password: Yes
I've tried multiple permutations of the available settings - no userid/pw; anonymous; disconnected; anonymous+disconnected; etc...
To answer the question asked above, I'm using EGit 2.1.0 currently. I see that 2.2.0 is out there, just on a different repo, so I'll update and give it a go.
I'm guessing that this all comes back to the core issue of the plugin ignoring the protocol specified in this window and using HTTPS instead for everything. That seems like a poor decision, when it comes to supporting GitHub Enterprise deployments, but I understand that that's a small subset of users.
Anyone found a way around this yet?
|
|
|
Powered by
FUDForum. Page generated in 0.01781 seconds