La documentación está sólo en inglés por ahora. El resto del sitio sigue su idioma.
Troubleshooting
Common install, cache, API, and plugin problems — and where to look first.
6 lectura mínima
- I only see under construction.
- Install sets
site_public=false. Sign in as admin or editor, open Settings, and publish the site. Anonymous users (and the public API) get a 404-style empty site until then. - The public API returns 404.
- Enable Public API in Settings. Confirm the site is public. Only published content is listed unless
?preview=1is sent with an editor session. Checklocalematches a site language. - Admin mutations fail with CSRF errors.
- Send cookie
jf_csrfand headerx-csrf-tokenon POST/PATCH/PUT/DELETE to/api/*. Login and install are exempt. The hydrated admin client does this automatically; your own scripts must copy the cookie. - I changed CACHE_* or gzip and nothing happened.
- The cache singleton is created once per process. Restart Node, or save from Tools so Passenger writes
tmp/restart.txt. - Pages look stale after I edited content.
- Content routes invalidate
content:on save. If you edited theme CSS or menus, wait for TTL or Clear cache now. Preview with?previewbypasses page cache. - Admin shows “content_types doesn't exist”.
- The site was installed before migration
0005. Restart the app so boot migrations run, or POST/api/db/migrateas administrator, then reload Content types. - Plugin upload is rejected.
- The package must declare its own license, and that license must be GPL-compatible (core is MIT; extensions are not). Id must be namespaced (
acme.plugin). Package authenticity is required by default: the archive needs a valid Marketplace signature or a SHA-256 digest listed inJUSTFLOWS_TRUSTED_PACKAGE_DIGESTS. SetJUSTFLOWS_ALLOW_UNSIGNED_PACKAGES=1only as a deliberate development escape hatch. Check the zip is a valid.jfpkg. - Admin UI says it is not built.
- The server requires both
apps/server/admin-ui/dist/clientandapps/server/admin-ui/dist/server. Run the admin production build (or use the development server). Official release archives and Docker images include both bundles. - Database connection fails in the wizard.
- Driver, host, port, name, user, password must match. Docker Postgres is on the compose network — use the service hostname from the compose file, not
localhostfrom inside the web container unless ports are mapped that way. - CLI talks to the wrong host.
- Set
ADMIN_URLto the same origin the browser uses. Default ishttp://localhost:3001.
Tip
Site Health (/admin/health) and LOG_LEVEL=debug are the first two diagnostics. GitHub issues: JustFlows/justflows-ce.