Error on REST API request - ConnectionResetError(10054, 'An existing connection was forcibly closed

[alexey sorochkin]

My REST API request from Python to JIRA is failing is following error message:

Connection aborted.', ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None

time.sleep() is not solving the issue.

Any help would be appreciated.

[Thomas Deiler]

Dear @alexey sorochkin ,

this sounds crazy. Due to the nature of a REST call, which is stateless, a connection is never kept open longer.

Can you give me more details when this happens? Does this happen only for specific calls? POST, GET, PUT same?

So long

Thomas

[alexey sorochkin]

It happens one GET call

[Thomas Deiler]

Ok. Which call exactly?

have you tried to send the REST call with a browser extension to verify if it works in general?

So long

Thomas

[Thomas Deiler]

Ok this means the REST API interface in Jira is not broken. :)

Is 

request.request()

from a library?

[alexey sorochkin]

Yes from HTTP request library

[Thomas Deiler]

Do other GET request (eg. get all projects) work with this HTTP request library function?

Try GET /rest/api/2/project

So long

Thomas

[alexey sorochkin]

No, nothing is working. Event simple attemp to GET jira url information immediately resulting in this error.

[Thomas Deiler]

And what about a PUT/POST requests?

e.g. PUT /rest/api/2/issue/{issueIdOrKey}/assignee ?

Has your code ever worked?

[alexey sorochkin]

PUT and POST giving same error.

It worked up until few days ago and suddenly it started showing this error.

[Thomas Deiler]

Can you remember what has changed? A new SSL certificate pops up immedately into my mind, as a source of problems. Network changes? Host name changes?

[alexey sorochkin]

We dont know yet, but thanks for ideas.

What network change can cause this kind of problem?

[Thomas Deiler]

Dear @alexey sorochkin ,

I have no clue about what could be the reason. But thinking logically, if your didn't change the Python script and Jira was also not manipulated, something in between must have been changed - the network (firewall, router, vpn, ...).

Probably there was a package / software upgrade on both client and server. Eg. a new Python lib / binary could react different than before.

So long

Thomas

[alexey sorochkin]

So, yes we did couple of tests:

Its working from browser and postman

url = https://***jiraserver***/rest/api/2/issue/abc-123/?fields=issuelinks

response = requests.request("GET", url, auth=auth, headers=headers, data = payload, verify = False)