Pterodactyl Daemons

Pterodactyl Wings is the server-side engine of the Pterodactyl game server management platform, launching and supervising each game server inside its own…

  • Other
  • Tools & Utilities
Pterodactyl Wings is the server-side engine of the Pterodactyl game server management platform, launching and supervising each game server inside its own isolated Docker container. It exposes the API and container controls that the Pterodactyl Panel uses to give users a self-service web interface for deploying and running game servers, and is aimed at homelab operators who want to host multiple game servers with per-server isolation.

Platform availability

Available on 3 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

22/100 Low

Maintained
0GitHub repository no longer exists
Popular
No data
Easy to install
452 install platforms, install notes, Docker image
Light to run
502 GB minimum RAM

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 9 days ago

No GitHub repository data collected yet.

Checked 54 days ago - source: GitHub (BigBearTechWorld/pterodactyl-wings)

Resources & Compatibility

Minimum requirements: 2 GB RAM, 2 CPU core(s), 20 GB disk.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set the Wings API address and port In the Wings YAML settings file (a simple text settings file), set api.host and api.port to the network address and port the Panel can reach, often 0.0.0.0 and 8080. If this numbered door is closed or wrong, game servers will not install, start, or stop. source
  • Point SSL to real certificate files If you turn on api.ssl.enabled (secure HTTPS connection), point cert and key to the actual certificate and key file paths. Wrong paths can stop the secure API from working, so the Panel cannot talk to Wings. source
  • List trusted Proxy addresses If the Panel connects through a reverse proxy (a front-end that forwards web traffic) or from another machine, add that address to trusted_proxies. Without a trusted address, Wings may reject Panel requests that arrive through the proxy. source

Fetched 54 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can the Pterodactyl Panel and Wings be installed on the same machine?

Some self-hosters install both on the same machine when they only have one server, but the thread notes this is not recommended.

Which Wings YAML settings are easy to get wrong when connecting the Panel?

Set api.host and api.port to a reachable address and port, often 0.0.0.0 and 8080. If HTTPS is enabled, point cert and key to real certificate files. If traffic goes through a proxy or another machine, add that address to trusted_proxies.

What kinds of Pterodactyl Panel errors are commonly troubleshooted?

The guide covers diagnosing 502 Bad Gateway errors, Wings connection failures, database migration issues, and permission problems.

Answers sourced from github.com, guide.astroworldmc.com, www.reddit.com

Community

Collected 54 days ago - public community threads