{"headline":"StartOS 0.4.0.1","release-notes":{"0.3.4.1":"Various bugfixes","0.3.4.2":"* Update build system for Server Lite and NUC-based Server One\n* Rename embassyOS to StartOS\n* PWA support for StartOS web interface. You can now save StartOS to your phone as an app!\n* Various bugfixes","0.3.4.3":"* Improved Tor reliability\n* Experimental features tab\n  * Zram\n  * Manually reset tor\n* Multiple bugfixes and general performance enhancements\n* Update branding","0.3.4.4":" * Https over Tor for faster UI loading times\n* Change password through UI\n* Use IP address for Network Folder backups\n* Multiple bug fixes, performance enhancements, and other small features","0.3.5":"* This release contains significant under-the-hood improvements to performance and reliability\n* Ditch Docker, replace with Podman\n* Remove locking behavior from PatchDB and optimize\n* Boost efficiency of service manager\n* Require HTTPS on LAN, and improve setup flow for trusting Root CA\n* Better default privacy settings for Firefox kiosk mode\n* Eliminate memory leak from Javascript runtime\n* Other small bug fixes\n* Update license to MIT","0.3.5.1":"* Revert perpetual performance mode for quieter fan\n* Minor bug fixes","0.4.0.1":"StartOS 0.4.0 is a completely new operating system. This update replaces StartOS in place: it downloads ~3 GB, reboots your server, and migrates your services and data to the new format. It requires StartOS 0.3.5.1.\n\n**This is a major migration, not a routine update.** Complete every preparation step below before tapping \"Begin Update\". Skipping the service-update or backup steps can result in **permanent data loss**.\n\n**1. Review services that need special handling**\n\n- **Embassy Pages** — retired and replaced by **Start9 Pages**. Embassy Pages will survive the update but will no longer receive updates. Uninstall it, then after the update install Start9 Pages from the marketplace and re-add your content.\n- **Ghost** — completely redesigned for 0.4.0 and incompatible with the old version. Before updating, open your Ghost admin UI and use Ghost's built-in **Export** tool to download your content. After the update, install the new Ghost and use its **Import** tool to restore your content.\n- **Synapse** — the old Synapse was Tor-only; the new Synapse is clearnet-only. These are different services now, with no migration path.\n- **Jam** — Jam's backend (JoinMarket) is being replaced, and Jam is unavailable on 0.4.0 until its new backend matures. Back up your seed, move out any spendable funds (fidelity-bond funds stay locked until expiry), and uninstall Jam before updating.\n\n**2. Prepare for new service addresses**\n\nOn 0.4.0, each service no longer has its own `.local` address (e.g. `longexamplepublickey.local`); services are reached on unique ports of your server's main `.local` address (e.g. `adjective-noun.local:4545`). Your old per-service `.local` addresses will no longer exist after the update. If you use a password manager, give your saved passwords clear names now — not just the old `.local` URLs — so you can identify them later and save the new URLs.\n\n**3. Update ALL services**\n\nUpdate every installed service to its latest version, starting at the base of the dependency tree and working upward — Bitcoin before LND, LND before RTL. Bitcoin may safely remain at 28.x or 29.x, but you MUST update to the latest **minor** version of your selected major version. **This step is required:** services that are not on their latest version may fail to migrate, potentially requiring a rollback to 0.3.5.1 or losing data entirely.\n\n**4. (Recommended) Add an SSH key**\n\nIf you haven't already, add an SSH key to your server. If something goes wrong during the migration, SSH access makes it much easier to debug.\n\n**5. Uninstall services you don't use**\n\nEvery installed service must be migrated, and each adds to the total migration time. Uninstalling unused services now is much faster than migrating them; you can reinstall fresh on 0.4.0.\n\n**6. Stop all services**\n\nStop every remaining service and wait for each to fully stop, so no new data is written before your backup.\n\n**7. Create a full system backup**\n\nWith all services stopped, create a full system backup covering every service. **Do not skip this step.** Backups made on 0.3.5.1 cannot be restored onto 0.4.0 — this backup is your safety net for returning to 0.3.5.1 if the migration fails.\n\n**What to expect**\n\nAfter you begin, the update downloads (~3 GB), your server reboots, and the migration runs. It can take **hours**, depending on how much data you have — be patient, and do not power off or unplug your server.\n\n**Your browser will not show you 0.4.0 on its own.** Your server is unreachable for part of the restart, and your browser has this 0.3.5.1 interface cached — reloading this tab will keep showing you the old UI or a \"cannot connect\" error indefinitely, long after 0.4.0 is up and serving. So check on your server every few minutes by opening its address (the `.local` address you are using right now) in a **new private/incognito window** — a fresh window each time. That bypasses the cache, and is the reliable way to see whether your server is back: first an initialization screen with migration progress, then the 0.4.0 login page. Once a private window loads, bring your normal window over with a hard refresh (`ctrl+shift+R`; on macOS Firefox `cmd+shift+R`, on macOS Safari `cmd+option+E` then `cmd+R`) or by clearing your browser's cache.\n\nWhen the migration completes: sign in, update **all** of your services from the marketplace before doing anything else (the 0.4.0 versions are repackaged for the new system even when the app version looks the same), start them, and create a fresh backup.\n\nFull guide: https://docs.start9.com/start-os/update-040.html"},"version":"0.4.0.1"}