Skip to main content
Community site session details

Community site session details

Session Id : oieInxU0qAi7k/bBbEC/3B
Power Automate - Using Connectors
Unanswered

Getting 'The remote name could not be resolved' error with Custom Connector

Like (0) ShareShare
ReportReport
Posted on 4 Aug 2021 16:25:37 by

Hi,

 

I'm trying to access a WSO2 API with Basic Authentication using Custom Connector.

While testing the connector i'm receiving the below error.

 

{
"error": {
"code": 500,
"message": "The remote name could not be resolved: '************'",
"source": "***************",
"path": "forward-request",
"clientRequestId": "******************"
}
}

 

The same WS02 endpoint is accessible though post man and git bash using curl.

 

Note - I have created the Custom connector using Postman collection.

 

Thanks in Advance.

 

  • rakadakaka Profile Picture
    77 on 05 Aug 2021 at 19:07:19
    Re: Getting 'The remote name could not be resolved' error with Custom Connector

    @Anonymous  : It looks like access issue , can you please confirm if the WSO2 URL is accessible publicly as well ?

     

    If not , my guess there might be some IP whitelisting or network restriction placed where WSO2 API is hosted

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

Paul Stork – Community Spotlight

We are honored to recognize Paul Stork as our July 2025 Community…

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 497 Super User 2025 Season 2

#2
David_MA Profile Picture

David_MA 436 Super User 2025 Season 2

#3
Riyaz_riz11 Profile Picture

Riyaz_riz11 244 Super User 2025 Season 2

Featured topics

Loading complete