Is there APIGEE Edge having issue while referencing Private IPs?

[#1]

We are facing issues while connecting backend urls (deployed on machine which having Private IP) from APIGEE Edge portal.

While connecting backend urls (deployed on machine which having PUBLIC IP) from APIGEE Edge portal, getting response.

Getting "502 Bad Gateway" issue

We are able to call backend url from APIGEE server by using "curls" command.

Question:

Is there APIGEE Edge having issue while referencing Private IPs?

This is very urgent. We are facing this issue from last 2 weeks.

We got below link where APIGEE has mentioned - "By default, the Edge UI is prevented from referencing private IP addresses." - Please confirm.

"http://docs.apigee.com/private-cloud/latest/allowing-trace-tool-access-local-ip-addresses

[gaurav_bhandari]

Hi @Vinod,

Are you trying to access the backend with one way TLS or two way TLS.

What exact curl command are you trying to hit the backend?

Is the backend outside the network or within the network?