Custom deployments not firing to endpoint properly
Anonymous
TRIALOP

2 years ago

<@219150672166125568>

14 Replies

Anonymous
TRIALOP

2 years ago

if possible if we could get a more direct line of communication taht is not public


Anonymous
TRIALOP

2 years ago

that would be great


2 years ago

i'm not the best resource for that, if you are on the team plan i believe you can just email their direct support line cc @Brody


Anonymous
TRIALOP

2 years ago

we should be


2 years ago

team doesnt do email support anymore, but unless there is sensitive matters at hand we ask that threads not be made private


Anonymous
TRIALOP

2 years ago

has to do with our internal stack which is proprietary


2 years ago

right but im not going to ask you about anything proprietary


Anonymous
TRIALOP

2 years ago

give me one minute sorry


2 years ago

you are using the project webhooks right?


Anonymous
TRIALOP

2 years ago

looping in another engineer


Anonymous
TRIALOP

2 years ago

basically on some of our customer deployments, we couldn't connect to one of the necessary api's in our stack.


Anonymous
TRIALOP

2 years ago

 "type": "error",
  "message": "connect ETIMEDOUT ",
  "error": {
      "errno": -110,
      "code": "ETIMEDOUT",
      "syscall": "connect",
      "address": "<address>",
      "port": 443
  }

Anonymous
TRIALOP

2 years ago

we were connecting to a websocket


2 years ago

@Simon could you link me to your project?


Loading...