Pterodactyl & Wings

This page helps you connect Paymenter + Vortexus to Pterodactyl and Wings. You do not replace Pterodactyl: Vortexus talks to the panel you already run.

Quick definitions

Pterodactyl Panel — Web UI + API that manages servers, nodes, and eggs.
Wings — The agent on each node that actually runs Docker-based game servers.

Vortexus relies on your Pterodactyl install working normally before adding billing on top.

Before you rely on Vortexus for deployments: In Pterodactyl admin, create a test server by hand. If that fails, fix Pterodactyl first — Vortexus will not magically fix node or allocation problems underneath.

What Pterodactyl must already have

Panel URL reachable over HTTPS (recommended in production).
Application API credentials with permission to create/update servers (as your product design requires).
Nodes online; Wings reporting healthy.
Allocations (IP + port pools) assigned to nodes.
Eggs / nests configured for the games you sell.

If you are new to Pterodactyl, follow official Pterodactyl docs until panel + node + test server work.

Paymenter server extension

In Paymenter Admin → Extensions → Servers, configure your Pterodactyl extension (URL, API keys, defaults) as you would for any other integration. Vortexus uses that context when provisioning through marketplace purchases.

Treat API keys like passwords. Never paste them in public tickets or screenshots without redacting.

Wings: trust your Paymenter URL (browser console)

The in-browser game console uses Pterodactyl’s websocket flow. Wings checks Origin headers. You must add your Paymenter site URL (and admin URL, if different) to each node’s allowed_origins in /etc/pterodactyl/config.yml on the node.

Example shape (values must match your real domains and scheme):


allowed_origins:
  - https://billing.example.com
  - https://pay.example.com

After editing:


systemctl restart wings

Tips:

Include https vs http exactly as customers use it.
Add www and non-www if both are used.

Test before going live

Order or create a test service that uses Vortexus Web.
Open the embedded panel and try the console.
If the console stays blank or errors, re-check allowed_origins and browser devtools for websocket or CORS hints.

Common issues

Symptom	Likely cause
Provisioning fails with API error	Wrong API key, wrong panel URL, or missing permission on the Application key.
Console does not connect	Missing Paymenter domain in Wings `allowed_origins`; Wings not restarted.
“No free allocation”	No free ports on the node; expand the allocation pool in Pterodactyl.
Server creates but wrong egg/image	Map products/templates in Paymenter admin to the right Pterodactyl egg or Docker image.

Next step

Module packages — how Marketplace and Web fit together.
Usage — categories, templates, regions, and deploy flows.