Skip to main content
Best answer

Attempting to use Zapier to send a JIRA custom request resulting in gaierror(-2)


Attempting to use Zapier to send an issue to a specific sprint is resulting in the following error: 

('Connection aborted.', gaierror(-2))

Any thoughts on what’s going wrong here?

The documentation is here: https://developer.atlassian.com/cloud/jira/software/rest/api-group-sprint/#api-rest-agile-1-0-sprint-sprintid-issue-post

 

Best answer by Tom M

Turns out using a base64 encoded username:token as JIRA authentication that the authorization isn’t Authorization: Bearer, but Authorization: Basic.

 

All sorted! Hope this helps someone else out there for better JIRA automation. 

 

Thanks.

View original
Did this topic help you find an answer to your question?

2 replies

Danvers
Forum|alt.badge.img+12
  • Zapier Staff
  • 3731 replies
  • July 5, 2022

Hi @Tom M!

It’s a little tricky to see what might be happening based on that error message. Have you been able to get to the bottom of this one? If not, the Zapier Support team can provide you with the full error response, which might give you a better idea of what isn’t working the way that it should. To be super clear, the Support Team can’t help you troubleshoot the set-up of the hook, but they can share the error logs with you, which might give you an idea of what you need to change. You can contact them using the Get Help form (https://zapier.com/app/get-help)

 

Thanks!


  • Author
  • 4 replies
  • Answer
  • July 6, 2022

Turns out using a base64 encoded username:token as JIRA authentication that the authorization isn’t Authorization: Bearer, but Authorization: Basic.

 

All sorted! Hope this helps someone else out there for better JIRA automation. 

 

Thanks.


Reply