#j-_api

1 messages · Page 1 of 1 (latest)

feral reefBOT
#

👋 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/1235309309756309666

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

ionic arrow
#

Hi there

white hollow
#

Hi

#

I dont understand why i am getting some errors

#

On localhost everything works fine

#

on production isnt

ionic arrow
#

Are you using Payment Element here?

#

Can you clarify exactly what you mean by "Stripe Card form"?

white hollow
#

this

ionic arrow
#

Yep okay that is Payment Element

#

And where in your code exactly do you get this 404? Generally a 404 indicates you couldn't reach your backend

white hollow
#

but it loads first some stripe info and then gets stuck

#

and everything on my website is loading correctly

#

also get this:
m.stripe.network/inn…n=6&preview=false:1 Uncaught (in promise) undefined
Promise.then (async)

ionic arrow
#

The m.stripe error is a red-herring and you can ignore that

#

What are you doing at line 121?

#

That is causing that Axios Error

white hollow
#

since is on production, i dont know where is line 121

ionic arrow
#

Yep so that request is to your own endpoint

#

So you'll need to debug on your side why you aren't able to hit your backend here

#

I'd recommend adding logs in your production code to be able to better troubleshoot

white hollow
#

but why on localhost works fine

#

and how do i know where is line 121 on my code?

ionic arrow
#

You are the developer and need to troubleshoot your own code here. Your server is completely different when developing locally versus in a hosted production environment. There could be many reasons why it would error in one place and not the other.

#

You can inspect the browser source code to determine exactly where it is erroring