Документация пока доступна только на английском языке. Остальная часть сайта соответствует вашему языку.

Troubleshooting

Common install, cache, API, and plugin problems — and where to look first.

6 минута чтения

Where do I get help with Justflows Cloud?: The help center has short guides on getting started, domains, publishing, plans and limits, AI agents, and security, plus answers to questions other users asked. For anything else, contact support: the team replies by email. Self-hosting? Ask on Discord or open an issue on GitHub.
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=1 is sent with an editor session. Check locale matches a site language.
Admin mutations fail with CSRF errors.: Send cookie jf_csrf and header x-csrf-token on 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 ?preview bypasses 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/migrate as 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 in JUSTFLOWS_TRUSTED_PACKAGE_DIGESTS. Set JUSTFLOWS_ALLOW_UNSIGNED_PACKAGES=1 only 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/client and apps/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 localhost from inside the web container unless ports are mapped that way.
CLI talks to the wrong host.: Set ADMIN_URL to the same origin the browser uses. Default is http://localhost:3001.
Passkey sign-in fails with an origin or RP error.: Behind a reverse proxy, the passkey origin comes from X-Forwarded-Host and X-Forwarded-Proto, which are trusted only from addresses in TRUST_PROXY. Set the proxy's address there. Check that Security → Headers still allows publickey-credentials-get=(self) in Permissions-Policy, and that the RP ID under Security → Passkeys matches the hostname the passkey was created on.
I lost my passkey.: Sign in with your password and a recovery code, then remove the lost passkey from your account. If you also lost the password, reset it by email first. If the recovery codes are gone too, an administrator can clear your sign-in factors under Users → Edit user → Sign-in factors.
A page disappeared after I turned off a plugin.: The entry or its content type probably has a visibility rule from that plugin. A rule whose plugin is off denies, so the page answers 404. Turn the plugin back on, or remove the rule from the Visibility panel. Check access shows which rule decided.
A plugin update stops and asks for approval.: The new version asks for permissions the installed one does not have. Review them and approve the update in Plugins or Marketplace. Automatic updates wait for this manual step.
The cache shows as Unavailable or bypassed.: The selected plugin cache store is not ready: its plugin is inactive on the main site, it cannot connect, or an invalidation failed. Pages still render without caching. Fix the store, then use Clear cache now, or switch the driver back to filesystem.

Tip

Site Health (/admin/health) and LOG_LEVEL=debug are the first two diagnostics. GitHub issues: JustFlows/justflows-ce.