L4 0.3.8

This release makes it easier to claim a self-hosted Server, especially on Coolify. Landing, Shell, installer, Server, portable runtime and Docs share 0.3.8. It stays on the server-v2 lineage and adds no migrations. Customer Servers update only when their operator chooses an update.

Claim a self-hosted Server

• /setup has a Setup token field. On Docker, Coolify or the VPS, open /setup and paste SETUP_TOKEN (on Coolify, SERVICE_PASSWORD_64_SETUPTOKEN). You no longer have to build a /setup#claim=… link by hand. A rejected token returns you to the field with the error. The links that the installers open still work.
• To skip the claim, set ADMIN_PASSWORD (at least 12 characters) before the first start. The Server creates the Owner with ADMIN_EMAIL and that password, so you can sign in right away. In the Coolify template this is an optional variable. The VPS installer takes it as LLLL_ADMIN_PASSWORD and prints no claim link. Change the password after you sign in. Later changes to the variable have no effect.
• Container logs show the Server's address after start, and how to finish setup.

Coolify

• If Coolify includes the container port in the generated URL, PUBLIC_ORIGIN no longer keeps :8080. Before, that port made sign-in and setup fail with "Origin mismatch".
• "Origin mismatch" now names the page's address and the Server's address. If those two match, it says the reverse proxy changed the Host or scheme.

Sign-in page

• The left side of the sign-in and setup pages shows only the Server's mark.

Update to this release

A Cloudflare Server that keeps Cloudflare access updates from Server settings → Deployment → Updates by itself. A Docker Server updates by its image tag in Coolify or Docker Compose; the VPS installer uses llll upgrade.