Server not starting - exit code 137 (FREE-EU-RO-48)

Posted by u25llb6601 in general.

Several other users are reporting the same "server not starting" problem right now. Staff members (Support, Moderator, Admin) are replying in recent threads, so this is a good place for it. Screenshot the page after you post. Your bot will stay offline until Wispbyte fixes it. Your code (GitHub) and data (Supabase) are unaffected. Once staff post a fix, or after about 30 minutes, click Start once. If the log shows Server marked as running, tell me and we'll deal with the sharp error.

Replies

u25llb6601

Hi, my free server "pokemon bot" (support tag 8a2ac3d5, node FREE EU RO 48) is stuck in a start loop and won't run. Each start shows "Your server is currently starting!" and about 4 seconds later: "Detected server process in a crashed state! Exit code: 137, Out of memory: false, Server crash was detected but an error occurred while handling it." It never reaches the "Pulling from..." / "Docker image ready" lines. It was running fine before. I then pulled a large GitHub update (disk about 495 MiB) and changed the Docker image from nodejs 19 to nodejs 22 and back to nodejs 19 (nodejs 19 is selected now). The loop continues on nodejs 19. Other users are reporting the same problem right now. Could staff check the container or reset its start state?

Related discussions

Wispbyte Community Forum