Connect JIRA (on premise) with Power Automate

[Shreya SINGH]

Hello,

I am trying to connect  JIRA (on premise) (REST API) with Power Automate using HTTP connector and also checked on Postman with Basic authentication. However, I am getting Unauthorized error 

In power automate it shows something like this : UnresolvableHostName. The provided host name xxxxxxxxxxxxxxxxx could not be resolved.

In Postman with basic authentication:

{
  "error": {
    "code": 500,
    "message": "The remote name could not be resolved: 'xxxxxxxxxxx.net'",
    "source": "europe-001.azure-apim.net",
    "path": "forward-request",
    "policyId": "",
    "clientRequestId": "886e9188-cd22-4e80-8b6a-6391ede4c62b"
  }
}

[Sunny Ape]

The provided host name xxxxxxxxxxxxxxxxx could not be resolved.

And what is the hostname? IE, what do you type in the URL of a web browser to access the web interface?

Is there some reason why you are obscuring the hostname with 'X's?

What IP address did the hostname resolve to when you did a ping or nslookup?

"message": "The remote name could not be resolved: 'xxxxxxxxxxx.net'"

I highly doubt your company put an on-premise instance of Jira into the .net public name space.

[Shreya SINGH]

Hello , from xxxx is just a dummy name. The message is like this "message": "The remote name could not be resolved: 'rndwww.nce.companyname.net'"

[Sunny Ape]

But the domain name 'rndwww.nce.companyname.net' is just nonsense too. There is no such domain in the .NET namespace.

Anyhow, whatever the name is, just as Nic Brough has said, you have no DNS resolution of that name to any IP address.

[Nic Brough -Adaptavist-]

Yep, your network does not recognise the URL you are asking for.  You need to configure it with the right URL, or fix your network so that it can resolve it.

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

This is what it says it is: "Name can not be resolved" is a network error.  It's nothing to do with your code or the server at the other end, it means your computer cannot find the specified address.

It's your DNS - your computer is trying to look up your xxxxxxxx.net so that it can get the actual IP address to try to talk to, and it is not getting anything back from the DNS server.  As far as your network is concerned xxxxxxxx.net does not exist, so there is nothing to talk to.

You need to get the name added to your DNS, or find out what the actual name is.

(In the short term, you could replace xxxxxxx.net with the raw IP address, but that is not a good solution, as it could change)

[Shreya SINGH]

Hello , from xxxx is just a dummy name. The message is like this "message": "The remote name could not be resolved: 'rndwww.nce.companyname.net'"

[Nic Brough -Adaptavist-]

It doesn't matter what the URL is, the problem is that your network DNS can not resolve it to the IP address that the service is running on.

Please, re-read the answer I gave before, I don't want to repeat it.