As the subject mentions. We are getting intermittent 404 errors when requesting one of our APIs. An example of the request being made is this one:
https://intcomex-prod.apigee.net/v1/placeorder?apiKey=1905266f-2ed3-4061-a81d-f3939b6a610b&utcTimeSt...
The response for this request is sometimes the expected one (it should be a 401 response), but other times it responds with a 404 error and the following content:
{ "fault": { "faultstring": "Unable to identify proxy for host: secure and url: /v1/placeorder", "detail": { "errorcode": "messaging.adaptors.http.flow.ApplicationNotFound" } } }
Please help us in fixing this error because it is causing issues with some of our customers. Thank you!
Solved! Go to Solution.
Hi,
Unfortunately, the troubleshooting guide did not help. It doesn't mention anything about the problem happening at random without changing a single character from either the request or the body. This is what was happening to us. You made a request one time, it worked. You made the same exact request a second time, 404 error.
However, I opened a ticket on the support portal and they told me that they reset the message processors and that doing that seemed to stop the errors.
I then checked again and indeed, the random 404 errors were no longer happening, so it seems to be fixed now.
Thank you!
Hi @Gabriel Salama, please have a look at below troubleshooting guide,
https://docs.apigee.com/api-platform/troubleshoot/runtime/404-unable-identify-proxy-host
If problem persists, get in touch with Apigee support.
Hi,
Unfortunately, the troubleshooting guide did not help. It doesn't mention anything about the problem happening at random without changing a single character from either the request or the body. This is what was happening to us. You made a request one time, it worked. You made the same exact request a second time, 404 error.
However, I opened a ticket on the support portal and they told me that they reset the message processors and that doing that seemed to stop the errors.
I then checked again and indeed, the random 404 errors were no longer happening, so it seems to be fixed now.
Thank you!