Getting below error while accessing the base path of proxy:
We have started using Apigee in our API management. I have created some proxies with target URLs as company APIs and some proxies with target URLs sample from internet (out side company).
My Proxy base path is working fine which are built on outside target APIs (URLs), whereas the proxy with target API (URL) as company API (URL) is giving error. like below. Why my proxy is giving error with target URLs are company URLs...?
{"fault":{"faultstring":"The Service is temporarily unavailable","detail":{"errorcode":"messaging.adaptors.http.flow.ServiceUnavailable"}}}
I am using on-prem, I have installed edgemicro gateway on prem and its working fine. However the proxy (if it is has target end point url as Internal URL) then the proxy giving this error.
It sounds like your MP is unable to resolve the internal hostnames. Are you using hostnames or IP addresses? There aren't a lot of details to go on here.
Thank you Jeremy. It looks like proxy clearance is not there for my Target URL (which is in different stand alone server) from Microgateway server (which is on private cloud)... I will update you once I have tested this scenario....
Answer by Siddharth Barahalikar
·
Jul 27, 2019 at 04:51 PM
Hi @prabhanjan reddeppagari, which Apigee instance are you using Cloud or On-prem?
If it is cloud and if you trying to call services hosted on the local machine like localhost:8080/abc then you will get 503 ServiceUnavailable.
Apart from this, the issue can also be an SSL handshake failure, as you are calling company private APIs.
Have a look at this troubleshooting doc for 503 error,
https://docs.apigee.com/api-platform/troubleshoot/runtime/503-service-unavailable