Troubleshooting

Check that the structure file uses the exact PascalCase value registered in BlockRenderer.astro. Confirm that the translation file uses the same block _id values. Also check that the page has a valid layout and that the requested language exists in site.config.json.

Run the project's sync command before building. Check generated files, missing direct dependencies and Astro integrations first. If the error mentions fonts, confirm that the build environment can reach the configured provider or use a local font strategy.

If a block import fails, read its schema and component together. A block installed in content but missing from the generated registry needs to be reloaded through MagiCMS.

Check the exact WEB_APP_URL, FUNCTION_URL and ALLOWED_ORIGINS values. Confirm that the database schema is current and that the browser is using HTTPS for Secure cookies. A 401 usually means the session is missing or expired; a 403 usually means the origin, membership, role or path is not allowed.