nextjs - 💡(How to fix) Fix Critical: Stripe API Connection Failures from Vercel Functions [1 comments, 2 participants]

Link to the code that reproduces this issue

ttps://github.com/0xjc65eth/-vercel-stripe-connection-bug

To Reproduce

Provide environment information * Please run next info in the root directory of your project and paste the results. You might need to use npx --no-install next info if next is not in the current PATH.

Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.6.0 Binaries: Node: 20.17.0 npm: 10.8.2 Yarn: 1.22.22 pnpm: 9.10.0 Relevant Packages: next: 15.0.0-canary.148 eslint-config-next: 15.0.0-canary.148 react: 19.0.0-rc-3dfd5d9e-20240910 react-dom: 19.0.0-rc-3dfd5d9e-20240910 typescript: 5.6.2 Next.js Config: output: N/A Field can not be empty Which area(s) are affected? (Select all that apply) * An option must be selected Which stage(s) are affected? (Select all that apply) * An option must be selected Another way you can help the maintainers' job is to pinpoint the canary version of next that introduced the issue. Check out our releases, and try to find the first canary release that introduced the issue. This will help us narrow down the scope of the issue, and possibly point to the PR/code change that introduced it. You can install a specific version of next by running npm install next@<version>.

Additional context Any extra information that might help us investigate. For example, where are you deploying your application (Vercel, Docker, other platform)? Is it only reproducible on that platform, or locally too? Is the issue only happening in a specific browser? etc.

Markdown Editor Markdown input: edit mode selected. Write Preview I tested my reproduction against different canary releases, and the first one that introduced the bug was "15.0.0-canary.148", since reverting to "15.0.0-canary.147" works.

or

I am hosting via Docker with the recommended output: "standalone" option, and if I remove that option or try a different hosting option, I cannot reproduce the same issue. Metadata Assignees No one assigned Labels No labels Type Bug Projects No projects Milestone No milestone Remember, contributions to this repository should follow its contributing guidelines, security policy and code of conduct.

Current vs. Expected behavior

Provide environment information * Please run next info in the root directory of your project and paste the results. You might need to use npx --no-install next info if next is not in the current PATH.

Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.6.0 Binaries: Node: 20.17.0 npm: 10.8.2 Yarn: 1.22.22 pnpm: 9.10.0 Relevant Packages: next: 15.0.0-canary.148 eslint-config-next: 15.0.0-canary.148 react: 19.0.0-rc-3dfd5d9e-20240910 react-dom: 19.0.0-rc-3dfd5d9e-20240910 typescript: 5.6.2 Next.js Config: output: N/A Field can not be empty Which area(s) are affected? (Select all that apply) * An option must be selected Which stage(s) are affected? (Select all that apply) * An option must be selected Another way you can help the maintainers' job is to pinpoint the canary version of next that introduced the issue. Check out our releases, and try to find the first canary release that introduced the issue. This will help us narrow down the scope of the issue, and possibly point to the PR/code change that introduced it. You can install a specific version of next by running npm install next@<version>.

Additional context Any extra information that might help us investigate. For example, where are you deploying your application (Vercel, Docker, other platform)? Is it only reproducible on that platform, or locally too? Is the issue only happening in a specific browser? etc.

Markdown Editor Markdown input: edit mode selected. Write Preview I tested my reproduction against different canary releases, and the first one that introduced the bug was "15.0.0-canary.148", since reverting to "15.0.0-canary.147" works.

or

I am hosting via Docker with the recommended output: "standalone" option, and if I remove that option or try a different hosting option, I cannot reproduce the same issue. Metadata Assignees No one assigned Labels No labels Type Bug Projects No projects Milestone No milestone Remember, contributions to this repository should follow its contributing guidelines, security policy and code of conduct.

Provide environment information

Operating System:
    Platform: darwin
    Arch: arm64
    Version: Darwin Kernel Version 23.6.0
  Binaries:
    Node: 20.17.0
    npm: 10.8.2
    Yarn: 1.22.22
    pnpm: 9.10.0
  Relevant Packages:
    next: 15.5.3
    react: 19.0.0
    react-dom: 19.0.0
    stripe: 14.25.0
    typescript: 5.7.2
  Next.js Config:
    output: N/A

Which area(s) are affected? (Select all that apply)

Connection

Which stage(s) are affected? (Select all that apply)

Vercel (Deployed)

Additional context

Provide environment information * Please run next info in the root directory of your project and paste the results. You might need to use npx --no-install next info if next is not in the current PATH.

Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.6.0 Binaries: Node: 20.17.0 npm: 10.8.2 Yarn: 1.22.22 pnpm: 9.10.0 Relevant Packages: next: 15.0.0-canary.148 eslint-config-next: 15.0.0-canary.148 react: 19.0.0-rc-3dfd5d9e-20240910 react-dom: 19.0.0-rc-3dfd5d9e-20240910 typescript: 5.6.2 Next.js Config: output: N/A Field can not be empty Which area(s) are affected? (Select all that apply) * An option must be selected Which stage(s) are affected? (Select all that apply) * An option must be selected Another way you can help the maintainers' job is to pinpoint the canary version of next that introduced the issue. Check out our releases, and try to find the first canary release that introduced the issue. This will help us narrow down the scope of the issue, and possibly point to the PR/code change that introduced it. You can install a specific version of next by running npm install next@<version>.

Additional context Any extra information that might help us investigate. For example, where are you deploying your application (Vercel, Docker, other platform)? Is it only reproducible on that platform, or locally too? Is the issue only happening in a specific browser? etc.

Markdown Editor Markdown input: edit mode selected. Write Preview I tested my reproduction against different canary releases, and the first one that introduced the bug was "15.0.0-canary.148", since reverting to "15.0.0-canary.147" works.

or

I am hosting via Docker with the recommended output: "standalone" option, and if I remove that option or try a different hosting option, I cannot reproduce the same issue. Metadata Assignees No one assigned Labels No labels Type Bug Projects No projects Milestone No milestone Remember, contributions to this repository should follow its contributing guidelines, security policy and code of conduct.