My Server Stopped on Its Own

Use the server status, Credit Balance, Automation, and Activity Log to identify why a server stopped.

Check Credit Balance first

A running server is charged for its next hour when the current paid hour ends. If the owner's Credit Balance cannot cover that charge, the server is stopped and the balance does not go below zero.

To continue:

1. Top up the owner's Credit Balance.
2. Return to Console and open the server.
3. Select Start.

The stopped server is not deleted, and its remaining Banked Hour is preserved when applicable.

Check Auto-shutdown

Open Automation and check whether Auto-shutdown was enabled for that day, time, and timezone. A scheduled shutdown is expected even if players are connected.

If the schedule was not intended, correct it and confirm that the page shows Schedule saved. A missed or unwanted occurrence is not reversed automatically; start the server manually.

Check recent actions and access

Review the Activity Log around the stop time. If other people have access, open Roles & Sharing and check which roles can start and stop the server. Remove a member or revoke and replace a link if access is no longer appropriate. Revoking a link does not remove members who already joined through a login-required link; remove those members separately.

Check for an Error

If the server shows Error rather than Stopped, read the status message and Activity Log. Wait for any current operation to finish, then try Restart once. Repeated errors need the checks in My Server Won't Start.

Next action

To reduce unexpected stops, keep enough credit for the displayed hourly rate, use Auto-shutdown when you want a predictable stop, and consider a lower-cost Server tier or Server size. Review the actual hourly charges in Cost & Usage.