Jira field says TestRail "refused to connect"

Question

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"

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.

Bibek_ikuTeam_ · Answer

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

Jeremy Munoz · Answer

Hey @Nina Lord

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

Jim Knepley - ReleaseTEAM · Answer

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.