Skip to main content

Notifications

Power Automate - Connector Development
Answered

Power Automate Custom Connector / Gateway Connection Issue

(0) ShareShare
ReportReport
Posted on by 9

I've configured an On-Premises Data Gateway and a Custom Connector to use only HTTP API endpoints, but I receive this error message when testing:

 

 

 

{
"message": "Received error payload from gateway service with ID 3091244: Substituted: HttpRequestException:<pi>System.Net.Http.HttpRequestException: An error occurred while sending the
request. ---> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. --->
System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure
...
},
"source": "gatewayconnector-eus.azconn-eus-002.p.azurewebsites.net"
}

 

 

 

I have validated the On-Premises Data Gateway is online and ready for use.

PA5.png

I'm certain that my API is configured for HTTP traffic only and that the Connector is making HTTP calls.

PA4.png

Requests to the API work as expected.

PA3.png

What am I missing / where else should I be looking? I'm at a total loss.

  • Verified answer
    davidfilkins Profile Picture
    davidfilkins 9 on at
    Re: Power Automate Custom Connector / Gateway Connection Issue

    Ok, perhaps this will prevent some other unfortunate developer loads of wasted time... turns out that the whole issue was due to a rogue HTTP > HTTPS redirect being initiated from my API.

     

    It was difficult to track down because the redirect did not occur when the request was issued from Postman. But after reviewing the Gateway's QueryExecutionReport log, I was able to confirm that traffic was making its way to my On-Premises Gateway and being relayed correctly to my API. Testing from a browser on the same server my Gateway resides on led me to the redirect... and since my test API doesn't have a valid certificate, voila. Crash & burn.

     

    The quick / easy fix was to configure the API to not perform HTTP > HTTPS redirects.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Microsoft Kickstarter Events…

Register for Microsoft Kickstarter Events…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Announcing Forum Attachment Improvements!

We're excited to announce that attachments for replies in forums and improved…

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 145,422

#2
RandyHayes Profile Picture

RandyHayes 76,287

#3
Pstork1 Profile Picture

Pstork1 64,711

Leaderboard

Featured topics