Troubleshooting common issues

Quick fixes for the issues people hit most often, from purchase to local setup to deployment.

Purchase did not unlock

• Make sure you are signed in with the same email you used at checkout.
• On /dashboard/purchase, use Recover my purchase / Check again and wait a minute.
• Confirm the Stripe webhook is delivering with a 200. A missing or misconfigured live webhook is the top cause. See Setting up Stripe webhooks (live).
• Still stuck? Open a ticket with your receipt.

GitHub invite problems

• Enter your GitHub username, not your email.
• Check the username spelling; a typo or non-existent username makes the invite fail.
• Accept the invite from your GitHub notifications, then refresh status on the purchase page.
• See Get repository access on GitHub.

Checkout fails with "No such coupon"

• STRIPE_SALE_COUPON_ID must be a valid Coupon ID (e.g. your_coupon_id) or a Promotion Code ID (promo_...).
• A coupon with a past "redeem by" date stops working; use a coupon with no expiry for an open-ended sale.
• See Configure Stripe payments.

Database connection errors

• Verify DATABASE_URL and that the database is reachable.
• Managed databases usually need sslmode=require.
• Run pnpm --filter @faststaq/server db:migrate:deploy to apply migrations.
• See Configure database and Redis.

Redis / job errors (NOAUTH Authentication required)

• Managed Redis requires a password: set REDIS_PASSWORD or include credentials in REDIS_URL.
• Use rediss:// for TLS providers.

Login redirect loop (/dashboard to /login)

• On split front-end/API domains, set COOKIE_DOMAIN=.yourdomain.com so the front-end can see the auth cookie.
• See Authentication module.

Emails not sending

• Check SMTP credentials and that the worker process and Redis are running (email is queued).
• Look at the worker logs for the SMTP error. See Configure email and SMTP.

Uploads failing or links 404

• File storage stays off until S3_BUCKET, S3_ACCESS_KEY, and S3_SECRET_KEY are set.
• Set S3_PUBLIC_URL (and the client NEXT_PUBLIC_STORAGE_URL) for working public links.
• See Configure file storage (R2/S3).

Build or dependency errors

• Use Node.js 20+ and pnpm 8+. Run pnpm check to verify prerequisites.
• Delete node_modules and reinstall with pnpm install if the lockfile state looks off.

Still need help?

If your issue is not here, open a support ticket with the exact error, what you tried, and your environment (local or production).