tunneling socket could not be established

Ajit Vijay Repal 1 Reputation point
2021-01-18T12:15:34.827+00:00

I have deployed node.js service on AKS which calls external api (cisco webex bot). But it throws error as

{"code":"ECONNRESET"}
2021-01-18T11:51:22.421Z [ [31merror [39m] [FAKEID] <../features/webhooks/incomingMessage.handler.js:31>tunneling socket could not be established, cause=getaddrinfo ENOTFOUND abc.proxy.abcd.com abc.proxy.abcd.com:8080

What would be the possible issue?

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
8,933 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. ajkuma 28,036 Reputation points Microsoft Employee Moderator
    2021-01-19T09:34:26.553+00:00

    anonymous user, To better assist you on this issue, Just to confirm, is your app hosted on AKS or Azure App Service WebApp?

    This could be due to SNAT Port exhaustion happening on your Node.js while connecting.
    https://learn.microsoft.com/azure/load-balancer/load-balancer-outbound-connections#snat

    On Azure App service - The SNAT port limit (128) affects opening connections to the same address and port combination.

    Kindly see if implementing connection pool or scale-up App Service Plan tier (In case it is App Service) works.

    Please check the 'Avoiding the problem' section in the document and let us know how it goes.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.