Wings 1.12.1 fixes Hytale servers re-authentication after restarts
If you’re hosting Hytale on Pterodactyl and every server restart turned into “log in again”… Wings 1.12.1 is the small release that saves your sanity.
The core fix: Wings now adds a persistent mount for /etc/machine-id specifically to support Hytale servers, keeping the machine identifier consistent across container restarts. Result: the authentication token can persist instead of getting invalidated after every restart.
Official links
Changelog (Wings v1.12.1): https://github.com/pterodactyl/wings/releases/tag/v1.12.1
How to upgrade Wings: https://pterodactyl.io/wings/1.0/upgrading.html
What changed in Wings 1.12.1
In the v1.12.1 release notes, the main item is:
Added: a mount for
/etc/machine-idfor Hytale servers.
That’s it. No giant feature list. Just a surgical fix aimed at one very annoying real-world issue.
Why Hytale was forcing re-auth after every restart
Hytale dedicated servers require authentication to communicate with Hytale service APIs and to prevent abuse.
When the machine identity inside the container isn’t stable between restarts, auth state/tokens can stop matching what the server expects—so you get pushed back into re-auth flows.
Persisting /etc/machine-id makes that identifier stable across restarts, which is exactly what this Wings patch targets.
How to upgrade to Wings 1.12.1
The official upgrade guide keeps it simple: download the updated Wings binary into /usr/local/bin, stop Wings briefly, then restart it. It also notes that your running servers will not be affected.
Step 1 Stop Wings briefly
Before the command: you’re stopping the daemon, not “killing all containers”.
