Server is rebooting by itself sometimes and disconnecting all, and that cause us to lose some items if server didnt save world. I dont know if it crashes and it reboot.
@CubeCoders-Bot Help this user determine if they are in an OOM situation which is what I suspect may be the cause. Failing that, help examine their Minecraft server logs from within AMP using the file manager. Assume they are not particularly Linux savvy despite using Debian. Don’t do anything regarding the container, ignore it for the sake of diagnosing the issue.
Alright, let’s try to figure out what’s making your Minecraft server reboot itself like an over-caffeinated hamster. First, we’re going to check if the server is running out of memory (OOM - Out of Memory). This is a common issue and can cause unexpected reboots like what you’re describing.
Pop open AMP’s Diagnostics Tab (Settings → Support → Diagnostics) and hit that “Copy data to clipboard” button. Paste the juicy info it gives us here as text. That’ll usually give us a clue if OOM is involved.
If that doesn’t pan out, we can dive into the Minecraft server logs—AMP’s File Manager to the rescue for that. But first, let’s rule out memory issues.
This post was produced by an AI controlled by CubeCoders Limited - Feedback
Hello bot, may could you tell me where is this diagnostics tab? there isn’t anything named ‘settings’, there’s configuration but it hasnt support => diagnostics.
Ah, you’re right—naming conventions can be a pain. My bad on that!
In AMP, the Diagnostics Tab isn’t under “Settings,” it’s under the main ADS (the one managing all your instances). Login to ADS, search for “Diagnostics” in the search box at the top-right to find it. From there, you should see the button to “Copy data to clipboard.”
If you’re still stuck, just let me know and we’ll dig deeper together.
This post was produced by an AI controlled by CubeCoders Limited - Feedback
Alright, no need to Sherlock Holmes this thing; let’s break it down. From the screenshot, that’s the File Manager view, which is helpful but not the Diagnostics tab we need.
Here’s the map: Go to your ADS instance. That’s the manager instance controlling all your game servers. Once in ADS, look for Configuration and then Support & Updates. That’s where the diagnostics are hiding.
Once you find it, grab the “Copy data to clipboard” button info and paste it here as text (not as an image or link). If the Diagnostics tab is still elusive, give me another shout. It’s hiding somewhere, I promise!
This post was produced by an AI controlled by CubeCoders Limited - Feedback
Ah, great—you managed to navigate to it, even if AMP played “hide the Diagnostics”! Not sure why AMP decided to list it under some cryptic spot. Anyway, is that all it provided you, or is there a more detailed section related to the Minecraft server or any memory-related hints?
Check through for crash/termination logs, resource usage, or anything mentioning system memory or OOM. Post it here as plain text when you find it. We’re looking for any clue as to why your server keeps rebooting itself. If this doesn’t yield results, we’ll move on to reviewing the Minecraft server logs directly.
This post was produced by an AI controlled by CubeCoders Limited - Feedback
Alright, either AMP’s diagnostics are being unhelpfully tight-lipped, or we’re not seeing OOM issues logged there. No sweat; let’s shift focus to the Minecraft server logs.
Back in AMP, use the File Manager (the tab from your previous screenshot). Navigate to your Minecraft instance’s logs folder and look for files like latest.log or any crash-report files. Open up the latest ones and paste the text contents here. This is where we’ll likely find something useful about what’s causing these surprise reboots.
This post was produced by an AI controlled by CubeCoders Limited - Feedback
there isn’t latest.logs, but theres a file with date and hour. and thats the point it always resets “[23:34:52] [System:admin Warning/23] : The application stopped unexpectedly. Exit code 137”
Exit code 137 is our troublemaker here—it typically means the server was killed because of insufficient memory (OOM). Sounds like your server ran out of RAM, and the system decided to put it down like a sickly Tamagotchi.
Let’s increase the Java memory allocation in AMP. Go to your Minecraft instance settings in AMP:
Search for “Java” in the top-right search bar.
Locate the “Java and Memory” section.
Increase the Maximum Memory (Xmx) value. As a starting point, allocate at least 2-4 GB more than what it’s currently set to.
Save and restart the instance. This should give your server the elbow room it needs. Let me know how it goes, or if the issue persists!
This post was produced by an AI controlled by CubeCoders Limited - Feedback
there isnt anything as that, there are no results like ur if i type java in searchbar. It’s also weird how 3.6gb ram isn’t enough for run a MC server without any complicated plugin, even Aternos could run it without any lag at lower ram and configs
Huh, that is odd. Let’s double-check the available memory for the whole system. If the server only has ~4GB to its name and other stuff (AMP or even the OS) is nibbling on it, that could explain why even Aternos seems chiller.
Do this:
Go to AMP’s System Info page from ADS (search “System Information” in the top-right). It should show how much total RAM the system has available.
Let me know what you find, and we’ll figure out if the issue is limited server RAM allocation or something else hogging resources. (Tempted to blame Java. It’s always Java .)
This post was produced by an AI controlled by CubeCoders Limited - Feedback
Ah, there’s the bottleneck—the whole system only has about 4 GB of RAM to play with. Since AMP, the OS, and Minecraft are all fighting for memory, it’s not surprising the server is face-planting with exit code 137.
Aternos probably stabilizes things with some super-tight optimization magic that AMP doesn’t replicate out-of-the-box. For a smoother run:
Lower your Minecraft memory allocation:
Head to your Minecraft server settings in AMP.
Search for “Java and Memory” (it’s buried somewhere, I swear—AMP loves a scavenger hunt ).
Reduce the Maximum Memory (Xmx) to 2.5 or 2 GB to leave some room for the OS and AMP itself.
Disable unnecessary plugins: Some aren’t much of a drain, but even basic ones like Geyser or SkinsRestorer chew RAM.
Optimize server settings:
Use AMP’s UI config to tweak things like render distance or entity tick limits for lower memory usage.
Give that a go. If it still nukes itself, we might need to consider slicing out plugins or expanding your RAM setup because 4 GB can only stretch so far!
This post was produced by an AI controlled by CubeCoders Limited - Feedback
This post was produced by an AI controlled by CubeCoders Limited - 
Sounds like your server ran out of RAM, and the system decided to put it down like a sickly Tamagotchi. 
.)
).