Skip to content

πŸ“š The open-source, offline-first Notion, Obsidian & Confluence alternative. Advanced Markdown, multi-tenant teams, OIDC/SSO, and local S3 backups. Deploy in one command.

1.6 KB
Raw Blame

title: Troubleshooting description: Resolve login, file, TLS, and startup issues. navigation: icon: i-lucide-wrench

Login loop or immediate logout

The most common cause is COOKIE_DOMAIN. It must be the frontend/API common domain, without a protocol or path. For wiki.example.com and api.example.com, use example.com.

Also verify that ALLOW_UNSECURE=false behind an HTTPS proxy, or true for a local HTTP trial. After changing it, clear domain cookies or test in a private window.

Images and files do not load

Open the file URL in your browser developer tools. Check the combination of CDN_URL, CDN_ENDPOINT, and MINIO_BUCKET. CDN_ENDPOINT should normally match the bucket name with slashes, for example /alexandrie/.

Also verify that your reverse proxy publishes the S3 origin and that no CORS rule blocks the browser.

Backend does not start

docker compose ps
docker compose logs --tail=200 mysql rustfs backend

Wait for MySQL and RustFS health checks: the backend waits for them before starting. MySQL passwords must be consistent between the mysql service and the backend variables.

TLS error to S3 storage

MINIO_SECURE must match the protocol actually used between the backend and S3 endpoint. For a certificate issued by a private authority, mount its PEM certificate in the backend container and set MINIO_CA_PATH to that path. Use MINIO_INSECURE_TLS=true only for temporary diagnostics.

Gather useful information

Include the Alexandrie version, deployment method, relevant anonymised logs, and generic URLs in a report. Never publish a .env file, token, or password.