Skip to content
This repository has been archived by the owner on Jul 23, 2020. It is now read-only.

Error: connect ECONNREFUSED #3

Closed
alexcotoranu opened this issue May 27, 2015 · 4 comments
Closed

Error: connect ECONNREFUSED #3

alexcotoranu opened this issue May 27, 2015 · 4 comments

Comments

@alexcotoranu
Copy link

Hi, I'm getting the following error on every API call:

image

(This is when running console.log(err); )
I'm connecting to Jira v6.4.1 using basic authentication.

When already logged in the browser, I can get to the API to give me data in the browser with both the IP and the host name of the Jira server.

When logged out I get {"errorMessages":["No project could be found with key 'PROJ'."],"errors":{}} where 'PROJ' would be the project key. This part makes sense as I am not logged in. However, this is not returned to my application when I make the API calls using jira-connector (at least not visibly to me).

Also, I can connect just fine with curl using the first command outlined here: https://developer.atlassian.com/jiradev/api-reference/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-example-basic-authentication

Any help with this issue would be greatly appreciated.

@apla
Copy link
Contributor

apla commented Aug 1, 2015

Have same issue.

protocol: "http" fixed issue for me

@floralvikings
Copy link
Owner

I haven't been able to reproduce this, but since changing the protocol to HTTP seems to help, I think I might know the problem; Are the servers you're connecting to using unsigned SSL certificates? I'm not sure how request handles those, so that might be the issue.

@apla
Copy link
Contributor

apla commented Aug 1, 2015

I just installed jira and at this time I'm waiting right certificate from admins. So, jira is listening on 80 only. When I supply only host and basicAuth, I see ECONNREFUSED

@floralvikings
Copy link
Owner

I'm going to go ahead and close this; the only way I've been able to reproduce it is to disable SSL and then try to connect over https, which obviously isn't going to work. If this issue persists I'll continue to investigate

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants