Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If Stripe is not configured, the GET /v1/me fails, and web keels over when trying to log in #5

Open
tjanczuk opened this issue Nov 17, 2023 · 1 comment

Comments

@tjanczuk
Copy link
Member

Current

  1. Auth0 configured on web
  2. Stripe not configured on api
  3. Attempting to log in calls /v1/me while keels over with
53-6b60db04f7c2dcbb.js:1 Error: Failed to fetch HTTP GET /api/proxy/v1/me: HTTP 418 Unknown. Details: Stripe is not configured in the API component. Missing required environment variables: LETSGO_STRIPE_LIVE_MODE, LETSGO_STRIPE_TEST_SECRET_KEY, LETSGO_STRIPE_TEST_PUBLIC_KEY, LETSGO_STRIPE_TEST_WEBHOOK_KEY.
    at createResultNotOkError (https://gwdvbituqq.us-west-2.awsapprunner.com/_next/static/chunks/app/(dashboard)/manage/page-f98a44f2471eaedc.js:1:3013)
    at async https://gwdvbituqq.us-west-2.awsapprunner.com/_next/static/chunks/app/(dashboard)/manage/page-f98a44f2471eaedc.js:1:3373
    at async 940-1aeca67aaff6f124.js:9:9968

(this shows up in the browser console)

Expected

You can log in to web without stripe being configured.
If the Stripe environment variables are not defined, the /

@tjanczuk
Copy link
Member Author

Hypothesis: this only happens if there are tenants on a Stripe plan already, which would be less of an issue, as it is clearly a misconfiguration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant