#bekahlew_code

1 messages ยท Page 1 of 1 (latest)

patent ruinBOT
#

๐Ÿ‘‹ 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/1216840412572942397

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

polar needle
smoky vineBOT
random flower
#

Hi ๐Ÿ‘‹ is there any context on where the 500 is coming from? Is the Stripe API responding with a 500?

#

Hm, it looks like it's your API responding with the 500, so I don't really have any insight into why it's doing that. Is there anything in your logs showing where the error is coming from?

polar needle
#

Hi @random flower! I'm not sure where it's coming from but I see these errors in the console form the browser.

#

I don't know why the json data would be fine in my localhost and on vercel but not the live production site hosted on amplify.

random flower
#

It's your API responding with the 500, you can see it in the network tab. I'm pretty sure that's saying no JSON data is returned, because the server's code is crashing before it completes the request.

polar needle
#

I saw that in the network tab as well. Would this be an issue with how the data is getting served up from Amplify? Please note that I have mostly worked in front-end code and this is unfamiliar territory for me. I may say some things that don't make sense haha

random flower
#

I'm not sure, all I know is your server seems to be crashing before it can respond.

#

I'd recommend looking through your server logs for indications of what is crashing.

#

If you don't see anything currently, then I'd recommend adding additional logging to your code so you can determine exactly what line isn't completing as expected and begin to diagnose why.

polar needle
random flower
#

Hm, I think that may be a private repo, I'm getting a 404 when I try to look at it.

polar needle
#

let me checked

#

Should be public now

random flower
#

Line 17 there is the line that makes a request to your server. You need to troubleshoot the server-side of this flow rather than the client-side portion.

polar needle
#

Ok, I will do that. Thank you.