Unable to identify proxy for host

Google Cloud Apigee
1

Hello,

I developed a new proxy in our organization. But, when I get to test it, I keep getting the error 'Unable to identify proxy for host <hostname.domain>.com: and url: /v1/candidateexport&apikey=blah", “detail”: { “errorcode”: “messaging.adaptors.http.configuration.ApplicationNotFound” } } }

Other proxies that were developed last week seem to work fine.

I have performed the following checks already:

  • Searched the community for this question and have already double checked the items that were suggested in those posts
  • Undeployed and deployed the proxy a few times
  • Got rid of the apikey validation

Still, I am unable to resolve this issue. Any help would be appreciated!!

2

Is the ≈ in the url when you make the request? or is that a copy/paste artifact? It looks like it should be a ‘?’ instead…

3

That is indeed a ‘?’. Copy/paste rendered it differently.

4

Try using the management API to verify the deployment details for that proxy/environment/revision. E.g.

curl -X GET -u {user} [https://api.enterprise.apigee.com/v1/organizations/{org_name}/environments/{env_name}/apis/{api_name}/revisions/{revision_number}/deployments](https://api.enterprise.apigee.com/v1/organizations/{org_name}/environments/{env_name}/apis/{api_name}/revisions/{revision_number}/deployments)

Here’s some example output:

{
  "aPIProxy": "**PROXY**",
  "configuration": {
    "basePath": "/",
    "steps": []
  },
  "environment": "test",
  "name": "17",
  "organization": "**ORG**",
  "revision": "17",
  "server": [
    {
      "status": "deployed",
      "type": [
        "message-processor"
      ],
      "uUID": "**UUID**"
    },
    {
      "status": "deployed",
      "type": [
        "message-processor"
      ],
      "uUID": "**UUID**"
    },
    {
      "status": "deployed",
      "type": [
        "router"
      ],
      "uUID": "**UUID**"
    },
    {
      "status": "deployed",
      "type": [
        "router"
      ],
      "uUID": "**UUID**"
    }
  ],
  "state": "deployed"
}

Check to confirm that the state/status is deployed everywhere. If it isn’t, you may need to force undeploy before you can successfully redeploy: http://docs.apigee.com/management/apis/post/organizations/%7Borg_name%7D/apis/%7Bapi_name%7D/revisions/%7Brevision_number%7D/deployments

5

This is great info. I will try this out.

6

Is there a “next step” once this is verified? I found the curl command useful but all output indicated that the state/status is fully deployed.

Thanks!

7

Same issue came up for my team. As for an explanation on why this would happen, i’m unsure. I “undeployed” and redeployed the proxy and that resolved for me.