Error in deployment for environment test. The revision is deployed, but traffic cannot flow. Call timed out; either server is down or server is not reachable
If the message says traffic can flow, but flow may be impaired, it means the proxy might have been deployed to some, but not to all available Message Processors or Routers (a partial deployment).
The proxy deployment failed because of a time out. There are two typical causes for this error:
Network connectivity issue: Communication failed between the Management Server and Message Processor. The underlying cause can be related to network connectivity issues or firewall rules.
Large API proxy bundle: A Message Processor may take a long time to activate if the API proxy bundle is large in size, leading to remote procedure call (RPC) timeouts.
See What you can do below for more information.
In the Edge UI, you will see an error message when you try to deploy a proxy:
You will also see messages in the deployment status areas in the Overview tab of the Edge UI:
Edge Private Cloud
If you are on Edge Private Cloud, you may be able to diagnose and resolve this problem yourself. For troubleshooting instructions, go to the Edge Public Cloud Troubleshooting Guide and locate the section that describes this error. If the problem persists, contact Apigee Support. See also What to include when you contact Tech Support or the Community.
Edge Public Cloud
If you are on Edge Public Cloud, you may need expert help from Apigee to resolve this error. However, you can try the steps outlined in the Troubleshooting section below before contacting Apigee Support or posting the issue to the Apigee Community. See also What to include when you contact Tech Support or the Community.
For Cloud customers, check the Apigee status page for outages
Deployment errors can occur when there is an outage in Edge for the Cloud. Use the following URL to check the current Edge status to see if there is an outage: https://status.apigee.com
Force undeploy and redeploy
In some cases, undeploying and redeploying the proxy revision will correct the problem. Apigee recommends that you do a forced undeploy using the Deployments API with the parameter force=true. If the forced undeploy works, try redeploying the proxy.
Create a new proxy revision
If undeploy/redeploy does not work, try deploying the proxy as a new revision. Sometimes if you delete certain policies from a proxy and then redeploy as the same revision, you can get a deployment error. See About revisions.
Check the deployment status of your proxy
Use the Deployments API to check the deployment status of your proxy to the Message Processors and routers in your environment. This step can indicate the source of the problem. For example, it will show you which Message Processors have errors.
If necessary, you can always include the response information when you contact Apigee Support or post your issue on the Apigee Community. See also What to include when you contact Tech Support or the Community.
Create and deploy a simple pass-through proxy
Create a "hello world" proxy and deploy it. If it deploys successfully, then there might be a problem with the size of the API proxy bundle that's not deploying properly. See the next section Move resource files to the Environment or Organization level.
Move resource files to the Environment or Organization level
If you're on Public Cloud, you can try this solution if you suspect you have an unusually large proxy bundle. If you're on Private Cloud, additional troubleshooting steps are described in Edge Public Cloud Troubleshooting Guide.
For example, if you're deploying a proxy with a Java Callout and the Java code includes a large number of JAR files, it's possible your proxy is exceeding a size limit (by default 15 Mb).
Deploy the API proxy and see if the error goes away.