After proxy bundle deployed to Test environment, unable to reach the base URL of the deployed proxy

[#1]

The requested URL is not available.

Requested URL:

http://<Base URL>v1/

Recommendations

Ensure the URL is entered correctly.

Refresh your browser window.

Try again later.

[#2 · Accepted solution]

@anbarasan.vincent

You might want to try a few things:

1. Undeploy other API Proxies and try your request. This will make sure that some other proxy listening to some wildcard base URL is not accepting your request.
2. Undeploy your proxy and see if you are getting CLASSIFICATION_FAILED
3. Deploy it again, and see if you are getting the 503 or 200
4. Deploy it to 'prod' environment and see if you see the same issue

Is it possible that the request is going to your backend proxy and that is returning the 503?

Did you start the trace session and if yes, do you see that 503 is actually seen in the trace

Also, v1 does not automatically get added to your http://<Base URL>. So technically, you should be hitting http://<Base URL>/<resource path> to hit your API Proxy.

If it still does not work with these suggestions, can you attach a screenshot of your API Proxy overview tab and the POSTMAN request/response?

[#3]

Not a lot to go on. Could you attach the bundle?

Are you sure that the bundle is really deployed to test? If you open the Deployment combobox on the Overview or Develop tab, do you see a green circle next to test? If not, then the bundle is not actually deployed.

[mdunker]

Other recommendations:

1) Verify with trace that the call is never reaching the proxy.

2) Make sure that you are accessing the correct virtual hosts -- a common problem is trying to use http traffic if only the secure virtual host is being used, or vice versa.

3) Make sure the base path is correct in both your URL and the proxy.

4) Make sure the proxy is deployed successfully to all routers and message processors. You can use this API:

GET https://api.enterprise.apigee.com/v1/o/{org}/e/test/apis/{apiname}/deployments

5) Run the call using curl or POSTMAN. If you test using the browser, sometimes you won't see what the real response to your GET request is.

[#5]

Thanks for your replies.

However, the deployment is successful and I checked all the RMP for the deployment and they are successful.

But even with POSTMAN, I am not able to hit the proxy bundle.

Also, virtual hosts are configured correctly.

Any other possibilities to check?

[sarthak]

Can you please provide a bit more details of what exactly you are seeing ? When calling the url what exact error are you seeing ? When you open the trace are you able to make the call with the "Send Request" section in the Trace ?

[#7]

Sarthak, When I see the results from https://api.enterprise.apigee.com/v1/o/<org>/environments/test/deployments, I see that the proxy successfully deployed. and when I send request for the API in the trace, I get the following error: Internal Error, HTTP 503

In simple HTML response, I am getting "The requested URL is not available."

Thanks

Anbu

[#8]

Hi Anbu,

You were talking about RMP and VH configurations and in this comment you are referring to Management API on Apigee Cloud. Are you using the cloud version or OPDK/private cloud version?

[#9 · Accepted solution]

@anbarasan.vincent

You might want to try a few things:

1. Undeploy other API Proxies and try your request. This will make sure that some other proxy listening to some wildcard base URL is not accepting your request.
2. Undeploy your proxy and see if you are getting CLASSIFICATION_FAILED
3. Deploy it again, and see if you are getting the 503 or 200
4. Deploy it to 'prod' environment and see if you see the same issue

Is it possible that the request is going to your backend proxy and that is returning the 503?

Did you start the trace session and if yes, do you see that 503 is actually seen in the trace

Also, v1 does not automatically get added to your http://<Base URL>. So technically, you should be hitting http://<Base URL>/<resource path> to hit your API Proxy.

If it still does not work with these suggestions, can you attach a screenshot of your API Proxy overview tab and the POSTMAN request/response?

[#10 · Accepted solution]

Problem solved. Thanks to Sandeep for troubleshooting it in a live meeting.

It was due the fact that there were multiple aliases in virtual hosts configured but most of them were not being used.

Traffic on both port 80 and port 443 were blocked.

So after changing the default proxy URL to the alias configured at port 1800 and using 1 way SSL, the API requests went through the proxy bundle.

Thanks

Anbu