Common errors and how to fix them.
Updated
DASH4DEVS_API_KEY not setThe CLI couldn't find your key. Add it to .env.local in the directory where you're running the command. Secret keys start with sk_test_ or sk_live_.
The key was deleted, regenerated, or belongs to a different environment. Generate a fresh one at Settings → API Keys in your dashboard.
The API key doesn't have the admin or api.write scope. Edit the key in the dashboard and set its scope to admin, or create a new admin-scoped key.
One or more uploads failed silently. Re-run dash4devs build. The manifest endpoint will detect what's still missing and only retry those files.
Your next.config.mjs isn't reading NEXT_PUBLIC_ASSET_PREFIX. Make sure the assetPrefix line is in place, then rebuild and redeploy.
DO Spaces sets permissive CORS by default. If you've tightened the bucket's CORS configuration, add your storefront origin as an allowed origin for GET/HEAD.
Your browser has cached the old HTML. Hard-refresh (Ctrl+Shift+R or Cmd+Shift+R). If the Node server is also caching rendered HTML, restart it or wait for the cache to expire.
Set DASH4DEVS_DEBUG=1 to print full error stack traces when a command fails.