#B33fb0n3
1 messages · Page 1 of 1 (latest)
What error are you getting here? I can check if something is going on
Do you have a request ID from a request that failed this way? (req_123)
getting this error: https://hastebin.com/eboderecok.lua
Hastebin is a free web-based pastebin service for storing and sharing text and code snippets with anyone. Get started now.
I have no request id :/
Maybe you also need this?
https://hastebin.com/filapajule.sql
Hastebin is a free web-based pastebin service for storing and sharing text and code snippets with anyone. Get started now.
ah ok
Hmm you are using Node SDK + typescript?
I just use nodejs, but not typescript
Sure. It's initializied like that in the backend:
const stripe = require('stripe')(getStripeKey);
My code that will be executed look like this:
paymentIntent = await stripe.paymentIntents.create({
amount: (totalPrice * 100),
currency: 'eur',
automatic_payment_methods: {
enabled: true,
},
});
Have you logged out getStripeKey?
no
Hmm okay can you double check on that real quick. But also can you run through the steps here: https://github.com/stripe/stripe-reachability
And ensure you can reach Stripe
give me a second, I try to see my secret key...
I can't see the secret key, cause it's secret.
I can't upload any .sh Files to the Backend and can't execute it.
Hmm nothing changed on our end with authentication that I'm aware of.
Has anything on your server changed recently?
Hmm...
currently I am building an onlineshop. So I would say: yes, it changes very often in the last hours...
I think you are going to have to debug on your end why your server can't reach Stripe. It does seem like you have the right key because otherwise I would expect a different error. But, something is preventing the outbound request to Stripe it seems.
what could it be? It's the first line of the backend code 😅
It likely isn't your code. It is likely something with your server config
Have you tested trying to hit the API locally with this code?
(in testmode)
oh ok... I haven't yet
That would be a good next step
I've never done that, how does that work?
Are you a developer?
I can't really walk you through spinning up a local server
But you would mostly just use an Express server and run it locally
We have a lot of code examples in our docs that do this
I am. I just use the aws Servers and my computer creates his own server via React on Port 3000
Okay then you are running locally then?
So if you run this code in testmode from your local server then do you hit the same issue? I assumed the original issue was reported from a production environment?
It's not a real server. It's just the react-scripts start-Command and that does it
Right, that is your local server
no, also in test environment
Sorry, what I mean is you are accessing your AWS server locally here
So yeah, if you want to rule out the code being the issue, you could create a simple project with an Express server hosted locally like we show in our code snippets for Node
That would indicate that something is blocking your AWS requests to Stripe, as it can't actually form a connection using that Server
Oh I can't. These one are in eu-north somewhere. I don't know, where they are in reallife
I don't mean actually physically accessing them. I mean the configuration for how they are set up to run
hm, am I the only one, that have authentification issues?
Yes
I haven't heard of any one else
Have you tried accessing any other APIs using your AWS server?
ah ok. I don't need to setup them. I just make the code and the server runs evertime
Right, something about how your server was configured/set up is likely the issue
I access data from aws graphql itself and that works perfectly
you mean, I am not the only one that has this issue?
Well people have issues with their Server configs all the time
But I'm saying this isn't a Stripe issue specifically. I haven't heard of many other folks reporting the same thing you are which could indicate something broke on our side
hm ok. I gonna check this tomorrow. I can just reply in this chat, right?
We don't cover this channel on weekends, but you can post in the main channel on Monday and someone may be around to help (coverage will be low next week due to holidays)
ok, thanks for your help!