Custom deployments not firing to endpoint properly | Railway | Page 1

versed sierraBOT Jul 15, 2024, 6:28 PM

#

Project ID: N/A

heavy snow Jul 15, 2024, 6:28 PM

#

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

#

that would be great

thorn pelican Jul 15, 2024, 6:29 PM

#

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 @quick nest

heavy snow Jul 15, 2024, 6:30 PM

#

we should be

quick nest Jul 15, 2024, 6:33 PM

#

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

heavy snow Jul 15, 2024, 6:33 PM

#

has to do with our internal stack which is proprietary

quick nest Jul 15, 2024, 6:33 PM

#

right but im not going to ask you about anything proprietary

heavy snow Jul 15, 2024, 6:34 PM

#

give me one minute sorry

quick nest Jul 15, 2024, 6:36 PM

#

you are using the project webhooks right?

heavy snow Jul 15, 2024, 6:42 PM

#

looping in another engineer

#

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

#

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

#

we were connecting to a websocket

#Custom deployments not firing to endpoint properly