Server Control Integration
ProConnect your game servers to Arkanis, whatever runs them. Pterodactyl and Pelican panels connect over their API; Windows and Linux machines connect over SSH. One panel controls all of them.
Open Server Control →
Start, stop and restart servers, browse and edit files, watch the console and read resource usage, without opening a hosting dashboard or handing out its login. Works with a Pterodactyl or Pelican panel and with a Windows or Linux machine you reach over SSH.
/server control in Discord and the Server Control page on the dashboard. You choose the provider when you add a connection, and the panel adapts to what that provider can do. Servers from different providers sit in the same list, so a community running one server on a panel and another on a machine of its own manages both from one place.What is this?
The connection layer underneath the Server Control panel. It holds the credentials for wherever your servers actually run, so the actions you reach for every day (start, stop, restart, browse files, read the console, check CPU and memory) show up as buttons in Discord and on the dashboard rather than in someone else's web interface.
Why you might want it
You don't want every staff member holding a hosting login or an SSH key, and you don't want to switch tabs every time a server hangs. Arkanis puts the routine power and file operations behind your existing permission system, and writes every action to the audit log with a name attached.
What this is for
Letting staff start, stop, restart, browse files and read the console on every game server you run, from Discord, without anyone holding hosting credentials.
Before you start
- ·Your guild is on the Pro tier.
- ·You know which provider each server uses: a Pterodactyl or Pelican panel, or a Windows or Linux machine you reach over SSH.
- ·For a panel: the panel URL and an API key. For a host: an SFTP connection already added, using the account that owns the server files.
- ·Staff who should use Server Control have its capabilities assigned to their role.
5-minute setup
- 1Open the dashboard → Server Control and click Add Connection.
- 2Pick your provider. The rest of the form changes to ask only for what that provider needs.
- 3Save, then click "Refresh servers". A panel imports every server its key can see; a host is one server and appears immediately.
- 4Open any server and check its resource readout. A CPU and memory figure means the connection works end to end.
- 5From Discord, run
/server controland pick Server Info to confirm the capability gate is happy.
Common failure modes
- "Authentication failed" on save (panel)API key wrong, copied with a leading space, or revoked. Mint a fresh key in your panel and paste it again. The key is shown only once, so paste straight from the panel.
- No servers appear after Refresh (panel)The API key cannot see them. Application keys see every server; client keys only see servers that account owns. Use an application key, or transfer ownership of the missing servers to the account behind the client key.
- "Cannot reach panel" or 404 on every callPanel URL is wrong. Use the full origin only, with no trailing slash and no path (e.g.
https://panel.example.com, nothttps://panel.example.com/orhttps://panel.example.com/api). Arkanis appends the API path internally. - A host starts, then immediately reports offlineThe process name or executable does not match what actually runs. On Windows check the name in Task Manager; on Linux check
psor the systemd unit name. Arkanis reads status by looking for that exact process. - A host connection saves but every action failsThe SSH account cannot act on the server. It must be the account that owns the server files, and on Windows it must land in cmd.exe, the OpenSSH default shell.
Which Providers Are Supported
A connection is one provider. Add as many as you need; servers from all of them land in the same Server Control list.
Pterodactyl is the open-source game-server panel a lot of hosts already use. Arkanis talks to it over its API. Needs the panel URL and an API key.
The actively-developed Pterodactyl fork, API-compatible with it. Identical setup; pick Pelican as the provider so the panel labels it correctly.
A server started from a script on a Windows machine you reach over SSH. No panel involved. Needs an SFTP connection and the start command.
A server run by systemd or a start script on a Linux machine you reach over SSH. Needs an SFTP connection and either the unit name or the start command.
What each provider can do
| Action | Panel (Pterodactyl / Pelican) | Host (Windows / Linux) |
|---|---|---|
| Start, stop, restart | Yes | Yes |
| Kill | Yes | Yes, by ending the process |
| Resource readout | CPU, memory, disk, uptime, network | CPU and memory of the server process |
| Browse, read and edit files | Yes, over the panel API | Yes, over SFTP |
| Console output | Live console from the panel | Read-only tail of the server log |
| Console input | Yes | No. Send commands through the RCON panel |
| Download link for a file | Yes, a signed URL from the panel | No, pull it over SFTP |
Connecting a Pterodactyl or Pelican Panel
Mint an API key in your panel
Go to Account Settings, then API Credentials, and create a key. It must be able to read and write the servers Arkanis will manage; a key scoped to fewer servers only lets Arkanis control those. Leave the allowed-IPs field empty unless your panel requires an allowlist, in which case list the Arkanis host. Copy the key once, you cannot read it again.
Add the connection
On the dashboard Server Control page click Add Connection and pick Pterodactyl or Pelican. Give it a name, then provide:
- Panel URL — the full origin of your panel (e.g.
https://panel.example.com), with no trailing slash and no path - API key — the key you just created
Discover your servers
Use Refresh servers to scan the panel and import everything the key can see. Each imported server becomes a row you can open, and counts against your plan's managed-server cap.
Verify the connection
Open /server control and select Server Info. A live CPU and memory readout means the credentials, the URL and the capability gate all work.
Connecting a Windows or Linux Host
A server that runs from a script instead of a panel is controlled over the SSH connection you already use for its logs. Arkanis writes a small start script (arkanis-start.cmd or arkanis-start.sh) into the working directory and, on Windows, registers an on-demand scheduled task named Arkanis-<id>; nothing else is installed.
Add the SFTP connection first
Add Connection, pick Windows host or Linux host
Activate the server
Which Games Does It Support?
Power, files and console are generic: they act on the server process or the panel API, so they work for whatever game you run. A panel hosts anything its egg catalogue covers (hundreds of games); a host runs whatever your start command starts.
- Power control (start, stop, restart, kill)
- File browsing, reading, and editing
- Console output, and console input on a panel
- Resource monitoring
- The Isle (Evrima) — RCON panel with Evrima-specific commands, structured log parsing
- Path of Titans — RCON commands, structured log parsing
- Other games — RCON and log parsing can be added per-request
the_isle or path_of_titans). Other games are still fully manageable; they just don't expose the deeper integrations.The Server Control Panel
Server Control groups every action into four categories, whichever provider a server came from. Launch it with /server control, or open the Server Control page in the dashboard sidebar.
Multi-Server Power Actions on the Dashboard
The dashboard Server Control page groups Start, Stop and Restart through a server picker. Servers from different providers can be selected together; each one is actioned through its own provider. The picker behaviour matches the RCON panel:
0 connected servers
The action button is disabled. Add a connection and refresh server discovery before bulk actions become available.
1 connected server
Clicking the action runs immediately on that server.
2 or more connected servers
The picker opens with checkboxes and an “All servers” toggle. Pick the targets, click Run, and a single per-server result banner is returned.
Bulk-supported actions:
- Non-destructive:
ptero_start. Runs immediately after the picker resolves. - Destructive (require type-to-confirm):
ptero_stop(verb STOP),ptero_restart(verb RESTART). The confirm modal lists the affected server names before it accepts the verb.
Those action names still carry the ptero_ prefix from when Pterodactyl was the only provider. They apply to every provider. Renaming them would silently break existing role configurations, so they stay as they are.
After the action runs, the per-server result banner shows each server's outcome with a color-coded chip (green success, amber retryable, red hard failure, grey unknown) and a footer with the parent audit ID. The audit trail follows the same parent-plus-children shape as RCON: a parent ptero_bulk_action row with redacted args, plus one ptero_bulk_action_result row per server.
Open a server from the Servers list for its page: a live console with a command box, Files, and for Windows and Linux hosts a Settings tab. Bulk Start, Stop and Restart stay on the Server Control page. The Kill action sits behind the Advanced menu on the server page, gated by a type-to-confirm dialog; it has no bulk variant.
Server Management
Monitor live resource usage and server status. When you have a single server linked, the panel auto-opens its detail view; with multiple servers, you get a selectable card list first.
Server Info
- Open
/server controland choose Server Info from Server Management. - If you have more than one server, pick it from the dropdown.
- Arkanis returns an embed with the figures that provider exposes. A panel reports CPU, memory, disk, uptime and network in/out; a host reports CPU and memory for the server process.
- Refresh the panel to pull updated values.
Server List
From the panel's server selector, choose Show All Servers to see every linked server with its current state (online, starting, stopping, offline), across every connection. Useful before running bulk power actions.
Quick Actions
Every power action is gated by capability checks and confirmation dialogs where appropriate.
Start
- Open
/server controland select Start from Quick Actions (disabled when the server is already running). - Pick the target server.
- Confirm. Arkanis streams the state transitions until the server reports running.
Stop
- Choose Stop from the Quick Actions dropdown.
- Confirm the prompt. A panel sends its graceful stop signal. A host runs an RCON save first when RCON is linked, then ends the process.
Restart
Select Restart from the Quick Actions dropdown. Arkanis performs a full graceful stop followed by a start and reports progress in the same message.
Kill
- Choose Kill from the Quick Actions dropdown.
- A red confirmation dialog warns about potential data loss.
- Type or click confirm to force-terminate. The server process is ended immediately without saving.
File Operations
Browse, read, and edit server files directly from Discord. A panel connection reaches files through the panel API; a host reaches them over the same SFTP connection it uses for logs. The actions look identical either way.
Browse Files
- Open
/server controland select Browse Files from File Operations. - Pick the server.
- Navigate using the breadcrumb trail. Each folder click drills deeper; the breadcrumb lets you jump back to any parent.
- Select any file to see metadata and the Read File action.
Read File
- From the browse view, click a file and choose Read File.
- Arkanis streams the text content. An Edit button is shown if your role has edit capability. Files past the editor's size limit are listed but not editable.
Edit File
- From the Read File view, click Edit.
- The inline monospace editor opens with the current contents.
- Make your changes.
- Click Save to write the file, or Cancel to discard without touching the file.
Download
On a panel connection, the Download action returns a temporary signed URL for pulling the file locally; the link expires after a short window. Hosts have no download action, so pull those files with your own SFTP client.
Console Access
Read what the server is printing, and on a panel connection type back into it.
Send Console Command
- Open
/server controland select Send Console Command from Console Access. - Pick the target server.
- Enter the command in the modal and submit.
- Arkanis forwards the command and captures any output into the command history.
Command History
The history view lists recent console commands with actor, server, timestamp, and response. Useful for auditing or reproducing a fix.
Opening the Panel
Every provider is reached through a single slash command. All actions are inside the panel dropdown menu.
/server control— Opens Server Control