Error 503 when connecting HTTPS Target Server

[#1]

Hi,

I've created a new Target Server

{
  "host": "<HOST>",
  "isEnabled": true,
  "name": "<NAME>",
  "port": 443,
  "sSLInfo": {
    "ciphers": [],
    "clientAuthEnabled": "false",
    "enabled": "true",
    "ignoreValidationErrors": true,
    "protocols": []
  }
}

When i want to connect, i'got a 503 error

{"fault":{"faultstring":"The Service is temporarily unavailable","detail":{"errorcode":"messaging.adaptors.http.flow.NoActiveTargets"}}}

In the documentation, I saw that I had to add ssIInfo.enabled=true to activate the https connection between Apigee and my API but it doesn't work.

Do you have any idea?

Julien

[#2]

One possible scenario is that you need to specify to use a proxy server to access the target. You can do that as part of the HTTPTargetConnection configuration. Here is a snippet:

<HTTPTargetConnection>
<Properties>
<Property name="use.proxy">true</Property>
</Properties>

</HTTPTargetConnection>

[#3]

Is this on Cloud or Private cloud?
Do you know if you have connectivity to that backend from edge and if that service is up?

pls add more details.

[#4]

My API is on Public Cloud, I can access it directly in HTTP and HTTPS. With Apigee, I can only access it in HTTP and I get this error in HTTPS

[#5]

Have you verified that the certificate for your host is valid?

You can run something like:

echo | openssl s_client -showcerts -servername apigee.com -connect apigee.com:443 2>/dev/null | openssl x509 -inform pem -noout -text

Pay attention to the ciphers, dates, etc. If these look good, PM me with the host name and I will verify from another org. It is possible that your org does not support SNI which is required for some configurations.

[gregkuelgen]

David's advice is solid.

Note that I was able to recreate this issue using https://httpbin.org. Httpbin's certificate it is missing the Organization (O) and Organization Unit (OU). It causes the same error you report.

The error you are seeing is likely due to something with the certs causing an SSL handshake issue.

[#7]

Hello,

I think my cert is correct. You can test it at https://flowchart.preprod.lefebvre-sarrut.eu.

Thanks

[#8]

Are you using Loadbalancer (http://docs.apigee.com/api-services/content/load-balancing-across-backend-servers) and health Monitor in the HTTP target endpoint definition to route your calls?

We recently found a bug with that and want to make sure you are not running into the same. @Julien NOEL

[#9]

As anyone been able to solve this issue?

I'm experiencing exactly the same behaviour.