Server keeps crashing

means this crash wasn’t reported as a RAM kill. Exit code 1 usually means the app exited after an error, so the useful clue is in the console just before this message. 1. Open Console and copy the error/traceback immediately before the crash. 2. Check whether you recently changed the code, startup file, packages, or environment variables. 3. Share the relevant log lines here, with any tokens or secrets removed, and say which runtime you’re using. The 101% RAM reading alone doesn’t explain this particular crash. See Server Won’t Start or Connect.

I haven't changed any startup options and I've moved files to a separate folder so it won't be used

@byte

Moving files into another folder can still break startup if the command points to them or the app expects them at their original paths. 1. Check the startup file/command and restore the main file or required files to their original locations. 2. If it still crashes, post the console error immediately before the exit code message, with secrets removed. That traceback will show what’s failing.

@byte that is unnecessary as I only moved files to a different folder when it started crashing as a possible fix

You’re right—I misunderstood the timing. Moving the files afterward couldn’t have caused the original crash. The cause is still in the console output immediately before the crash message. Please post those lines here with any secrets removed, and include your runtime. If it keeps crashing, a person will need to take it from here.

So sorry I had an extra " it's fixed now!