Repository navigation
Releases
v0.14.1
Minecraft version updates now have to be earned: a newer version is only offered when every mod on
the server has a build for it. Closes #52.
Added
- Version compatibility for modded servers (#52). Each server has a new Versions tab under
Mods: the version it runs now, the highest version every installed mod has a build for, and a
collapsible row per future Minecraft version showing how many mods are ready and how many have
nothing published yet. Open a row to see exactly which mods would be left behind. Press Check
Future Versions to run it. Nothing scans on its own, and a check saves its progress as it goes,
so a refresh - or a panel restart - resumes where it stopped instead of starting over. Large packs
stay responsive: each version's mod list is fetched when you open it and rendered a page at a
time. Thanks @gleep52 for the report. - Undo a mod update. The build a mod was updated from stays in the shared library, so its row on
the Mods tab now offers Revert: it puts the previous build back from local files, with no
download, and stops offering the build you reverted away from until a newer one appears.
Version checks cover mods, not plugins: Hangar and SpigotMC publish no per-version build list to
check against, so a Paper server keeps the behaviour it has today and has no Versions tab. A mod
from GitHub Releases, Hangar or SpigotMC on a modded server is reported as "could not be checked"
rather than guessed at - which, like an unidentified jar, holds back the one-click update. Disabled
mods are not loaded by the server, so they never block a version.
Fixed
- A modded server is no longer told to update to a Minecraft version its mods cannot run (#52).
The version check compared a pinned version against the newest release in Mojang's manifest and
nothing else, so a 1.20.1 Forge server was offered 26.3 as if it were an upgrade. The offer is now
capped at what the server's last version check proved every mod supports, and when compatibility
cannot be established at all - no check yet, a check for a different version or loader, one that
never finished, or a jar neither Modrinth nor CurseForge recognises - nothing is offered. Applying
a version above that ceiling is refused and names the mods blocking it. Servers with no mods are
unaffected.
v0.14.0
Per-server permissions: decide what each operator or viewer may do on each server, or hide a
server from them entirely. Closes #43.
Added
- Per-server permissions (#43). Settings → Permissions shows every operator and viewer against
every server. Click a cell to pick what that user may do there: view, power, console, players,
content, backups, files, settings, delete. A role stays the default everywhere, so a viewer can be
given power and console on one server while staying read-only on the rest, and an operator can lose
delete on the server that matters. Turning everything off hides the server from that user
completely: it leaves their sidebar, dashboard, backups, schedules, activity, updates, modpacks,
live status, tasks, and blueprints, and a direct link, API call, or console socket answers "not
found". A reference below the grid opens each permission into what it allows, what it does not,
and the exact routes it unlocks. Existing installations are unchanged until an admin edits a cell.
Thanks @RandomGuy908 for the request.
Internal
- One module,
services/permissions.js, answers "may this user do X on server Y" for the API,
pages, WebSockets, map proxy, schedules, backups-by-id, blueprints, tasks, and world targets. A
structural test walks the live API and page router stacks and fails the build if a server-scoped
write route, sub-router mount, or page ships without a permission gate. - The
user_server_permissionstable from the very first migration is now in use; no schema change.
v0.13.2
Settings changed in the panel now survive a restart, and creating a server from a modpack works
again. Closes #39.
Fixed
- World Controls, the whitelist toggle and server.properties edits stick across restarts
(#39). The container image re-applies every environment-backed server.properties value on each
start, so a PvP or difficulty change, a whitelist toggle, or an edit in the Files editor was
silently reverted the next time the server came up. Whenever the panel edits a property directly
it now removes the matching environment variable and marks the server for a rebuild, so the
on-disk value wins. Values chosen in the wizard still apply at creation. Thanks @doubleangels. - Every property-backed setting is covered, not only PvP, difficulty and the message of the
day: hardcore, whitelist enforcement, query, proxy protection, network compression, native
transport, RCON broadcast, the watchdog tick limit, pause-when-empty, snooper and JMX all unlock
the same way when edited in the file. The "require resource pack" mapping was also wrong and
never unlocked. - Difficulty changes are written to server.properties as well as sent to the game, so the
file stays truthful for servers that read it on boot. - Turning the whitelist off or on while the server runs no longer undoes other edits.
Minecraft itself rewrites server.properties from the values it loaded at boot when the whitelist
is toggled, which wiped a PvP or difficulty change made moments earlier. The panel now restores
its own edits around that rewrite. - Creating a server from a modpack works again (#41). The pinned pack version was not handed
to the create step, so the pinning safety check rejected the new server before the pack was
applied; GTNH always hit it. Thanks @tomas-pecserke.
Internal
- Single-key server.properties writes (PvP, difficulty, whitelist) share one choke point,
setServerProperty(), next to the whole-filewriteServerProperties(). - The field catalog's property mappings are checked against a vendored copy of the image's own
property definitions, so a wrong or missing mapping fails the test suite.
v0.13.1
Two bug-fix rounds: the Settings page's dialogs work again, and the memory meter explains why a
server "uses" its whole heap with nobody on. Closes #37; #25 stays open for the reporter.
Fixed
- Add User, New Key and Sign-in Security work again on Settings (#37). Two JSON islands on
the page were HTML-escaped, so the firstJSON.parsethrew at load and every handler on the
page (user edit and delete, the API key dialog, the CurseForge key and localization saves) was
never registered. Shipped broken in 0.13.0. - The memory meter explains itself (#25). "RAM (Java heap)" is handed to Java as both the
starting and the maximum heap, and Java fills a heap it was given up front within the first
minute of world generation, whether or not Aikar's or MeowIce's flags are on (measured: a 2 GB
heap reads 2.6 GB either way; the presets only make it instantaneous). A 12 GB heap therefore
reads as 12 GB with nobody playing, which looked like a leak. The Overview and Monitoring meters
now mark where the heap sits under the container limit and say what the number means, the
server card says it on hover, and the field help for RAM, Initial heap and the two flag presets
tells you before you choose. The lever that actually lowers idle memory, a smaller Initial
heap, is now explained where it lives (512 MB on that 2 GB heap: 1.4 GB idle with Aikar's
flags, 1.25 GB without). - Initial heap / Maximum heap actually apply. Both advanced fields stored the bare number
you typed, which Java reads as bytes;INIT_MEMORY=4096became-Xms4096and the server could
not start. Bare numbers in size fields are now sent to the image as megabytes. - README and the servers guide carry the measured numbers and the headroom guidance (at least
2 GB above the heap for a modpack; hypervisor dashboards can count disk cache and VM overhead,
the panel does not).
Internal
- Template JSON embeds go through two helpers named for their destination,
jsonScript(inside
<script>text) andjsonAttr(inside adata-*attribute), so the brace count can no longer
break a page; a test scans every template for a helper in the wrong context and renders the
affected pages with awkward server names.
v0.13.0
A large community release: a public read-only API, a live monitoring dashboard, world
shrinking, per-update "ignore", admin-configurable server defaults, backup renaming, a
mobile-first pass over every page, and a long list of audit-driven fixes. Closes #21, #23,
#27, #28, #29, #30, #31, #32.
Before you upgrade
TRUST_PROXY=trueis deprecated. It trusts an attacker-suppliedX-Forwarded-For, which
defeats the per-IP login lockout and the rate limiters. It still boots for now (treated as
TRUST_PROXY=1, with a warning in the log) but will be refused in a later release: set the
proxy hop count (1) or the proxy's IP/CIDR list instead.COOKIE_SECURE=autoneedsTRUST_PROXY. Set alone, the panel cannot see the proxy's
HTTPS hop and the session cookie ships without the Secure flag. The panel now warns loudly at
boot; a later release will refuse to start like this.SENTRY_ENABLE_LOGSno longer exists (it never did anything with the dormant Sentry seam).- Database migrations were renumbered so every file has a unique prefix (the old
010-015
duplicates are now011-025). Existing panels are migrated transparently; nothing re-runs. - The Docker image and the GitHub Release are now published by the same CI workflow that runs
the gates, and only after they pass. The required status check onmainis stillquality.
Added
- Public read-only API (
GET /api/v1/servers,GET /api/v1/servers/:id) behind
admin-minted Bearer tokens: scopable to a subset of servers, revocable, optionally
time-limited, rate-limited per token and per IP, off by default. See
docs/public-api.md. - Monitoring → Live dashboard: TPS/MSPT (Paper, Purpur, spark, Forge/NeoForge), a Health &
Stability card with 24 h / 7 d crash counts, per-world sizes and host disk free; plus a
combined live resource overview and an at-a-glance status breakdown on the main dashboard. - Shrink World: remove chunks nobody has spent time in (configurable threshold and spawn
radius, real spawn read fromlevel.dat, every dimension includingDIM-1/DIM1/custom,
entities and points of interest dropped with the chunk), with a dry-run preview, an
optional stop-shrink-start round trip, and an opt-in on manual and scheduled backups. See
docs/world-shrink.md. - Ignore an update per mod, modpack, Docker image, Minecraft version, or loader build. An
ignored build stays out of the badge, the digest, and the automatic update policy until a
newer one appears. - Defaults for new servers (heap, container limit, CPUs, disk quota, warning thresholds)
are editable on Settings; the create wizard pre-fills from them. (#31) - Backup rename from the backup list; the archive and the record move together. (#32)
- Backup retention ceilings: an optional maximum age and maximum total size per server,
with per-server overrides; the newest backup is never pruned. - Delete Player: a full wipe of a player's roles, saved data, stats, advancements,
inventory snapshots and moderator notes, refused while they are online. - Check for Updates on Settings compares the panel version with the newest stable GitHub
release (never pre-releases) and links to it; it never modifies files. - World Controls now covers every vanilla boolean gamerule, reads them concurrently, and
reports a rejected command as a plain sentence. - Roster status distinguishes Online / Whitelisted / Joined / Banned, with a "join
blocked" hint when whitelist enforcement is on. (#29) - Custom zip uploads detect a loader already installed in a prepared server pack and pin
the container to it. (#30) - Console: a "Hide RCON noise" toggle (on by default, remembered per browser).
- Profile pictures: WebP, uploads up to 16 MB, a working cropper preview, decompression-bomb
and SVG-scrub guards, and orphaned files cleaned up on replace or removal. - Mods / datapacks: orphaned files on disk are adopted back into the panel by content hash or
an unambiguous name; broken icons and missing metadata are repaired lazily and nightly. - Mobile-first pass: every data table stacks into cards on narrow screens, toolbars and grids
collapse, touch targets have a real minimum size, and the per-server navigation is regrouped
(Console, Mods, Monitoring, Discord / Status Page / Invites / Chatbot). Old deep links
redirect.
Fixed
- Auto-restart after a crash fires again on Docker daemons that report the event kind as
Actioninstead ofstatus. Unrequested clean exits (an in-game/stop, a consolestop,
the image's own auto-stop, a host shutdown) stay "stopped" and are never fought by the
watcher; a crash inside a stop/restart window is still recorded as a crash. (#23) - Delete Server keeps its files and backups by default, and the confirmation says exactly
what it does. (#21) ONLINE_MODEdefaults to on in Advanced Settings and the wizard, matching the image. (#27)- A numeric
0in Advanced Settings is a real value, not "unset"; cleared CPU / quota inputs
no longer silently become0. (#28) - Offline (file-mode) inventory edits work again.
- The Shrink World preview works on a running server, as the dialog promises; only a real
shrink requires the server to be stopped. - Installing a mod with "ignore version" prefers a build for the server's own loader; it no
longer hands a Fabric server the newest NeoForge jar. - A malformed zip (a path that escapes the archive, unsupported entries) is refused with a
clear message instead of a generic server error, on every upload path. - An invalid cron expression on a new schedule is refused with a clear message instead of a
generic server error. - A stalled Docker daemon can no longer hang a panel request forever: every
docker exec
(RCON commands, live probes) gives up at its deadline, including creating the exec itself. - A stopped server's console no longer replays its last lines every few seconds.
- Auth: the setup PIN locks out one address after a handful of wrong tries and everyone after
ten, with a fresh counter after each window; the acting admin re-enters their password to
change any password; other sessions are revoked when 2FA is enabled; the public API's
pre-auth rate limit is keyed per IP so rotating bogus tokens cannot bypass it. - Docker events buffer is capped with exponential reconnect backoff; Mojang lookups are
single-flight; directory sizing no longer follows symlinks; the crash watcher and the storage
indexer skip redundant work. - Daily maintenance prunes event history (365 days) and stale API-cache rows (30 days) in
bounded windows, and the panel-database snapshot runs in a worker thread. - Performance indexes for the Activity / History pages, the dashboard crash badge, and the
player-event prune (migration 025).
v0.12.0
An update-safety release: the last unpinned-modpack path is gone, and the per-server update
policy finally does what it says - including a real, guarded auto-update mode. (#22, #24)
Added
- The update policy is now real. Manual only excludes the server from the update badge, the
Updates page, and the daily check's notifications entirely - the true "never touch my versions"
mode. Auto-update applies pending pack updates after the scheduled daily check through the
same guarded path as a manual upgrade: pre-update backup, first-boot health monitoring, and an
automatic rollback when the new version fails to come up. Updates that would change the
server's Minecraft version are always skipped with an event - world conversion stays a human
decision. The manual "check now" buttons never trigger auto-updates. Previously all three
options were stored but changed nothing. - The README now points to the new community Discord (support forum, showcase, dev corner).
Fixed
- No more silent modpack self-updates. Servers created before 0.9.7 (or with hand-edited env)
could carry a pack selector with no version pin, making the container image download the newest
pack version on every start - the failure mode behind lost worlds in #21/#22. A boot sweep now
pins every such server to the version that is actually installed (from the panel's own record
or the image's install manifest, with the pack slug cross-checked - never a freshly resolved
"latest"), backfills the panel's pack record so these servers join the guarded upgrade flow, and
flags the container for recreate. Servers with no readable evidence get a prominent Settings
warning with a manual version picker instead of a guess. - Every path that writes server env (create, config update, blueprint import) now rejects an
unpinned pack selector outright, so the state can't come back. - The settings-page policy radios and the modpacks doc now describe the actual behavior of each
option.
v0.11.0
A content-sources release: three new keyless registries, server-side .mrpack import,
checksum-verified downloads everywhere, mclo.gs crash analysis, and a batch of compatibility
fixes (Quilt↔Fabric, PaperMC's new Fill v3 API).
Added
- Hangar (PaperMC's plugin registry), SpigotMC (via Spiget's
/download/proxyCDN
endpoint, which avoids the Cloudflare wall), and GitHub Releases as first-class content
sources - all keyless. They appear as chips in the plugin search modal, work in add-by-link, and
are covered by the update checker and the one-click updater. GitHub responses are cached with
ETag/If-None-Matchrevalidation (304s don't count against the rate limit) and an optional
GITHUB_TOKENenv var raises the quota; off-site SpigotMC resources get the same
browser-download + upload-jar fallback as CurseForge's distribution-denied mods. - Universal add-by-link: the Add-by-URL box now accepts Modrinth/CurseForge/Hangar/SpigotMC
project pages, GitHub repo/release URLs (bareowner/repotoo, with SpigotMC'sname.12345id
form recognized in URLs), Modrinth slugs, and direct.jarURLs. - Server-side Modrinth modpack (
.mrpack) import: the zip digester detects
modrinth.index.jsonas a third shape next to CurseForge exports and jar zips. Files are
canonicalized back into Modrinth projects via the sha1 reverse lookup (keeping real provenance,
icons, and update-checkability), verified against the pack's sha512 checksums while downloading,
and previewed with fit verdicts; client-only and non-mod entries are surfaced instead of
silently dropped;overrides/andserver-overrides/apply in spec order (server wins) with
the usual pre-apply backups. The wizard's create-from-zip flow accepts.mrpacktoo and
prefills loader, MC version, and loader build from the pack's dependencies. - Checksum-verified downloads: every registry install streams through the strongest digest the
registry publishes (sha512 → sha256 → sha1 → md5; CurseForge's numeric algo codes handled) and a
mismatch aborts the install before anything reaches the server. - mclo.gs crash sharing + insights: crash-report cards gain Share to mclo.gs (publishes the
report as a public paste behind an explicit confirm; the link is remembered so nothing uploads
twice) and Analyze (mclo.gs's automated analysis - known problems with suggested fixes -
rendered in a modal).
Fixed
- Quilt servers now see fabric-tagged builds in search, version pickers, update checks, and
zip-import verdicts (Quilt runs Fabric mods; most projects only tag "fabric") - previously the
Quilt catalog was nearly empty. - Paper build lists migrated to PaperMC's Fill v3 API - the legacy
api.papermc.io/v2
endpoint stopped receiving new versions and 404s for Minecraft releases above 1.21.11, which
silently emptied the Paper build picker for new versions. Fill's
STABLE/RECOMMENDED/ALPHA/BETAchannels map onto itzg'sdefault/experimental
PAPER_CHANNELvocabulary. - Modrinth rate limits on bulk sweeps (the update checker) now wait out short reset windows
and retry once instead of failing the run on the first 429.
v0.10.0
A large operability release: structured logging, rate limiting, a dedicated at-rest encryption key,
reliability work across the backup and lifecycle paths, a client-side avatar cropper, and a
project-wide copy pass. It also folds in the npm→pnpm migration and a round of dependency major
bumps. Two behaviour changes below need a note before you upgrade.
Upgrade notes
- At-rest encryption moved to a dedicated key. Stored credentials (API keys, RCON passwords,
TOTP secrets, the Discord webhook URL) are now encrypted with a random key at
$DATA_DIR/.secret-key, generated automatically on first boot, independent of
SESSION_SECRET. Values written under the oldSESSION_SECRET-derived key still open (it's
kept as a decrypt-only fallback) and are re-encrypted under the dedicated key automatically on the
next boot. Back up.secret-keywith the rest ofdata/- losing it means re-entering every
stored credential. A.secret-keyfile that exists but doesn't parse is now a hard boot error
rather than being silently regenerated. - Session cookie
SameSitedefault is nowlax(wasstrict), configurable via
COOKIE_SAMESITE. This fixes "remember me" appearing to log users out after following a link
from another site. State-changing requests are stillOrigin-checked; withCOOKIE_SAMESITE=none
the panel additionally rejects writes that carry noOrigin/Referer.
Added
- Structured logging (Pino). Every module logs through
src/logger.js; one JSON line per
request; a secret-redacting sanitizer;makeFailureThrottle()for background loops; a dormant
Sentry seam (src/instrument.js). New env:LOG_LEVEL,LOG_PRETTY,MSM_EXIT_ON_FATAL
(hard-exit on an uncaught fault, for supervised deployments), and an inertSENTRY_DSNblock. - Rate limiting.
express-rate-limiton all of/api(RATE_LIMIT_API_PER_MIN, default 1200)
and on login / 2FA / setup POSTs (RATE_LIMIT_AUTH_PER_15MIN, default 100);0disables a
limiter. Plus an account-global soft login counter alongside the existing per-IP one. - Health & monitoring endpoints.
GET /healthz(unauthenticated liveness; checks the DB;
deliberately returns no version) andGET /api/status/summary(authenticated: current problems,
recent alerts, disk free) for operators and external monitors. The containerHEALTHCHECKnow
hits/healthz. - Discord "Alerts" category. OOM, unhealthy, stalled boot, stop-failed, failed schedule, quota
stop, offline-after-restart, crash loop, crash report, and update-failed are forwarded under a new
toggleable category (on by default). See the new integrations guide. - Automatic daily backups + panel-DB snapshots. Every new server is seeded a daily backup
schedule on create (staggered 02:00–05:59). The panel's own database is snapshotted via
VACUUM INTOtodata/backups/_panel/on a daily timer (newest 14 kept), and an
integrity_checkpragma runs on boot. - Avatar cropper. Custom profile-picture uploads now pass through a client-side square-crop
step (drag / corner-resize) before upload; oversized rasters are downscaled before the crop UI so
a large photo can't OOM a mobile browser. - Explicit container healthcheck (
mc-health) sodocker inspect"healthy" means the server
accepts players, not just that the process started. - Update checking extended to Docker-image staleness and, for servers with no managed pack,
explicit Minecraft-version / loader-build pins (Paper/Forge/etc.). - esbuild client bundle.
pnpm run buildnow also producespublic/dist/js/; the app serves it
when present and raw source otherwise. - New docs:
docs/integrations.md; refreshed backups / architecture / updates / getting-started
/ users-and-roles / 2FA guides and the README env table. - Import zip on the Mods tab - one button, two zip shapes, auto-detected. A CurseForge
modpack export (manifest.json) is resolved through the CurseForge bulk endpoints (two POSTs
instead of ~170 GETs for an 87-mod pack), previewed with per-mod warnings, and installed as
custom mods with real task progress. A hand-assembled zip of jars gets each jar identified
(Modrinth sha1 lookup, then CurseForge fingerprint, then the jar's own metadata) and judged
against the server: fits / wrong loader / wrong MC version / already installed / unidentified. - Pack overrides, opt-in and reversible - a modpack export's
overrides/tree can be applied to
the server; every file that would be overwritten is backed up first to.import-backups/<timestamp>/
inside the server folder. Zip-slip-guarded, size-capped, and the backup tree itself is protected. - Create a server from a zip - the wizard's From-modpack tab takes a custom zip: the manifest
(or a majority vote across identified jars) prefills the loader and Minecraft version, then create,
bulk install, optional overrides, and start run as one task. Zips of plugins create Paper servers. - CurseForge search on the existing-server Mods tab - platform chips (Modrinth default,
CurseForge once the API key is stored), with Installed badges on results already on the server. - Blocked downloads handled up front - when a CurseForge author forbids API downloads, the
search modal swaps Install for Open CurseForge + Upload jar, and zip imports partition
those mods into a report with per-mod browser links and upload slots. - Datapack support on the Mods tab and an opt-in override for Modrinth's MC-version
compatibility filter, so a build not listed for this exact version or loader can still be
installed with a clear "not verified" warning. - Solver goes cross-platform - the Auto-detect compatibility solver accepts CurseForge mods
alongside Modrinth ones, mapping each CF project's file history into the same loader and
MC-version intersection. - Per-server OpenAI-compatible chatbot - admins can connect each Minecraft server to its own
Ollama or OpenAI-compatible endpoint and configure the model, invocation name (@wizardby
default), persona, join greeting, timed check-in, opt-in conversation window, and transcript
retention. Vanilla recipe questions use versioned game data and compact 2x2/3x3 chat grids. - Optional chatbot powers - Basic users may receive enabled self/world powers; separately named
Power controllers may affect another exact online player. Gifts, healing, feeding, spawn/time/
weather changes, and directional teleports are individually configurable and audited. Powers
start disabled and in dry-run mode; configuration and transcripts are admin-only; API keys are
encrypted at rest; LAN endpoints are accepted while link-local and metadata targets stay blocked.
The model never receives raw RCON: it can select only intent-matched structured tools whose
authorization, target, item, quantity, cooldown, and dry-run policy are validated again right
before execution; selectors are rejected, cross-player targets must be online and cannot be the
caller, and models without tool calling fall back to conversation only.
Changed
- Package manager: npm → pnpm throughout (scripts, CI, Dockerfile, docs).
- Dependency majors: express 5, zod 4, multer 2, dockerode 5 (closes a uuid buffer-bounds
advisory), plus croner / dotenv / js-yaml / express-handlebars / marked and the dev toolchain
(eslint 10, typescript 7, @types/node 26). Node ≥ 24 is now required. - Backup retention is capped per reason (scheduled 10, pre-update 10, manual 20) and restore /
world-reset safety snapshots get their ownpre-restorebucket (keep 5) so they can never evict a
manualbackup you deliberately kept. Each new archive is integrity-checked before it's recorded. - Project-wide copy pass: one house style for casing, punctuation, and error messages; a shared
friendlyError()replaces raw "Request failed (500)" / Zod jargon / leaked container ids. - Performance: prepared-statement cache in the DB layer; the per-page sidebar view models no
longer fan out per-server pack/update/crash lookups; the WebSocket console stream is brokered (one
docker logs --followper server, not per tab); static-asset caching; backup zipping moved to a
worker_threadsworker; async bcrypt on the login path; memoized analytics reports. - First-run
/setupon a non-loopback bind is PIN-gated (PIN printed to the console). - Side-effecting GETs (event export, world download,
.mrpack) are gated to admin/operator. - Windows-authored zips whose entry names use backslash separators are now rejected on
import/restore (a containment tightening in the consolidated extractor).
Fixed / Security
- Logging/secrets:
pino-prettymoved to runtime dependencies (a pruned prod install could
crash at boot); the log sanitizer now redacts webhook tokens that live in a URL path and no longer
over-redacts keys likesessionId; one throwing getter no longer discards a whole log line; the
access log records aborted requests and never 500s on a craftedX-Request-Id. - Console broker: a broker is now torn down when its upstream stream ends, so a tab that
connects afterwards starts a fresh follow instead of getting a stuck, stale stream; one slow
client is dropped rather than freezing the console for every other viewer. - Backups/lifecycle: the status-refresh overlap guard can no longer wedge permanently on a hung
Docker call; boot crash-recovery respects crash-loop backoff and no longer emits a false
"not auto-started" alert for a server it then auto-starts; the "server up" check reads only the
current boot's logs, not a reused container's previous run; the crash-loop counter only counts
crashes that actually armed a restart. - Discord bridge: a transient webhook failure retries the event instead of dropping it (bounded,
so a dead webhook can't wedge th...
v0.9.8
Account security lands: opt-in two-factor authentication for every account, plus a round of
security hardening across the file manager, the SSRF guard, the chat-command gate, and the map
proxy. Both are community contributions from @doubleangels, each reviewed and runtime-tested
(including a full upgrade of a populated 0.9.7 install) before merge. New documentation
ships alongside.
Added
- Two-factor authentication (TOTP). Any account — admin, operator, or viewer — can protect its
login with a standard authenticator app (Google Authenticator, Authy, 1Password, and the like).
Enroll by scanning a QR code (or entering the key by hand) and confirming a code plus your
password; you're given ten one-time backup codes for when your phone isn't around. Signing in
gains a second step that asks for the code, and the half-finished session is never treated as
authenticated until it's passed. Manage or turn off 2FA from the account menu (password required),
and admins can reset another user's 2FA from Settings → Users for the lost-device case. See the
two-factor authentication guide. - A documentation site under
docs/— a main index linking to focused,
screenshotted guides for the dashboard, servers, console & chat commands, modpacks, worlds & files,
backups, blueprints, schedules, storage, updates, activity, users & roles, and 2FA.
Fixed / Security
- File-manager path containment now covers symlinks. Every file operation already refused
..
traversal and absolute paths; it now also rejects symlinks that resolve outside a server's data
directory — including dangling links to a not-yet-existing target — so a mod or plugin can't plant
a link to read or write elsewhere on the host. - SSRF guard hardened. Server-side fetches of user-supplied URLs (mod and icon downloads) now
block additional IPv4-mapped IPv6 spellings of internal addresses (leading-zero groups and the
embedded dotted-quad form) that previously slipped through to loopback and cloud-metadata, while
still allowing ordinary public domains. - Chat-command gate tightened. Dangerous console commands (
stop,op,ban, …) are blocked on
low-permission triggers even when nested inside anexecute … run …chain, without wrongly
blocking ordinary chat text that merely mentions those words. - Map proxy no longer forwards your session. The BlueMap proxy strips the panel session cookie
and any authorization header before forwarding, so it can't leak to a target reachable by other
containers on a shared Docker network. - Fixed the account-menu Sign out button doing nothing when its click raced the menu closing.
v0.9.7
Two community contributions, both runtime-tested against live servers before merge: GT New
Horizons becomes a first-class modpack platform (thanks @pharomwinters), and the server-status
pipeline learns every known /list phrasing plus a set of live-cache hardening fixes
(thanks @doubleangels).
Added
- GT New Horizons is now a first-class modpack. The creation wizard's "From modpack" tab has a
dedicated GTNH card: pick a pack version (stable by default, betas behind a toggle) and the panel
pins it, sizes the server for it, and installs it in one task. Pinning means restarts can never
silently upgrade the pack — the same rule every other modpack already followed. - GTNH servers pick their own Java. GTNH's release index states the highest Java each pack
version supports, so the panel runs 2.8.0+ on Java 25 and older releases on Java 21 or 17
automatically, instead of stranding a 1.7.10 pack on Java 8. Overriding the image tag by hand
still wins. - GTNH packs take part in update checks (respecting the channel they were pinned from), blueprint
export/import, and the guarded upgrade flow with pre-update backup and rollback. - GTNH pack changes pass Forge's world-migration auto-confirm flag (
-Dfml.queryResult=confirm,
the same one GTNH's own start scripts use), so upgrading a pack over an existing world no longer
blocks forever on a console prompt nothing can answer. The pre-update backup remains the safety
net.
Fixed
- Server cards no longer get stuck on a boot-phase label (e.g. "Finishing startup") when a
server's/listreply isn't parseable. The parser now knows all three known phrasings — vanilla
"N of a max of M", Paper 26.2's "N out of maximum M", and the 1.7.10-era "N/M" every GTNH server
speaks — and when none match but RCON answers cleanly, the card shows "Player count unavailable"
instead of a stale boot phase. - The two copies of the
/listregex (live cache and player service) are consolidated into one
shared parser, closing a live-save corruption hazard: an unparseable player list used to read as
"nobody online", which could let a player's.datfile be edited on disk while they were on the
server. - A container restart the live cache missed no longer keeps the previous boot's player list and
uptime as live data; all latched state resets when Docker's own start time changes. docker execcalls no longer pay an extra daemon round trip per command, and a command whose
output was already captured can no longer be reported as failed by a late inspect error.- Fresh GTNH installs actually install: the panel no longer sets
SKIP_GTNH_UPDATE_CHECK, which
told the image to skip the code path that downloads the pack in the first place and crash-looped
every new GTNH server on missing files. - Pack upgrades no longer time out at 10 minutes for GTNH, which downloads a ~1–2 GB server pack
and builds a several-hundred-mod world on first boot; it now gets 30 minutes before the upgrade
is treated as failed.