Teramont Logo
Wings 1.12.1 fixes Hytale re-auth with persistent machine-id
Volver al blogEste contenido está disponible en español

Wings 1.12.1 fixes Hytale re-auth with persistent machine-id

Mizael Segovia

1/17/2026 ·Mizael Segovia· 3 min de lectura ·

387 visualizaciones

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-id for 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”.

systemctl stop wings

Step 2 Download the latest binary and set permissions

Before the command: this pulls the correct binary for amd64 vs arm64 automatically.

CTA Pattern

20% discount on VPS plans!

Get 20% off all our VPS plans.

Get 20% off
curl -L -o /usr/local/bin/wings "https://github.com/pterodactyl/wings/releases/latest/download/wings_linux_$([[ "$(uname -m)" == "x86_64" ]] && echo "amd64" || echo "arm64")"
chmod u+x /usr/local/bin/wings

Step 3 Restart Wings

After this, open connections should recover automatically per the docs.

systemctl restart wings

What you should see after upgrading

  • Restart a Hytale server container and it should no longer require re-authentication every time.

  • Your auth token/state should persist thanks to the now-stable machine identifier behavior tied to /etc/machine-id.

Conclusion

Wings 1.12.1 is a “tiny changelog, huge impact” release if you host Hytale on Pterodactyl. If you’re on 1.12.0 and you’ve hit the restart → re-auth loop, this upgrade is the clean fix.

Wings 1.12.1 fixes Hytale re-auth with persistent machine-id
Generalwingspterodactylhytale1.12.1authenticationmachine-idlinuxcontainersdevopsupgrade
¿Te gustó este artículo?Compártelo:

Sobre el autor

Mizael Segovia

Mizael Segovia

CEO & Desarrollador Full Stack y DevOps en Teramont Host

CTA Pattern

¿Necesitas ayuda con tu servidor?

Nuestro equipo está listo para ayudarte con cualquier duda o problema que tengas.

Contáctenos
Wings 1.12.1 fixes Hytale re-auth with persistent machine-id | Teramont Host