07. Launch Checks and Common Errors

This chapter is for the final check before you call the system live, plus the most common deployment mistakes people hit on their first pass.

1. Launch checklist

Before you call the deployment done, verify the basics one more time.

Frontend access

Check:

• the public site opens normally
• the admin opens normally
• the correct domains are being used

Admin access

Check:

• login works
• the admin can read real project data
• obvious configuration pages are usable

Core user flow

Check:

• signup or login works
• critical pages are not empty
• the product can read the current app_key data correctly

Optional modules

If you enabled them, also check:

• payment flow
• AI flow
• blog flow
• notifications
• check-in

2. Common error 1: service binding target not found

Typical causes

• you renamed a Worker
• not all required Workers were created first
• you deployed using the wrong Cloudflare account

What to do

• restore the expected Worker names
• create every required Worker target
• run wrangler whoami and verify you are in the intended account

3. Common error 2: D1, KV, or R2 resources cannot be found

Typical causes

• resources were never created
• config files still contain placeholders
• resource IDs were copied incorrectly

What to do

• verify the resources exist in Cloudflare
• compare config values carefully
• replace all placeholder values before redeploying

4. Common error 3: admin login returns 401

Typical causes

• auth secrets are wrong
• frontend points at the wrong auth URL
• the domain configuration is inconsistent

What to do

• verify auth secrets again
• verify auth endpoints again
• confirm the deployed frontend is using the latest environment values

5. Common error 4: pages open, but all data is empty

Typical causes

• the frontend points at the wrong backend
• the wrong app_key is in use
• the admin and frontend are not reading the same dataset

What to do

• verify frontend environment variables
• verify the real app_key
• confirm the backend services and admin data belong to the same project

6. Common error 5: the payment page opens, but payment does not work

Typical causes

• provider keys are missing
• webhook config is incomplete
• pricing or product data is not configured correctly

What to do

• verify payment provider secrets
• verify webhook configuration
• verify product and pricing data in the admin

7. Common error 6: the AI page opens, but sending a message fails

Typical causes

• provider keys are missing
• model config is incomplete
• gateway or upstream settings are wrong

What to do

• verify AI provider keys
• verify model mapping
• verify the deployed AI service is reading the intended environment values

8. Common error 7: Pages deploy says Invalid binding SESSION

Cause

This usually means the expected binding exists in code or config, but is not properly created or attached in the target environment.

What to do

• verify the Cloudflare binding exists
• verify the Pages environment is using the right binding name
• redeploy after fixing the binding configuration

9. One final recommendation

If something breaks, do not panic and do not rewrite half the setup at once.

Use the simplest debugging loop:

1. identify one likely cause
2. change one thing
3. redeploy or retry
4. observe the result

That is the fastest way to converge on a stable production setup.