Http target connection throwing 503 Service unavailable

@Anil Sagar @ Google

I am trying to hit an external https service through my proxy.

URL for the Service is directly hardcoded in HTTPTargetConnection in the PostFlow of targetEndpoint.

The connnectivity is available between Router Server and Target Server. Still we are getting 503 error.

Please let us know do we connnectivity between MessageProcessor and Target Server.

Solved Solved
0 2 769
1 ACCEPTED SOLUTION

503 is emitted by an HTTP Endpoint to indicate it is too busy, or it is otherwise unable to service the request. A possible reason is a backing system or dependency is unavailable. Or, maybe the system is offline due to maintenance. https://httpstatuses.com/503

It's not clear which thing is throwing a 503.

you said "Still we are getting 503 error."

Is this from the target? If so, then your target is too busy or otherwise refusing to serve the request.

If this is from the Apigee Edge router, then there is something else going on.

To determine which, you can use the Trace tool inside the Apigee Edge UI. Turn on tracing, run a request. If you see the request in the Trace tool, then the request is reaching the API Proxy, which means it's not the Apigee Edge router that is responding with the 503.

It's likely the backend system in that case.

To solve that, you need to investigate the backend system.

View solution in original post

2 REPLIES 2

503 is emitted by an HTTP Endpoint to indicate it is too busy, or it is otherwise unable to service the request. A possible reason is a backing system or dependency is unavailable. Or, maybe the system is offline due to maintenance. https://httpstatuses.com/503

It's not clear which thing is throwing a 503.

you said "Still we are getting 503 error."

Is this from the target? If so, then your target is too busy or otherwise refusing to serve the request.

If this is from the Apigee Edge router, then there is something else going on.

To determine which, you can use the Trace tool inside the Apigee Edge UI. Turn on tracing, run a request. If you see the request in the Trace tool, then the request is reaching the API Proxy, which means it's not the Apigee Edge router that is responding with the 503.

It's likely the backend system in that case.

To solve that, you need to investigate the backend system.

A 503 Service Unavailable Error is an HTTP response status code indicating that your web server operates properly, but it can't temporarily handle the request at the moment. This error happen for a wide variety of reasons. Normally, this error can be due to a temporary overloading or maintenance being performed on the server and it is resolved after a period of time or once another thread has been released by web-server application. The subsequent points serve as a possible fix, aimed toward resolving the potential root causes.

  • Reload (Refresh) the page
  • Scan for Malware
  • Visiting the website later
  • Contact server admin