Jira field says TestRail "refused to connect"

Nina Lord
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 29, 2024

Integration between Jira and TestRail have worked fine in both directions for many months, but now when I view the "TestRail: Runs" field in Jira, it says "<companysubdomain>.testrail.com refused to connect"

refused to connect.png

So I created a new API key through Atlassian and used it in TestRail to reconfigure integration, but the issue remains.

Integration is working from TestRail to Jira, just not from Jira to TestRail.

3 answers

2 votes
Jim Knepley - ReleaseTEAM
Atlassian Partner
October 29, 2024

Hi @Nina Lord 

"Refused to connect" means the remote host actively refused to connect, but it can be misleading. If DNS is resolving to an incorrect IP address (like 127.0.0.1) when the browser tries to resolve <companysubdomain>.testrail.com it could try to connect to an IP that doesn't know how to answer.

If TestRail is embedded in Jira as an iframe (it looks like it is), your host is responsible for resolving that hostname. Maybe try to do something simple like a ping from a command line and see if that gives you any useful information.

0 votes
Bibek Behera
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 11, 2025

I am having the same issue, was anyone able to workaround it?

 

0 votes
Jeremy Munoz
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 7, 2024

Hey @Nina Lord 

 

Were you able to resolve this issue? I am having this exact same problem.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events