FAQ and Troubleshooting

FAQ and Troubleshooting

Short answers first; fixes follow. If something is missing, ask in Discussions or read SUPPORT.md. Report vulnerabilities privately (SECURITY.md).

Questions

Where does my data live? Page content is files in a Git repository on your server (and on your remote, if connected). PostgreSQL holds the index, access rights and live-editing state. Stop using Folio and the files are still there. See Backups, Updates and Monitoring.

Does it work offline? Documents and boards you opened on the device stay editable, and new ones can be created; they reach the server by themselves. Data tables, forms, uploads and templates need a connection, and so does opening Folio in a fresh browser session.

Do you support SSO, SAML, SCIM or user groups? No. Sign-in is email and password, optionally Google for listed domains. There is no end-to-end encryption of content.

Is there a hosted cloud version? Not documented. You run the server (Docker, PostgreSQL, Redis, a persistent disk). Serverless hosting cannot run it.

Which AI provider does the assistant use? Cursor only, with a personal, space or instance key (Set Up Folio AI). Everything else works without a key.

Which Git hosts work? Saved tokens exist for GitHub and GitLab; other hosts are not documented. A remote can be connected to a space only if it is empty; to start from an existing repository, create the space by cloning it.

Why is the history empty right after I edited? The commit comes about 90 seconds after the space goes quiet. Sync commits at once.

Languages and mobile? The interface is English and Ukrainian; content is not translated, and titles can be in any script (new file names are Latin only). There is no mobile app; the layout is responsive.

Is the demo safe for real data? No. It is shared and resets every 24 hours.

Troubleshooting

Problem	Fix
The page does not open	docker compose ps and docker compose logs app --tail 100
Port 4870 is in use	Put FOLIO_PORT=4880 in .env, set PUBLIC_URL to match, docker compose up -d
Sign-in does nothing on a server	The browser address and PUBLIC_URL must match exactly, including http or https
Real-time editing or live tables do not update	The reverse proxy must pass WebSocket connections (Upgrade, Connection; /collab on public sites)
Public site address opens main Folio, a 404 or a certificate error	Keep the original Host header, a subdomain is exactly one label under PUBLIC_SITES_DOMAIN, check DNS and certificate; changes take up to ten seconds
Space shows Conflict	Open the listed pages, fix the markers as plain text, or Take the version from git (a backup branch is made first)
Push fails	A protected branch refuses direct pushes; point the space at another branch
A change in Git is not in Folio	Wait for the fetch (about three minutes) or press Sync
After upgrade the space is slow for minutes	The one-time re-index; wait for the scan to finish
A new space from a plain repository wrote ids into every file	A space over a whole repository without .obsidian/ writes ids; tick Light footprint or set a root path (Docs as Code)
Confluence import: "token invalid" or "not found"	Check the token's rights and the link; Confluence reports a missing page and missing access identically (Migrate from Confluence)
An MCP client cannot connect	Check PUBLIC_URL, HTTPS for OAuth clients, the token scope, and that a header client sends Authorization: Bearer folio_pat_... (Connect AI Agents)
An artifact page is blank, or says "works partially"	It loads something from a host that is not on the CDN list, or calls Claude or your own API, which an artifact cannot do. Ask the agent to inline the data and use only the allowed CDNs (Artifacts)
Start from scratch	docker compose down --volumes deletes every page and account

The complete list of limits: LIMITATIONS.md.

See also

Install guides · Getting Started · Folio vs. Notion · Alternatives