Managing Servers
As an administrator, you have oversight of all servers in the system. This guide covers server administration from the admin perspective.
Accessing Server Management
To manage servers:
Click Servers in the admin sidebar
You'll see a list of ALL servers across all users
Required permission: access_servers or admin role
Server List
Server List View
The admin server list displays:
Identifier - Pterodactyl server unique identifier
Name - Server name
Owner - User who owns the server
Product - Associated server product
Status - Active, suspended, etc.
Expiration Date - When server expires
Auto-Renewal - Whether auto-renewal is enabled
Created - Server creation date
Actions - Edit, manage, delete
Filtering and Search
Search for servers:
By server name
By identifier
By owner email
Filter servers:
By status (active, suspended)
By owner
By product
By expiration date
By auto-renewal status
Quick Stats
View aggregated data:
Total servers
Active servers
Suspended servers
Servers expiring soon
Server Details
Viewing Server Information
Click on any server to view:
Basic Information:
Server identifier (Pterodactyl ID)
Server name
Owner (user)
Product used for creation
Server Resources: Inherited from Server Product Build:
Disk Space - Storage allocation
Memory (RAM) - RAM allocation
CPU - CPU limit
I/O - Disk I/O weight
Swap - Swap memory
Databases - MySQL database count
Backups - Backup slot count
Ports - Additional port allocations
Billing Information:
Purchase date
Expiration date
Auto-renewal status
Last renewal date (if applicable)
Status Information:
Is suspended?
Pterodactyl sync status
Creation status
Editing Servers
How to Edit a Server
Find server in list
Click Edit action
Modify editable fields
Save changes
Editable Fields
Server Name
Change server display name
Helps owner identify their server
Visible to user
Owner (User)
Transfer server ownership:
Edit server
Select new owner from user dropdown
Save changes
Use cases:
Correct initial assignment errors
Transfer between user accounts
Handle account mergers
Support requests for transfers
Ownership Transfer
Transferring ownership gives the new owner full control. The previous owner loses access immediately. Confirm this is intentional before saving.
Expiration Date
Modify when server expires:
Extend expiration for customer service
Shorten for refunds/cancellations
Correct billing errors
What happens:
Server suspends on expiration date if not renewed
Auto-renewal attempts to renew before this date
User receives expiration warnings
Format: Date and time
Auto-Renewal Status
Enable or disable auto-renewal:
Enabled - Server automatically renews from user's balance
Disabled - User must manually renew
When to modify:
User requests to disable renewals
Account closure procedures
Payment dispute resolution
Special billing arrangements
Suspension Status (isSuspended)
Suspend or unsuspend server:
Suspended - Server is stopped and cannot be started
Active - Server can be started/stopped normally
When to suspend:
Non-payment (automatic on expiration)
Terms of Service violations
Abuse or resource overuse
Security issues
Account investigations
When to unsuspend:
Payment received
Issue resolved
Manual renewal processed
Read-Only Fields
Some fields are display-only:
Pterodactyl Server ID - Cannot be changed after creation
Identifier - Pterodactyl unique identifier
Server Product Build - Snapshot of product at purchase time
Server Product Build
What it is:
Immutable copy of the Product configuration at time of purchase
Defines server resources (RAM, disk, CPU, etc.)
Separate entity from the master Product
Why immutable:
Ensures server keeps resources purchased
Product changes don't affect existing servers
Allows different resources per server of same product
Viewing Server Product:
Click link to view exact resource allocation
See pricing at time of purchase
Compare with current product configuration
Server Actions
Quick Actions
From the server list:
Manage Server
Opens server management page
Access to Pterodactyl Panel (via SSO)
Server-specific controls
View User
Jump to owner's user profile
Check balance
View user's other servers
View Logs
See server-specific logs
Track server actions
Investigate issues
Advanced Actions
Recreate Server
If server creation failed:
Delete server from Pterodactyl
Recreate using stored configuration
Maintain same resources and settings
Use cases:
Initial creation errors
Pterodactyl API failures
Node migration issues
Sync with Pterodactyl
Force synchronization:
Pull latest data from Pterodactyl
Update server status
Resolve sync issues
When to use:
Status shows as out of sync
Recent Pterodactyl changes not reflected
After manual Pterodactyl modifications
Deleting Servers
How to Delete a Server
Find server in list
Click Delete action
Confirm deletion
Required permission: delete_server or admin role
What Gets Deleted
In PteroCA:
Server record
Server Product Build
Associated logs (depending on configuration)
In Pterodactyl:
Server is deleted via API
All server files removed
Allocations freed
Databases deleted
Permanent Deletion
Deleting a server is permanent and irreversible. All server data, files, and configurations are lost. Always confirm with server owner before deleting.
Soft Delete
PteroCA may use soft delete:
Server marked as deleted in database
Not visible to user
Can be restored if needed (before permanent deletion)
When to Delete Servers
Appropriate reasons:
User requests deletion
Account closure
Server expired and grace period ended
Duplicate/test servers
Refunded purchases
Do NOT delete for:
Temporary suspension (use suspension feature)
Payment issues (suspend instead)
Before grace period ends
Bulk Operations
Bulk Server Management
Select multiple servers to:
Bulk Suspend
Suspend multiple servers at once
Useful for mass non-payment scenarios
Abuse mitigation
Bulk Delete
Delete multiple servers
Caution: Permanent action
Confirm before proceeding
Bulk Transfer
Transfer multiple servers to new owner
Account migration scenarios
Using Bulk Actions
Select servers using checkboxes
Choose action from bulk actions dropdown
Confirm action
Operation applies to all selected servers
Server Monitoring
Health Monitoring
Track server health:
Online/offline status (from Pterodactyl)
Resource usage
Uptime statistics
Access monitoring:
Click on server
View Pterodactyl Panel data
Check console/logs
Expiration Monitoring
Track expiring servers:
Filter by expiration date
Set up reports for expiring servers
Proactively contact users
Automated warnings:
Users receive email reminders
Admin can see expiration list
Auto-renewal attempts before expiration
Suspension Monitoring
Track suspended servers:
Filter to show only suspended
Review suspension reasons
Process manual renewals
Grace period:
Configure grace period before deletion
Suspended servers count toward grace period
Delete after grace period expires
Pterodactyl Integration
Accessing Pterodactyl Panel
Admin access to any server:
Click Manage in Pterodactyl or similar
SSO to Pterodactyl as admin
Full control panel access
What you can do in Pterodactyl:
Access console
Manage files
Configure server
View resource usage
Manage databases
Control power (start/stop/restart)
Synchronization
Automatic sync:
Server creation syncs to Pterodactyl
Suspension syncs to Pterodactyl (server stopped)
Deletion syncs to Pterodactyl (server removed)
Manual sync:
Force sync if discrepancies exist
Refresh server status
Update resource allocations
Server Logs
Viewing Server Logs
Access server-specific logs:
Navigate to Logs → Server Logs
Filter by server or owner
View all actions related to server
Logged actions:
Server creation
Server modifications
Suspension/unsuspension
Ownership transfers
Deletion
Renewal attempts
Power actions
See Logs & Monitoring for full details.
Troubleshooting
Server Not Created
If server exists in PteroCA but not Pterodactyl:
Possible causes:
Pterodactyl API error during creation
Insufficient resources on node
Network issues
Invalid egg configuration
Solutions:
Check system logs for error details
Verify Pterodactyl connection
Check node resource availability
Recreate server if needed
Contact user about delays
Server Out of Sync
If PteroCA and Pterodactyl show different data:
Solutions:
Use Sync with Pterodactyl action
Refresh server page
Check Pterodactyl API credentials
Verify server still exists in Pterodactyl
Cannot Suspend/Unsuspend
If suspension status won't change:
Check:
Pterodactyl API is responding
Server exists in Pterodactyl
Your account has suspension permission
No errors in system logs
Solutions:
Verify Pterodactyl connection
Check server logs for API errors
Manually suspend in Pterodactyl if needed
Auto-Renewal Failed
If auto-renewal didn't work:
Possible causes:
Insufficient user balance
Server already suspended
Billing calculation error
System error
Solutions:
Check user's balance
Review system logs for renewal attempts
Manually renew server
Add balance to user account
Contact user about failed renewal
Best Practices
Server Administration
Do:
Monitor expiring servers proactively
Communicate with users before suspensions
Keep detailed notes on server issues
Verify user consent before transfers/deletions
Maintain backup of important server data
Don't:
Delete servers without user knowledge
Modify resources without informing user
Transfer ownership without verification
Ignore suspended servers indefinitely
Performance
Regularly clean up expired/deleted servers
Monitor resource usage across nodes
Balance server distribution across nodes
Archive old logs to free space
Security
Audit server access logs
Monitor for abuse patterns
Investigate unusual resource usage
Enforce Terms of Service consistently
Related Guides
Managing Users - User account administration
Managing Products - Product configuration
Logs & Monitoring - Server activity tracking
Pterodactyl Integration - API setup
Need Help?
For server management questions:
Check FAQ
Review Troubleshooting Guide
Join Discord Community
Contact technical support
Last updated