Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Confluence API TLS Issues

Brad Hayes June 18, 2018

Using GOLang to make connections to the Jira REST API I am periodically getting an error.  The text of the error is net/http: TLS handlshake timeout.

This occurs fairly repeatedly at the same time of day.  I periodically get other errors such as saturday I got an error

write tcp 128.28.14.69:60036->104.192.142.120:443: wsasend: An established connection was aborted by the software in your host machine.

I've contacted Jira technical support about the issue and ad least as far as the TLS  handshake timeout, they claim my client never connected to their host.  From all the research I've done, the error seems to be indicating a host error.

Any thoughts or help would be appreciated.

 

2 answers

0 votes
Brad Hayes June 22, 2018

Hi Andrew,

Thanks for the response.

I'm actually familiar with that post and implemented that at the beginning of my project.  Without it my calls that are ending with a TLS handshake timeout.  Based on other posts I've already overridden the Timeout to 200 seconds.

brad

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 22, 2018

Hi Brad,

I'm not familiar with using Go myself to make API REST calls, however from searching on this topic I came across this post I thought might help:  Don’t use Go’s default HTTP client (in production)

In it, Nathan explains a scenario in which these kinds of Go rest calls can get stuck in a TLS handshake because by default Go calls can use a default infinite period of time (ie no timeout).   He suggests setting a timeout value yourself in the Go code to wait a set interval before giving up.

I hope this helps.

Andy

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events