Account, billing & limits
This page covers errors that come from your account, plan, or usage limits rather than from your code. Each section starts with the exact symptom you see, explains why it happens, and gives the fix. For failures during a build or deploy, see Builds & deploys; for database issues, see Databases.
”Add a payment method to continue” (HTTP 402)
Section titled “”Add a payment method to continue” (HTTP 402)”You try to create or deploy a resource and the request is blocked with an HTTP 402 and a message asking you to add a payment method.
Why this happens. PandaStack requires a verified payment method before you can create or deploy resources — even on the Free plan. This is a fair-use and anti-abuse check, not a charge: you are not billed until you explicitly upgrade to a paid plan.
Fix
- Click the inline Add payment method prompt shown with the error, or go to Settings → Billing in the dashboard.
- Add and verify a card.
- Retry the blocked action — it will go through once the payment method is on file.
GitHub connect fails with a payment message
Section titled “GitHub connect fails with a payment message”You try to connect the GitHub App and instead of an installation succeeding, you see a message asking you to add a payment method.
Why this happens. Connecting the GitHub App is behind the same payment-method check described above. The installation itself worked on GitHub’s side — PandaStack just won’t complete the connection until a card is on file.
Fix
- Add a card via the prompt or Settings → Billing.
- That’s it — the same GitHub installation is retried automatically after the card is added. You do not need to uninstall or reinstall the GitHub App.
No verification email after email/password signup
Section titled “No verification email after email/password signup”You signed up with an email and password, but sign-in won’t complete and no verification email has arrived.
Why this happens. Email/password accounts must verify their address. A verification link is sent when you sign up, and sign-in only completes after you click it. GitHub and Google sign-ins are pre-verified and skip this step entirely.
Fix
- Check your spam folder.
- On the verify screen, click Resend to send a fresh verification link.
- If you’d rather skip verification, sign in with GitHub or Google instead — those accounts are pre-verified.
No welcome email
Section titled “No welcome email”You signed up but never received a welcome email.
Why this happens. Transactional email from PandaStack is sent from postmaster@pandastack.io, and some mail providers file it as spam.
Fix
Check your spam folder for mail from postmaster@pandastack.io.
Your site shows a “Bandwidth limit reached” page
Section titled “Your site shows a “Bandwidth limit reached” page”Visitors to your site see a bandwidth-limit page instead of your content.
Why this happens. Each organization has a monthly bandwidth allowance:
| Plan | Monthly bandwidth |
|---|---|
| Free | 100 GB |
| Pro | 500 GB |
| Premium | 1 TB |
You get a warning email at 80% of the allowance. At 100%, your sites serve the bandwidth-limit page instead of content. The counter resets at the start of each calendar month, and your current usage is visible on the dashboard’s usage card.
Fix
- Upgrade your plan — service is restored within seconds of upgrading.
- Or wait for the reset at the start of the next calendar month.
See Usage & metering for how bandwidth is measured.
”You’ve reached the limit” when creating a resource
Section titled “”You’ve reached the limit” when creating a resource”Creating a new web service, static site, or database fails with a limit error, or Functions/Cronjobs are unavailable on your plan.
Why this happens. The Free plan caps how many resources an organization can have:
| Resource | Free plan limit |
|---|---|
| Web services (containers) | 5 |
| Static sites | 5 |
| Databases | 1 |
| Functions | paid-only |
| Cronjobs | paid-only |
Pro and Premium have no count limits.
Fix
Delete a resource you no longer need, or upgrade — see Plans for the full comparison.
A feature shows a “Pro feature” lock
Section titled “A feature shows a “Pro feature” lock”A page or setting shows a lock and a note that it’s a Pro feature.
Why this happens. These features are only available on paid plans:
Fix
Upgrade to a paid plan — see Plans.
Builds stop running mid-month (build minutes exhausted)
Section titled “Builds stop running mid-month (build minutes exhausted)”Builds that worked earlier in the month stop running.
Why this happens. Build time is metered monthly per plan:
| Plan | Build minutes / month |
|---|---|
| Free | 300 |
| Pro | 1,000 |
| Premium | 2,500 |
Paid plans bill overage beyond the included minutes at the usage rates — see Usage & metering.
Fix
- On Free: wait for the monthly reset, or upgrade to a paid plan where overage is billed instead of blocked.
- On paid plans: builds continue and overage is billed per the usage rates; check Usage & metering to see where the minutes went.
Static upload rejected as too large
Section titled “Static upload rejected as too large”Uploading a static site fails with a size error.
Why this happens. Static uploads are capped by plan: 30 MB compressed on Free and 100 MB on paid plans.
Fix
- Shrink the upload (drop source maps, unoptimized media, or files that don’t need to ship) so the compressed archive fits your plan’s cap.
- Or upgrade for the 100 MB cap — see Plans.
- For large apps, consider deploying from Git instead of uploading — see Static sites.
”This account has been suspended”
Section titled “”This account has been suspended””You can’t use your account and see a suspension notice.
Why this happens. The account has been suspended by PandaStack.
Fix
Contact support@pandastack.io to review the suspension.
Still stuck?
Section titled “Still stuck?”If none of the above matches your error, check the build logs on your latest deployment for the exact failure message (see Build & buildpacks), then email support@pandastack.io with the error text and your organization name.