PLATFORM

  • Tails

    Create websites with TailwindCSS

  • Blocks

    Design blocks for your website

  • Wave

    Start building the next great SAAS

  • Pines

    Alpine & Tailwind UI Library

  • Auth

    Plug'n Play Authentication for Laravel

  • Designer comingsoon

    Create website designs with AI

  • DevBlog comingsoon

    Blog platform for developers

  • Static

    Build a simple static website

  • SaaS Adventure

    21-day program to build a SAAS

COMMUNITY
MORE
Question By

Durgesh Gupta

Unsolved
Back to All Questions

Wave 500 Stripe API error

ilearnbydoing ・

Aug 12th, 2020 08:16 AM

Getting Error

Could not connect to Stripe (https://api.stripe.com/v1/setup_intents). Please check your internet connection and try again.

When vist to plan page: http://wave.test/settings/plans

Report
DigitalOcean Laravel News Genesis
bobbyiliev ・

Aug 13th, 2020 01:47 PM

Hello,

Are you using the lastest Wave 1.0.3 version or Wave 1.0.2?

Report
ilearnbydoing ・

Aug 13th, 2020 02:05 PM

Where can I can check? though I Downloaded just couple of days before with a folder called wave-1.0.2.

Report
ilearnbydoing ・

Aug 13th, 2020 02:14 PM

I dont know what causes the issue but actually its now working fine? most probably since it was not internally able to connect to Stripe API server this possibly issue may have fixed as my MBP restarted today after MacOS upgrade.

I also noticed the release of V1.0.3 just upgraded and it upgraded smoothly without any error.

Thanks

Report
2
tnylea ・

Aug 13th, 2020 06:24 PM

Yeah, we had to put through an update for the latest version to work with the new Stripe API.

The solution is to upgrade to the latest version ;)

Report
guppy ・

Aug 14th, 2020 07:50 PM

Will just upgrading wave do the job? or do i also have to upgrade the theme?

Report
ilearnbydoing ・

Aug 15th, 2020 04:48 AM

It was fixed before upgrade. I had an issue with API server connecting 500 error as my Valet server was unable to make contact with Stripe API server I reboot the MacbookP and worked. The issue was most likely with Valet server configuration.

Report
1