critical wings
In the console
exceeding the assigned disk space limit
Server is exceeding the disk limit
Wings stops a server as soon as its files use more space than the disk limit set on the server. Until space is freed the server will refuse to start again.
How to fix it
- Open the File Manager and sort by size to find what grew: old logs, backups saved inside the server folder, crash reports, world backups or caches are the usual cause.
- Delete or archive what you no longer need (for example logs/*.log.gz, crash-reports/ or old world copies).
- If the data is genuinely needed, ask your host or admin to raise the disk limit for this server.
- Start the server again once usage is below the limit.
critical wings
In the console
Aborting automatic restart, last crash occurred less than seconds seconds ago
The server crashed twice within 60 seconds, so Wings stopped restarting it to avoid an endless crash loop. The real problem is whatever made it crash the first time.
How to fix it
- Scroll up in this report or the console to the first error before the crash; Cardinal Review lists it above when it recognises it.
- Fix that cause (memory, a broken plugin or mod, a bad config), then start the server manually.
- If the crash happens instantly on start, check that the startup command, Docker image and server jar or binary match what the server expects.
critical wings
In the console
Detected server process in a crashed state
The server process exited while Wings expected it to be running. Wings prints the exit code and whether the container ran out of memory right after this line.
How to fix it
- Look at the exit code and the 'Out of memory' line printed just after this message; Cardinal Review explains both when they are present.
- Read the last lines the server printed before it died; that is normally the actual error.
- If nothing was printed, the process was most likely killed from outside (out of memory, or the node itself had a problem).
critical wings docker
In the console
Out of memory: true
OOMKilled
The server used all of the memory assigned to it and the kernel killed it. Everything running in the container counts: the game itself, the JVM or runtime overhead, native libraries and plugins.
How to fix it
- For Java servers, keep -Xmx (or the memory startup variable) about 10-15% below the container limit so the JVM overhead still fits.
- Check the Performance tab for a memory climb before the crash: a steady climb points to a memory leak in a plugin or mod, a sudden jump to a specific action.
- Reduce load: lower view-distance and simulation-distance, pre-generate the world, remove heavy plugins or mods.
- If the server legitimately needs more, ask your host or admin to raise the memory limit.
critical wings docker
In the console
Exit code: 137
exited with code 137
Exit code 137 means the process received SIGKILL. In a container that is almost always the out-of-memory killer, or the server being killed after it ignored a stop request.
How to fix it
- If the 'Out of memory' line says true, follow the memory advice: lower -Xmx below the limit or raise the limit.
- If you pressed Kill or the stop command timed out, this is expected; make sure the egg's stop command (for example 'stop' or '^C') actually shuts the server down cleanly.
critical wings docker
In the console
Exit code: 139
exited with code 139
Exit code 139 is SIGSEGV: native code read memory it should not. This comes from the game binary, a native library or a native mod/plugin, not from your config.
How to fix it
- Update the server binary, the Docker image and any native mods or extensions (Metamod/SourceMod, Oxide, native Node or Python modules).
- Remove recently added mods or plugins one at a time to find the one that triggers it.
- If it started after an image change, switch back to the previous Docker image on the Startup page.
critical wings docker
In the console
Exit code: 127
exited with code 127
Exit code 127 means the shell could not find the program the startup command runs. The Docker image does not contain it, or the file name or path in the startup command is wrong.
How to fix it
- Check the startup command on the Startup page and make sure the program it calls (java, node, python, the server binary) exists in the selected Docker image.
- If the command runs a file from the server folder, confirm the file exists with exactly that name (names are case-sensitive).
- Try another Docker image offered by the egg, for example a different Java or Node version.
critical wings docker
In the console
Exit code: 126
exited with code 126
Exit code 126 means the file exists but cannot be executed: it is missing the execute permission, or it was built for another CPU architecture.
How to fix it
- In the File Manager, open the file's permissions and add execute (chmod 755), or reinstall the server so the installer sets them.
- If the node runs on ARM (arm64), make sure the binary and the Docker image are ARM builds.
warning wings
In the console
Exit code: code
The process ended with a non-zero exit code, which means it stopped because of an error rather than a clean shutdown.
How to fix it
- Read the lines just before the exit; the program usually prints why it stopped.
- Exit code 1 is a generic error, 2 is often a bad command line argument, 143 means it was stopped with SIGTERM.
critical wings docker
In the console
pull access denied
Failed to pull requested image
Error response from daemon: Get http:// … : dial tcp
Wings could not download the Docker image this server runs in, so it cannot create the container. The image name may be wrong or removed, the registry may need credentials, or the node cannot reach the registry.
How to fix it
- On the Startup page, pick another Docker image offered by the egg and try again.
- Admins: check that the image name in the egg is spelled correctly and still exists on the registry.
- Admins: on the node run 'docker pull <image>' to see the full error, and check the node's DNS and outbound network.
Cardinal Review