L4 0.3.2

L4 0.3.2

This release lets a Cloudflare Server keep Cloudflare access and update itself. Landing, Shell, installer, Server, portable runtime and Docs share 0.3.2. It stays on the server-v2 lineage with no new migrations, so a 0.3.x Server can update in place. Customer Servers update only when their operator chooses an update.

Servers update themselves

• Installing or updating through the official installer now offers Keep Cloudflare access on this Server, on by default. After the Server runs the new version, the installer hands its Cloudflare access to the Server and forgets it. For safety, run each Server in its own Cloudflare account; a free account is enough.
• Settings → Deployment → Updates shows that access, lets you disconnect it, or connect it with an API token from a pre-filled Cloudflare link.
• With that access, Back up and update runs on the Server itself: it verifies the release, backs up to the separate backup bucket and reads the backup back, uploads, and lets the new version confirm itself. You can close the page; Retry update resumes after the verified backup.
• After an update, Settings offers to load the new interface if your browser still shows the old one.
• The official installer remains available. Its update screen no longer spins before it starts or claims an upload that has not happened, and it retries release downloads that GitHub rate-limits.
• Release notes in Updates are formatted instead of shown as raw Markdown.

ChatGPT

• Pasting the sign-in address again now confirms a finished connection or shows the real reason it failed, instead of saying the attempt expired. After a failure the form asks for a fresh sign-in.

Update to this release

Update from Settings → Deployment → Updates as before and keep Keep Cloudflare access on this Server checked. Keep that tab open until it finishes; from the next release on, the Server updates from its own Settings.