Updates
Raptor updates Wings on your nodes for you. Game servers keep running through every update: they belong to Docker, not to Wings.
How an update happens
Section titled “How an update happens”New releases go out in stages: a few nodes first, then a quarter, then everyone, with time to watch in between. A stage that goes badly is stopped before it reaches the rest.
On each node:
- Wings downloads the release and checks its signature against Raptor’s release key, built into Wings, and the file’s checksum. Anything that doesn’t check out isn’t run.
- The new version starts on trial, beside the old one.
- Once it’s healthy (its local API answering, Docker ready, and reconnected to the Panel) for 30 seconds, it takes over.
- If it crashes, hangs, or can’t reach the Panel within 5 minutes, it’s rolled back automatically, and the old version carries on.
The node’s Overview shows the Wings version, and alerts can tell you when a node updates or rolls back (Alerts).
Update by hand
Section titled “Update by hand”sudo raptor update -check # what it would installsudo raptor update # install the newest releasesudo raptor update -version v0.17.0raptor update follows the trial and prints the outcome. -version can go back to an older release, too.
Pin a version or turn updates off
Section titled “Pin a version or turn updates off”In /etc/raptor/config.yml on the machine:
updates: automatic: false # don't update from staged rollouts pin: "0.17.0" # or install this version and stay on it channel: stable # or beta, for pre-releasesRestart Wings after changing it (sudo systemctl restart raptor-wings; servers keep running). A pinned or non-automatic node is skipped by rollouts; raptor update still works by hand.
© 2026 Xena Studios. Pterodactyl is a trademark of its owners; Raptor isn't affiliated with it.