StripeConnectionError: An error occurred with our connection to Stripe.
See original GitHub issueHave been running into this issue during development. Sometimes everything works fine and other times I get this error
version: 7.20
I’m not sure if its a bug or a connectivity issue
Get stripe account error { Error: An error occurred with our connection to Stripe.
at Constructor._Error (/Users/tunebase/node_modules/stripe/lib/Error.js:12:16)
at Constructor (/Users/tunebase/node_modules/stripe/lib/utils.js:164:17)
at new Constructor (/Users/tunebase/node_modules/stripe/lib/utils.js:164:17)
at /Users/tunebase/node_modules/stripe/lib/StripeResource.js:209:9
at ClientRequest.req.on (/Users/tunebase/node_modules/stripe/lib/StripeResource.js:380:67)
at ClientRequest.emit (events.js:182:13)
at ClientRequest.EventEmitter.emit (domain.js:442:20)
at TLSSocket.socketOnEnd (_http_client.js:425:9)
at TLSSocket.emit (events.js:187:15)
at TLSSocket.EventEmitter.emit (domain.js:442:20)
type: 'StripeConnectionError',
stack:
'Error: An error occurred with our connection to Stripe.\n at Constructor._Error (/Users/tunebase/node_modules/stripe/lib/Error.js:12:16)\n at Constructor (/Users/tunebase/node_modules/stripe/lib/utils.js:164:17)\n at new Constructor (/Users/tunebase/node_modules/stripe/lib/utils.js:164:17)\n at /Users/tunebase/node_modules/stripe/lib/StripeResource.js:209:9\n at ClientRequest.req.on (/Users/tunebase/node_modules/stripe/lib/StripeResource.js:380:67)\n at ClientRequest.emit (events.js:182:13)\n at ClientRequest.EventEmitter.emit (domain.js:442:20)\n at TLSSocket.socketOnEnd (_http_client.js:425:9)\n at TLSSocket.emit (events.js:187:15)\n at TLSSocket.EventEmitter.emit (domain.js:442:20)',
rawType: undefined,
code: undefined,
param: undefined,
message: 'An error occurred with our connection to Stripe.',
detail:
{ Error: socket hang up
at createHangUpError (_http_client.js:322:15)
at TLSSocket.socketOnEnd (_http_client.js:425:23)
at TLSSocket.emit (events.js:187:15)
at TLSSocket.EventEmitter.emit (domain.js:442:20)
at endReadableNT (_stream_readable.js:1094:12)
at process._tickCallback (internal/process/next_tick.js:63:19) code: 'ECONNRESET' },
raw:
{ message: 'An error occurred with our connection to Stripe.',
detail:
{ Error: socket hang up
at createHangUpError (_http_client.js:322:15)
at TLSSocket.socketOnEnd (_http_client.js:425:23)
at TLSSocket.emit (events.js:187:15)
at TLSSocket.EventEmitter.emit (domain.js:442:20)
at endReadableNT (_stream_readable.js:1094:12)
at process._tickCallback (internal/process/next_tick.js:63:19) code: 'ECONNRESET' } },
headers: undefined,
requestId: undefined,
statusCode: undefined }
Issue Analytics
- State:
- Created 4 years ago
- Reactions:11
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Stripe Connection Error - node.js - Stack Overflow
js code to connect to my Stripe account to make a Charge. But I'm getting this error. I'm using Firebase Functions, and this...
Read more >Handle errors | Stripe Documentation
Stripe offers many kinds of errors. They can reflect external events, like declined payments and network interruptions, or code problems, like invalid API ......
Read more >FAILURE: Could not connect to Stripe - WordPress.org
we have the following error on the final checkout page. FAILURE: Could not connect to Stripe (https://api.stripe.com/v1/customers).
Read more >Stripe Connection Error - Ionic Forum - RSSing.com
I have the follow backend Node.js code to connect to my Stripe account to make a ... { Error: An error occurred with...
Read more >Issue with stripe connection - Workers - Cloudflare Community
I am getting “Error: An error occurred with our connection to Stripe.” when I create customer in the worker. It seems something wrong...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It looks at first glance like it’s probably an intermittent connectivity problem. You could try enabling automatic retries to give you some protection against this type of thing.
I had the same issue. It was because I had changed the rules on my firewall. If you run into the issue try disabling your firewall to see if that fixes it, then re-enable the firewall and add the correct rules.