Hi. I'm testing Logic Apps and I'm getting this error:
UnresolvableHostName. Http request failed with status code 'NameResolutionFailure' and status message: 'The remote name could not be resolved: ...
The scenario is as follows:
When a blob is added to a certain container, it triggers an http. The https address is from a web app deployed in a container
Please tell me some to solve your problem.
Where is your container web app hosted?
Is the URL of the web application resolved?
It seems to use HTTPS communication. How is the SSL certificate configured?
Have you confirmed the following?
https://docs.microsoft.com/en-us/answers/questions/638013/logicapp-consumption-http-api-call-self-signed-cer.html
It is a private container.
The URL is resolved.
Using Private key certificates (pfx)
I understand that you want to act on the HTTPS endpoint (self-signed) of a private container with the trigger that Blog was added to Logc Apps, but it is failing.
The following pages mention scenarios where you can use self-signing when making outbound calls in Logic Apps.
https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-securing-a-logic-app?tabs=azure-portal#access-for-outbound-calls-to-other- services-and-systems
For Consumption logic apps in the multi-tenant Azure Logic Apps environment, HTTP operations don't permit self-signed TLS / SSL certificates.
For Standard logic apps in the single-tenant Azure Logic Apps environment, HTTP operations support self-signed TLS / SSL certificates. However, you have to complete a few extra steps for this authentication type.
If you are Standard logic apps (single-tenant), please refer to the following and double check if the settings are correct.
18 people are following this question.
