Skip to content
KenresoftKenresoft Docs

Astro Troubleshooting

“Not an Astro project”

Section titled ““Not an Astro project””

Run the command from the Astro project root. Astro 5 or newer is required.

@kenresoft-cms/astro is too old

Section titled “@kenresoft-cms/astro is too old”
Terminal window
npx @kenresoft-cms/create astro --update

A managed file reports a conflict

Section titled “A managed file reports a conflict”

The updater did not overwrite your edits. Merge manually, or use --force if you want the generated version. See Astro deployment.

The proxy does not work

Section titled “The proxy does not work”

Check:

  • the site uses server (on-demand) rendering and has a deployment adapter
  • PUBLIC_KENRESOFT_CMS_URL is set
  • the site origin is in the CMS CORS_ORIGINS
  • the global_fetch_strictly_public compatibility flag, if both run on Cloudflare in one account
  • TRUSTED_PROXY_SECRET matches on both sides, if you rely on per-visitor rate limits

Published changes do not appear

Section titled “Published changes do not appear”

A statically generated site fetches content at build time. Rebuild it, or switch to server rendering.

Live Preview shows a 404

Section titled “Live Preview shows a 404”

The token expires after 15 minutes, and the page must render on demand. See Live Preview.

Astro logs “custom src/fetch.ts does not call the actions()/middleware() handler”

Section titled “Astro logs “custom src/fetch.ts does not call the actions()/middleware() handler””

This comes from a src/fetch.ts in your own project, which Astro treats as a custom fetch handler. It is not produced by the CMS packages. Its default export must be an object with a fetch method that forwards to Astro’s default handler.