[{"data":1,"prerenderedAt":18},["ShallowReactive",2],{"release:0.3.8":3},{"version":4,"title":5,"description":6,"date":7,"url":8,"markdownPath":9,"prerelease":10,"html":11,"newer":12,"older":15},"0.3.8","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…","2026-10-30","\u002Fchangelog\u002Fv0.3.8","\u002Fchangelog\u002Fv0.3.8.md",false,"\u003Cp>This release makes it easier to claim a self-hosted Server, especially on Coolify. Landing, Shell, installer, Server, portable runtime and Docs share \u003Cstrong>0.3.8\u003C\u002Fstrong>. It stays on the \u003Ccode>server-v2\u003C\u002Fcode> lineage and adds no migrations. Customer Servers update only when their operator chooses an update.\u003C\u002Fp>\n\u003Ch2 id=\"claim-a-self-hosted-server\">\u003Ca class=\"heading-anchor\" href=\"#claim-a-self-hosted-server\">Claim a self-hosted Server\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ccode>\u002Fsetup\u003C\u002Fcode> has a \u003Cstrong>Setup token\u003C\u002Fstrong> field. On Docker, Coolify or the VPS, open \u003Ccode>\u002Fsetup\u003C\u002Fcode> and paste \u003Ccode>SETUP_TOKEN\u003C\u002Fcode> (on Coolify, \u003Ccode>SERVICE_PASSWORD_64_SETUPTOKEN\u003C\u002Fcode>). You no longer have to build a \u003Ccode>\u002Fsetup#claim=…\u003C\u002Fcode> link by hand. A rejected token returns you to the field with the error. The links that the installers open still work.\u003C\u002Fli>\n\u003Cli>To skip the claim, set \u003Ccode>ADMIN_PASSWORD\u003C\u002Fcode> (at least 12 characters) before the first start. The Server creates the Owner with \u003Ccode>ADMIN_EMAIL\u003C\u002Fcode> 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 \u003Ccode>LLLL_ADMIN_PASSWORD\u003C\u002Fcode> and prints no claim link. Change the password after you sign in. Later changes to the variable have no effect.\u003C\u002Fli>\n\u003Cli>Container logs show the Server's address after start, and how to finish setup.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"coolify\">\u003Ca class=\"heading-anchor\" href=\"#coolify\">Coolify\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>If Coolify includes the container port in the generated URL, \u003Ccode>PUBLIC_ORIGIN\u003C\u002Fcode> no longer keeps \u003Ccode>:8080\u003C\u002Fcode>. Before, that port made sign-in and setup fail with "Origin mismatch".\u003C\u002Fli>\n\u003Cli>"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.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"sign-in-page\">\u003Ca class=\"heading-anchor\" href=\"#sign-in-page\">Sign-in page\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>The left side of the sign-in and setup pages shows only the Server's mark.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"update-to-this-release\">\u003Ca class=\"heading-anchor\" href=\"#update-to-this-release\">Update to this release\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cp>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 \u003Ccode>llll upgrade\u003C\u002Fcode>.\u003C\u002Fp>\n",{"title":13,"url":14},"L4 0.3.9","\u002Fchangelog\u002Fv0.3.9",{"title":16,"url":17},"L4 0.3.7","\u002Fchangelog\u002Fv0.3.7",1793335826897]