Hosted Target 404 - No Runtime Error Logs
Hey Guys
org: hachetteuk
env: test
proxy: ProductAPI
I have followed the tutorial here for my own Node.js app we have been building in house, and unfortunately I always get 404 errors when trying to access my methods.
I get the following error when I try to hit my GET method:
{
"fault":{
"faultstring":"Unable to identify proxy for host: secure and url: /v1/product",
"detail":{
"errorcode":"messaging.adaptors.http.flow.ApplicationNotFound"
}
}
}
Here is my apigeetool command I used (excluding credentials) to deploy:
apigeetool deployhostedtarget -n ProductAPI -d . -o hachetteuk -e test -b /v1/product
Also here is my output from running that command (with -V) attached to this question:
Going to create revision 4 of API ProductAPI
Creating revision 4 of API ProductAPI Uploading resource app.js Uploading resource app.js.map Uploading resource app.yaml Uploading resource common/config.js Uploading resource common/config.js.map Uploading resource controller/ProductController.js Uploading resource controller/ProductController.js.map Uploading resource models/Mapper.js Uploading resource models/Mapper.js.map Uploading resource models/Product.js Uploading resource models/Product.js.map Uploading resource package.json Uploading resource repositories/base/CosmosBaseReadOnlyRepository.js Uploading resource repositories/base/CosmosBaseReadOnlyRepository.js.map Uploading resource repositories/common/CosmosDBUtilities.js Uploading resource repositories/common/CosmosDBUtilities.js.map Uploading resource repositories/CosmosProductRepository.js Uploading resource repositories/CosmosProductRepository.js.map Uploading resource repositories/entities/ProductEntity.js Uploading resource repositories/entities/ProductEntity.js.map Uploading resource repositories/errors/CosmosDatabaseError.js Uploading resource repositories/errors/CosmosDatabaseError.js.map Uploading resource repositories/errors/CosmosDatabaseQueryError.js Uploading resource repositories/errors/CosmosDatabaseQueryError.js.map Uploading resource repositories/errors/RepositoryError.js Uploading resource repositories/errors/RepositoryError.js.map Uploading resource repositories/factories/CosmosDBClientFactory.js Uploading resource repositories/factories/CosmosDBClientFactory.js.map Uploading resource repositories/interfaces/IQueryRepository.js Uploading resource repositories/interfaces/IQueryRepository.js.map Uploading resource server.js Uploading resource server.js.map Creating the target endpoint Creating the proxy endpoint Deploying revision 4 of ProductAPI to test Deployment on test successful "ProductAPI" Revision 4 deployed environment = test base path = / URI = http://hachetteuk-test.apigee.net/v1/product URI = https://hachetteuk-test.apigee.net/v1/product
As you can see from the above the node code has been deployed, but I'm getting runtime errors.
NB: There are no runtime or build logs for this proxy.
Your error message does not mention anything about being partially deployed so the undeploy/redeploy likely won't help. The error I see is "Unable to identify proxy for host" so are you sure there is a "secure" virtual host?
Wait...it appears to be deployed now. Did something change, or is this a runtime error as traffic flows through the proxy?
Thanks for looking at this. It deployed fine with regards to appearing in the Edge UI, but when I hit the the URLs, I get:
{
"fault":{
"faultstring":"Unable to identify proxy for host: secure and url: /v1/product",
"detail":{
"errorcode":"messaging.adaptors.http.flow.ApplicationNotFound"
}
}
}
Answer by Siddharth Barahalikar
·
May 24, 2018 at 01:44 PM
Hi @garethbradley, Even I faced the same issue when I deployed my first Node App using Hosted Targets. It has few issues as it is still in Beta.
Normally this error usually means the message processors are not able to classify the request - classification error. This can happen if the proxy is not deployed to the environment that you are hitting.
As a workaround, after apigeetool deployed the proxy, I had to manual un-deploy & deploy the proxy couple of times to make it work. Please give it a try.
Thanks for the reply.
As a workaround, after apigeetool deployed the proxy, I had to manual un-deploy & deploy the proxy couple of times to make it work
How did you undeploy and deploy? Is that apigeetool command as well?
Tried undeploying and using deployproxy, but to no avail.
