#leo_api

1 messages ¡ Page 1 of 1 (latest)

coarse vigilBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1332049663498649671

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

smoky ruin
#

Hello! Can you provide more details, such as the error logs from your server?

tidal scroll
#

"cause": {
"message": "Request aborted due to timeout being reached (80000ms)",
"stack": "Error: Request aborted due to timeout being reached (80000ms) | at /home/app/node_modules/stripe/cjs/RequestSender.js:326:37 | at process.processTicksAndRejections (node:internal/process/task_queues:105:5)"
}

#

Not sure if there's something wrong with my keys that is invalid now, or if there's something going on with my account

smoky ruin
#

If this was a key issue there would be a different error.

#

Can you log in to the server and run commands?

#

Like can you run curl https://api.stripe.com/healthcheck from the server?

tidal scroll
#

Yeah I'll ssh into the pod and run this

#

It seems to be hanging

#

Ran it in my local terminal and it returned a 200 right away

#

On the pod it is hanging

smoky ruin
#

Okay, so something is wrong at a low level, not related to your code. It could be that outbound connection to our API are being blocked. Are you running a firewall or anything like that?

tidal scroll
#

I'll talk to the devops teams

#

This was helpful to help me track it down tho, thanks!

smoky ruin
#

No problem, hope you can track it down!