v1.17.0 — servers that survive a reinstall, and a server.properties you can edit by hand

The v1.16.0 image never published. Its release build failed a security scan on Perl advisories in the base image, so latest stayed on v1.15.0. This release carries all of v1.16.0 plus four new changes. If you're on v1.15.0, see Before you upgrade below.

Reports from @odog1970, @IsXGeo, @bushibot and @excessnet drove all four. Thanks!

Servers survive a reinstall

When Palisade lost its database, after a reinstall or a power cut that corrupted it, the game containers it had created kept running and Palisade couldn't take them back. Unraid showed them as third-party containers. Now Adopt existing on the Servers page lists them with a "palisade server" badge. Adopting one brings it back under its old id, on its existing world and game files, without copying anything. The server's first start replaces the old container.

Every start now saves the server's settings, ports and mods next to its data, with passwords still encrypted, so a reattach restores those too. A server last started before v1.17.0 has no saved settings, so it comes back with defaults and you'll need to enter them again. Schedules, cluster membership and backup history live only in the database and don't come back.

Minecraft: hand edits to server.properties stick

The Minecraft image rewrites server.properties on every start from the values Palisade passes, so a hand edit to any of those keys was gone after a restart. A new Update server.properties on start setting on the Server tab turns that off. It's on by default, so existing servers behave as before.

With it off, edits you make in the panel to those fields stop reaching the file. server-port, rcon.port and rcon.password in the file still have to match the panel. If you set SKIP_SERVER_PROPERTIES as a workaround, you can remove it.

Enshrouded

• A server stuck on an old build after Update game now recovers on its next start. Images before mornedhels 1.8.0 could mark the latest build as installed when it wasn't, and every boot after that skipped the update. Palisade spots the mismatch and has the next boot re-check the game files. Saves aren't touched.
• Enshrouded 1.0 needs mornedhels 1.8.0 or later. Older Proton images crash on boot with No SteamUtils011. The default latest tag already points at 1.8.0 and a restart pulls it, so you only need to act if you set a custom Image tag.

Carried over from v1.16.0

The v1.16.0 notes have the details.

• A player-count condition on a schedule can require the count to hold for 1 to 60 minutes. A "stop when empty" schedule no longer stops a server nobody had time to join.
• A stop or start schedule skips a server already in that state instead of logging an error and sending a failure webhook.
• Conan Exiles: Update game installs the new build again, a half-filled PvP or raid schedule is refused at save, and a TARGET_MANIFEST_ID pin no longer updates the server on every boot.
• The "Update available" badge clears as soon as an updated server reaches Running.
• Production dependencies with advisories (proxy-addr, source-map-js, sharp) are pinned to patched releases.

Before you upgrade

Coming from v1.15.0, this release adds a database migration. Prisma only migrates forward, so rolling back to v1.15.0 needs a database backup from before the upgrade. Palisade snapshots its database nightly, under Settings → Backups.