WemXServer Connections
Connect WemX to the platforms that provision your services, such as Pterodactyl, Proxmox or cPanel, and keep an eye on their health.
A server extension teaches WemX how to talk to a platform: how to create, suspend, unsuspend and terminate a service there. A server connection is one configured instance of that extension, with its own URL and credentials.
You can have many connections for the same extension, for example one Pterodactyl panel per region. Every package points at exactly one connection.
Server extension (Pterodactyl)
├── Connection "EU Panel" ── packages: Minecraft EU 4GB, Minecraft EU 8GB
└── Connection "US Panel" ── packages: Minecraft US 4GB1. Install the server extension
WemX ships with the Universal Server Module, which provisions nothing. Use it for products that are delivered manually or need no automation.
For other platforms, install an extension from Admin → Marketplace (for example Pterodactyl, Proxmox VE or cPanel). Installed server extensions are listed under Admin → Servers → Installed Servers.
2. Create a connection
Go to Admin → Servers → Server Connections → Create and choose the server extension. The form then shows the fields that extension needs, typically the panel URL and an API key.
| Field | Description |
|---|---|
| Alias | An internal name, for example EU Panel. Shown when you pick a server for a package. |
| Description | Optional internal notes. |
| Extension fields | URL, API key and similar. They're stored encrypted. |
| Prevent Purchasing | When the connection is unhealthy, stop customers adding its packages to the cart, and remove them from existing carts. |
| Connection Alerts | Email an address you choose when the connection goes down, and again when it recovers. |
Click Test Connection to check the credentials and save. If the test fails, the error is shown and the connection isn't saved. Skip Test Connection saves it anyway, which is useful if the platform is temporarily down, but a bad configuration will then cause failed orders.
Your license plan may limit the number of server connections.
3. Configure packages on the connection
Each package on this connection has a Server tab with the extension's package-level settings, such as the plan, egg, node, disk or memory. Some of these can be offered to customers as configurable options.
Health monitoring
Every five minutes the scheduler tests every active connection that supports testing:
- A successful test marks the connection healthy.
- A failed test marks it unavailable, sends an alert if alerts are enabled, and, if Prevent Purchasing is on, stops new purchases on that connection until it recovers.
What the extension does for each order
| Event | What WemX calls on the extension |
|---|---|
| Order paid | Create: provisions the service, and usually creates a panel account for the customer |
| Due date passed + suspension period | Suspend |
| Unsuspended by staff | Unsuspend |
| Due date passed + termination period, or terminated by staff | Terminate |
| Staff upgrade/downgrade (if supported) | Upgrade/downgrade to the new package's resources |
| Customer changes their panel password (if supported) | Change password |
All of these run as background jobs on the queue. If one fails, the order is marked failed (for creation) or the error is recorded in the order's Incident logs tab, where staff can retry it once the cause is fixed.
Login details that an extension creates on the remote platform, such as a panel username and password, are stored encrypted and shown to the customer on their order page.