Velocity modern forwarding is proxy-WIDE. A backend that cannot verify the signed handshake does not degrade -- it rejects every login the proxy forwards. Until now the only backends that could verify it were the two images Felis builds itself (deploy/limbo, deploy/lobby), which read FELIS_FORWARDING_SECRET in their own entrypoints. An arbitrary Paper image a user brings does not, so it passed admission, started, reported Ready, and was UNJOINABLE. The platform's answer was to recommend the lobby image as a base for a user's own world (0018_recommended_images.sql), which was never a good base -- it carries the /menu plugin whose job is to TRANSFER a joining player away, the exact opposite of a server you mean to stay on. The fix configures forwarding from OUTSIDE the image instead of requiring it inside. The operator now injects a root `felis init-forwarding` initContainer into every user server; it writes the proxies.velocity block into config/paper-global.yml and forces online-mode=false in server.properties on the /data PVC before the main container starts. The image needs no forwarding logic of its own, so the joinable set stops being "images that self-configure forwarding" and becomes every Paper-family image the platform runs. buildStatefulSet gates the injection on the ABSENCE of the system-role label: the Felis-built system servers already consume the secret in their entrypoints and the login gate is a limbo, not Paper. It is also gated on a non-empty felis image name -- the operator Deployment passes its own image as FELIS_IMAGE, and an operator without it skips the injection rather than failing, because a cluster whose proxy is not in modern mode has nothing to configure. The init runs as root deliberately. The world volume's ownership comes from the storage provisioner and the main container runs as whatever UID its image declares, so root is the only UID that can reliably write these files; it then chmods them 0666/0777 so that non-root main container can rewrite them on boot. The privilege is bounded -- the init exits before the server container starts and the server container keeps its own UID. The alternative, an fsGroup on the pod, is noted in the code as the upgrade path if the init ever stops running as root. The writer merges rather than overwrites, both because Paper expands paper-global.yml to its full default tree on first boot and because the panel file editor may edit either file between boots. It sets proxies.velocity.* and the single online-mode key and leaves every other setting alone. It is a no-op on an empty secret, for the same reason the env var is optional: a proxy that is not in modern mode provisions no Secret, and wedging every server's init on a missing optional value would be worse than the status quo. felis-paper (deploy/paper) is the platform's plain-Paper expression of that base and 0019 seeds it recommended: same PAPER_JAR_URL the lobby build already resolves, no /menu plugin, no forwarding gate, and a correctly-escaped RCON channel so the console, the online-player list and permission commands work out of the box. 0018's row is left in place -- an admin who kept it can keep it; this only adds the better default beside it. Three fixes ride along, each of which the 1.8 path hit in practice. bootstrap pins ViaVersion's serverside-blockconnections off. ConnectionData.init() only builds its block-connection provider when Via's lowest supported protocol is below 1.13; under modern forwarding the Velocity injector reports 393, so init() returns early, blockConnectionProvider stays null, and the first 1.12.2->1.13 chunk rewrite dereferences it -- a 1.8 client takes an NPE on the first chunk it is sent and never finishes joining. Every call site is behind isServersideBlockConnections(), so switching it off skips all of them, at a cosmetic pre-1.13 cost: fences and glass panes stop drawing connected. ViaVersion ships the option ON, so a fresh install shipped that NPE. Seeding a file with this one key suffices -- Config#loadConfig parses the bundled default as the base map and merges the on-disk file over it, so every other option stays current across version bumps. The absence of "Loading block connection mappings" in the log is NOT evidence this worked: init() gates on the protocol version too, and that half fails on its own, so the line is missing either way. The config value is the only evidence, which is what the test asserts. The Velocity unit gains -Dfelis.legacy-forwarding.servers=legacy18. A protocol-47 backend sits behind ViaVersion, which strips modern forwarding's login-plugin-message when it down-translates the proxy->backend pipeline to 47 -- the packet is registered from 1.13 and has nowhere to go. Only the handshake address field survives Via, so the Felis fork forwards the named servers BungeeCord-style while every other backend keeps modern+secret untouched. v1 hardcodes the one legacy backend; rendering the list from the MinecraftServer CRs is the upgrade path. deploy/lobby's set_prop escapes the value before substituting it. The RCON password is operator-provisioned arbitrary bytes, and a '|', '\' or '&' in one corrupts a bare `sed s|...|...|` and silently kills the key -- taking the console, the online-player list and permission commands with it. deploy/paper was written with the escaping, so the lobby gets the same rather than leaving the sibling caller broken. Verified: the full Go suite passes on Windows and on Fedora 44 (go1.26.4), where TestWriteForwardingFileModes actually runs its POSIX mode assertions instead of skipping. The new tests cover the initContainer's image, root UID, world mount and secret env; the merge preserving unrelated config trees; the properties upsert including the commented-key case; and the bootstrap script both writing the Via key and still calling the function that writes it. Not verified: the initContainer has never run in a real cluster, and the felis-paper image is code-only here as the other game-stack images are -- no Go CI builds them. The ViaVersion pin is the one piece with live evidence, and that evidence is what it was written from. Before it, a client was cut within a second of "logged in with entity id" on legacy18 while the proxy logged the NPE above -- REMAP OF LEVEL_CHUNK chained into Protocol1_8To1_9's MAP_BULK_CHUNK. It was applied by hand to the running proxy on 2026-07-24 at 14:47 and only then written back into bootstrap. At 14:48:14 the same player joined real Paper 1.8.8 through the fork, issued commands, approved an op-login from in-game at 14:50:39, and held the connection until 15:30:09 -- 42 minutes. Neither session says which client version it was. The proxy never logged a protocol number. It bounds above at 1.16.4, from the viabackwards "(1.17->1.16.4) ... for 1.16 players and below" warning that fired for that player on the lobby leg, and no lower -- Via floors every handshake to the proxy's 393, so anything from 47 up is admissible. Reading Protocol1_8To1_9 in the stack as a client-version tell is backwards: that chain runs on the BACKEND leg, up-translating the 47 server's chunks to the floor. What the NPE proves is that the pin was load-bearing, not who was holding the mouse. That is one hand-run session on one host, and it is not a cell. The 393->47 leg has one now, in Felis-Legacy -- FL-009 puts a genuine protocol-47 client on a stock Paper 1.8.8 behind this proxy and flips this same option: on it, cut 0.2s after JoinGame with the fault above; off, holds. No automated test in THIS repository exercises the leg.
109 lines
5.1 KiB
Go
109 lines
5.1 KiB
Go
package felis
|
|
|
|
import (
|
|
"strings"
|
|
"testing"
|
|
)
|
|
|
|
// The lobby's LuckPerms wiring is a three-file contract with no compiler behind it:
|
|
// bootstrap.sh resolves a URL and passes it as a build-arg, the Dockerfile requires
|
|
// that exact arg name and writes the jar to a fixed path, and entrypoint.sh copies
|
|
// from that same path on every boot. A typo in any one of them is invisible until a
|
|
// lobby actually starts — and then `set -e` turns the failed cp into a crashloop on
|
|
// the always-on hub every authenticated player is transferred to.
|
|
//
|
|
// All three files ship inside the binary (gameStackAssets, bootstrapScript) for the
|
|
// TUI install path that has no source checkout, so reading them back here checks
|
|
// what is actually shipped rather than what is merely on disk.
|
|
func TestLobbyLuckPermsWiringIsConsistent(t *testing.T) {
|
|
dockerfile := readGameStackFile(t, "deploy/lobby/Dockerfile")
|
|
entrypoint := readGameStackFile(t, "deploy/lobby/entrypoint.sh")
|
|
script := BootstrapScript()
|
|
|
|
// The path is the contract. RUNTIME_DIR is /paper in the entrypoint, so the
|
|
// Dockerfile's download target and the boot-time copy source must be the same
|
|
// string; anything else fails at `cp`, not at build.
|
|
const jarPath = "/paper/plugins/LuckPerms.jar"
|
|
if !strings.Contains(dockerfile, "-o "+jarPath) {
|
|
t.Errorf("Dockerfile does not download LuckPerms to %s", jarPath)
|
|
}
|
|
if !strings.Contains(entrypoint, `cp -f "$RUNTIME_DIR/plugins/LuckPerms.jar"`) {
|
|
t.Error("entrypoint.sh does not refresh LuckPerms.jar from the image seed; " +
|
|
"a lobby would keep whatever stale jar the PVC happens to hold")
|
|
}
|
|
if !strings.Contains(entrypoint, `RUNTIME_DIR="/paper"`) {
|
|
t.Error(`RUNTIME_DIR is no longer "/paper", so the copy above no longer ` +
|
|
"resolves to the path the Dockerfile writes")
|
|
}
|
|
|
|
// The build-arg name has to agree across the two files that never see each other.
|
|
const arg = "LUCKPERMS_JAR_URL"
|
|
if !strings.Contains(dockerfile, "ARG "+arg) {
|
|
t.Errorf("Dockerfile declares no ARG %s", arg)
|
|
}
|
|
if !strings.Contains(script, "--build-arg "+arg+"=") {
|
|
t.Errorf("bootstrap.sh never passes --build-arg %s", arg)
|
|
}
|
|
if !strings.Contains(script, "LUCKPERMS_JAR_URL=\"$(luckperms_latest_jar)\"") {
|
|
t.Error("bootstrap.sh does not resolve the LuckPerms URL before building")
|
|
}
|
|
|
|
// bukkit-legacy targets Minecraft 1.8-1.12 and the other platforms are not
|
|
// loadable by Paper at all, so the resolver's grep must pin the /bukkit/ path
|
|
// segment — the metadata endpoint returns every platform's URL in one payload.
|
|
if !strings.Contains(script, "/bukkit/loader/") {
|
|
t.Error("luckperms_latest_jar does not pin the bukkit/loader path; it could " +
|
|
"return the fabric, forge or velocity jar, none of which Paper can load")
|
|
}
|
|
|
|
// A missing jar must stop the build. The alternative — shipping a lobby that
|
|
// starts fine and answers every `lp` command from the panel's permission screen
|
|
// with "Unknown command" — is discovered in production.
|
|
if !strings.Contains(dockerfile, `if [ -z "${LUCKPERMS_JAR_URL:-}" ]`) {
|
|
t.Error("Dockerfile does not fail the build when LUCKPERMS_JAR_URL is unset")
|
|
}
|
|
}
|
|
|
|
// A 1.8 client joining a protocol-47 backend dies on the first chunk unless ViaVersion's
|
|
// serverside block-connection tracking is off: under modern forwarding the Velocity injector
|
|
// reports 1.13 as the lowest supported protocol, ConnectionData.init() returns early on that,
|
|
// and the 1.12.2->1.13 chunk rewrite then dereferences the provider init() never built.
|
|
//
|
|
// ViaVersion ships the option ON, so this is a correction bootstrap has to make rather than a
|
|
// default it can inherit — and nothing else in the install would notice it missing. The failure
|
|
// surfaces only when a legacy player joins, on a host that installed cleanly.
|
|
func TestBootstrapPinsViaBlockConnectionsOff(t *testing.T) {
|
|
// go:embed takes the working tree verbatim, and this repository pins no eol attribute, so
|
|
// a Windows checkout embeds CRLF. Only the assertion spanning a line break below cares.
|
|
script := strings.ReplaceAll(BootstrapScript(), "\r\n", "\n")
|
|
|
|
const key = "serverside-blockconnections"
|
|
if !strings.Contains(script, key+": false") {
|
|
t.Errorf("bootstrap.sh never writes %s: false; a fresh install inherits ViaVersion's "+
|
|
"default of true and NPEs the first 1.8 player to receive a chunk", key)
|
|
}
|
|
|
|
// Writing the value is only half of it: the file has to be the one ViaVersion reads.
|
|
// Via names its data directory after the plugin in lowercase.
|
|
if !strings.Contains(script, "plugins/viaversion") {
|
|
t.Error("bootstrap.sh does not target plugins/viaversion, so whatever it writes is " +
|
|
"not the config ViaVersion loads")
|
|
}
|
|
|
|
// Via staging and this correction have to stay welded together. If the call is dropped,
|
|
// every branch above still exists and still looks right in review.
|
|
if !strings.Contains(script, "pin_via_block_connections\n ok \"Via staged") {
|
|
t.Error("install_via_plugins no longer calls pin_via_block_connections; the jars would " +
|
|
"be staged with the option left at its default")
|
|
}
|
|
}
|
|
|
|
func readGameStackFile(t *testing.T, name string) string {
|
|
t.Helper()
|
|
b, err := gameStackAssets.ReadFile(name)
|
|
if err != nil {
|
|
t.Fatalf("read embedded %s: %v", name, err)
|
|
}
|
|
return string(b)
|
|
}
|