The server will not come up, friends cannot join, or it dies moments after every start. The server page on uniz.host almost always says why — but the answer is spread across three places. This guide walks them in the order worth checking, from the one that states the cause outright to the one you have to read yourself.
Read the status badge first
The badge beside the server name is the first answer, and it is more specific than most people notice.
| Badge | What it means | What to do |
|---|
| Creating | first-time install; game files or a modpack are downloading | wait, and watch progress in the console |
| Starting | told to boot, not ready for players yet | wait; if it stays here, see the restart-loop section |
| Online | up and accepting players | if nobody can join, the problem is the address or the player's end |
| Stopped | off, and not being charged for | press start |
| Sleeping | put to sleep for you because nobody was playing | normal — a player connecting wakes it |
| Stopped — out of credits | stopped by the platform when credits ran out | top up, then press start |
| Archived | stopped long enough that the world was moved into storage | press start once; the world is restored free |
If you see "Stopped — out of credits" there is nothing further to diagnose. A card headed "Out of credits" appears on the same page with a top-up button. Top up, press start, and your world and files are exactly as you left them.
Read the last-error card if there is one
When a start fails at the platform level, a red-bordered card appears headed "Last error" followed by an explanation. Four underlying failures are translated into plain language.
| What you see | What actually happened | What usually fixes it |
|---|
| The server started then shut down repeatedly | the game boots and dies, over and over | read the console — usually a mod, a version, or a config file |
| Couldn't pull the server image | the program to run could not be fetched | check the configured version exists, then try again |
| The container failed to start | it failed before the game even began | try again; if it repeats, tell support |
| The selected size exceeds the cluster's current limits | no room right now for the size requested | try a smaller plan, or contact support |
If the message does not match any of those four, it is a raw message from underneath with no translation yet. Copy the whole line for support — it is worth a lot.
The card holds the most recent error, not the current state. A server that has since come back online may still show the card from an earlier attempt, so let the status badge decide what is true now.
Open the console and find the last lines before it died
The "Console" tab is the log the game itself prints, and it is the only place that names which mod or which line of config broke it.
Worth knowing before you read:
- The console is a live stream. It opens with roughly the last 200 lines and then follows along on its own — no need to press refresh.
- It keeps the most recent 500 lines on screen; older ones scroll away. To read more at once, expand it to full screen (Esc leaves).
- Logs are available from the "Creating" state onward, which is the most useful window for a large modpack because you can watch how far the download has got.
- An empty console during boot is normal. Before the container prints its first line the platform returns empty logs rather than an error, and keeps polling until output appears. Nothing is wrong and hammering refresh will not help.
- Passwords and secrets that leak into a log line are masked before the line ever reaches you.
The way to read it: work bottom to top and find the last lines before the run ended. Watch for filenames, mod names, and anything starting with Exception or Error. On Minecraft, UnsupportedClassVersionError or class file version means a Java version mismatch, which has .
The symptom: the badge sits on "Starting" and never becomes Online, the console prints the same block every few minutes, and the restart button is greyed out.
That is not a bug. Restart is only enabled while the server is genuinely online, because restarting means shutting down cleanly and coming back — which cannot be done to a server that never came up. In this state the button that works is Stop.
Stop it fully, fix the cause, then start again
- Press "Stop" and wait until the badge settles on "Stopped" — do not press start while it is still stopping
- Fix whatever the console pointed at. If you added a mod or changed the version just before this, undo that first: it is the most common cause by a distance
- Press "Start" and watch the console from the first line
If the "Changes pending a restart" banner is showing in this state, its button becomes Stop instead of Restart, for exactly the same reason.
Money is not a worry meanwhile: billing starts only once a server reports itself online, so a server that never finishes booting is never charged for. Stop it anyway — a server sitting in a restart loop is doing nothing for anyone.
When commands work
The command box under the console has two conditions.
First, the server must be online. Otherwise it reads "Console commands are available while the server is online", because a command is delivered to the running game, not to a file.
Second, the game must support remote commands. Minecraft does, which is why it gets a command box plus command and player-name suggestions. Palworld has no such system in the game itself, so a Palworld server shows logs and its own dedicated buttons but no command box.
Palworld: one line a minute is normal
If your Palworld server is quiet with nobody playing, the console will show roughly one line per minute. That is deliberate.
The game logs a line every time something reads values out of it, and our platform reads routinely to count players and measure server health. Letting all of it through would fill the console with the echo of our own polling, so one line a minute is kept as a sign of life and the rest is dropped. Real in-game events and the results of your own actions are never dropped.
Online, but friends still cannot join
If the badge says Online, booting is not your problem. Check these three:
- Wrong address — copy it from the Overview tab exactly. Games that use a port need the port number too; it is not optional.
- The address was just changed — the old one stops working immediately, so players who saved it in-game have to remove and re-add it.
- Whitelist or ban list — a Minecraft server with the whitelist on refuses anyone not on it, while working perfectly in every other respect.
Still stuck — what to send support
Sending these four together shortens things considerably:
- the server name or its address
- the status badge you are looking at right now
- the full line inside the "Last error" card, if there is one
- the last twenty or so console lines before it died
And if you changed something just before this started, say what. Nearly every time, that is where the answer is.
Read next
- — if the console mentions class file version
- — how to undo a config edit
- — every badge, card and tab on the server page
- — if the server stopped for want of credits