My server will not start
Check the console in your panel first — it names the exact error. Confirm your disk quota is not full, then try a restart. Plugins or a corrupted jar are the usual cause of a crash loop.
There is no outsourced first line. The team that deploys your service is the team that answers your ticket, and every conversation stays in a single thread so nothing gets lost between replies.
Support conversations live inside your account so we can see the service your question is about. Sign in with the email you ordered with, and your existing conversations will be waiting.
Not ordered yet? Tell us what you want to run and how many players you expect, and we will recommend a plan — including whether a smaller one is enough.
Most questions are answered by one of these three. If none of them do it, open a ticket with the details below and we will take it from there.
Check the console in your panel first — it names the exact error. Confirm your disk quota is not full, then try a restart. Plugins or a corrupted jar are the usual cause of a crash loop.
Every setting lives in the service workspace: Startup for variables and the JAR, Settings for general options, Properties for the server itself. The panel is the same on every plan.
Services are created automatically once the order is confirmed and capacity is verified. A plan marked capacity limited has not been queued — it cannot be ordered until a node frees up.
The service name from your dashboard. We can then look at the actual node, container and allocation instead of guessing.
Describe the behaviour you wanted, in your own words. That is what lets us tell a misconfiguration apart from a fault on our side.
The error message, the exact wording of any dialog, and roughly when it started. Screenshots help for panel questions.
Restarts, a reinstall, clearing the file cache. This stops us repeating steps you have already ruled out.
Tickets stay linked to your services, so we can act on the real server instead of a description of it.