Repository navigation
Atrium 1.11.5
Proxy setup fixed
If a reverse proxy or tunnel (Caddy, nginx, cloudflared) runs on the same machine as Docker, check your .env. Earlier guides said TRUST_PROXY=loopback for that setup. With Docker it has no effect: the proxy reaches the app through Docker's bridge (a 172.x address), so every visitor still shared one set of sign-in and sign-up limits. Use this instead, then run docker compose up -d:
APP_BIND=127.0.0.1
TRUST_PROXY=172.16.0.0/12APP_BIND=127.0.0.1 is new. It opens the app's port on this machine only, so nobody can get around your proxy, and that is what makes trusting the bridge range safe. Without APP_BIND the port stays open to every network, as before.
To check it, sign in through your domain and run docker compose logs app | grep remoteAddress | tail -3. Your own address should show, not 172.x. The install guide has a new section, "Behind a reverse proxy or tunnel", covering a proxy on the host, a proxy container and npm start.
Also
- Tests for accepting invitations on a server without email, and for fake
X-Forwarded-Forheaders being ignored when no proxy is trusted. - SECURITY.md now explains that
ALLOW_PRIVATE_URLSis on by default and who that affects. It also says the server keeps running after an unexpected error, and that the logs are where to look. - Android: exporting and printing don't work in the app yet. The install guide now says so; use the phone's browser for them.
- Roadmap: the planned API and Claude (MCP) additions are listed in
docs/ROADMAP.md.
Downloads
- Windows:
Atrium-Windows-setup.exe(installed apps update themselves) - Android:
Atrium.apk