POST request with node fetch at action level to Elastic Search API running on port 36029 responses error 503 timeout | Community
Skip to main content
Level 2
April 1, 2022
Question

POST request with node fetch at action level to Elastic Search API running on port 36029 responses error 503 timeout

  • April 1, 2022
  • 1 reply
  • 1929 views

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?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

Adobe Employee
April 1, 2022

To my knowledge there are no restrictions on port numbers used.

  1. What is the response time in Postman?
  2. What library are you using for fetch?
  3. Is there any IP whitelisting on Elastic Search API? Postman might use your VPN but runtime does not.

Regards,

Level 2
April 1, 2022

1- thanks for reply, as i already mentioned while from runtime the response is 503 timeout, in postman works ok which means the response is 200 ok  .

2- fetch js 

3-By the moments theres no whitelisting on ES API is open and theres no VPN.

 

 

Adobe Employee
April 1, 2022

Hi Jose,

 

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.

 

Are you using either fetch or node-fetch?

 

Do you mean by open that it does not have authentication?

 

Regards,