Actually it happens with any method type (post/put/get/delete) request with node fetch at action level to Elastic Search API running on port 36029 responses error 503 timeout, i have events that triggers actions in this case if send a the same request from postman it works fine but the request done at action level when is triggered it responses error 503 timeout which makes me suspect there is some kind of restriction on request sent from adobe io runtime on api endpoints running on non standard ports such like 36029, my question is: can this be possible? and if so how can i change this?
Topics
Topics help categorize Community content and increase your ability to discover relevant content.
I understand that the response is 200, what are the response times? How long does it take for the API to respond in Postman. A 503 response usually means that the service is unavailable. That's why I was thinking of IP block.
I take it that you request the Bearer token with the same domain but different path/endpoint?
How are you passing the parameters for the search API? Double check that headers and body are passed in the same way. I suggest also trying library make-fetch-happen in my experience this library has more options.
Hello i've finally found that the problem is due to ports not opened for my Elastic Search instance connection so i finally found the problem and the way i'm going to solve it is to change to port used for Elastic Search connection to another port that are already open in App Builder:
