Troubleshooting

Sign-in fails

Check credentials in apps/admin/.env. Register the exact STORMY_CMS_REDIRECT_URL in your site's allowed redirect URLs. Restart after environment changes.

Check that your account belongs to the site.

A page fails to load

Check the site credentials and slug. The starter uses about for /about and an empty slug for /.

A saved edit does not appear

The starter caches pages in the site process. Restart it to clear cached content, then review the caching policy in apps/site/src/app/(pages)/[...slug]/page.tsx.

A component is missing

Match its name to a key in packages/components/src/index.ts. For missing picker options, check placement rules.

Page content disappears inside a layout

Add an Outlet to the layout and save. Each layout in a nested chain needs an outlet for its child content.

Deeply nested content is missing

The client queries three child levels. Use a custom query for deeper trees.

A write fails

Page and layout writes need a valid editor JWT and site credentials. Check the session, required inputs, and layout ID against the API reference.

For rate-limit errors, wait for the retry delay in the response.

Uploads fail

Check the admin's S3_* settings and bucket permissions. See Media storage.

Where do I manage billing and team access?

Use your site's Plan and Users pages in the account portal. The portal lists current prices and allowances.