> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.nexushosts.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How to View and Understand Your Minecraft Server Logs

Minecraft server logs might look confusing at first, full of timestamps, warnings, and messages that aren't always easy to understand. But logs are really just a record of what’s happening on your server. Once you know how to read them, they can help you quickly spot problems, keep an eye on player activity, and fix performance issues.

### Step 1: Log in

Log in to your [Nexus Hosting Account](https://gamecp.nexuscorehosting.com/auth/login).

![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXfeUSwhIC2TFn-NJUY2yF9oo779O62KAsQXaus1oF62Fd8LnYC88te9oCf7WT-ZhV9tn-y4GdYQEifAHbHOtYkHXj8q1SNbHn1hxUt6OzeQyGq-UvM8vl7JhlpcPARUXkemgtKejg?key=mDSnHMRSbsVeGcOwzYXHEY0S)
### Step 2: Select the Server

Once on the dashboard, find and select your intended Minecraft server. 

![](https://storage.crisp.chat/users/helpdesk/website/-/1/e/6/c/1e6c49e0d02dca00/minecraftserver_pwjjl0.png)
### Step 3: Open logs

Now, click ** Files** in the sidebar. Locate and select the **logs** file from the list. This folder contains all recent server logs.

![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXefXP2Qcm3cg7WSRyZFfhDBbCXU-gW5ytL3yGh3jh-R2bmfI9kvlI5PCWCgj3MLVNxhFt-dBKVjE-eZGPo5hHgLWVW9JPu8U2sCRWd9TjGYp9_WJozhHtnrlHoa5GHCxMYSVNqs?key=mDSnHMRSbsVeGcOwzYXHEY0S)
### Step 4: Download Logs

Inside the logs folder, you'll find files organized by date. For example, a file named 2024-04-24-1.log.gz. The **latest.log** (at the bottom) file always shows the most recent server activity as it happens. Older log files are compressed with a .gz extension to save space. 

You can download these compressed files by clicking the **ellipses** and then **Download** from the pop-up window. Before viewing them, you’ll need to extract them using something like WinRAR, 7-Zip, or your computer’s built-in archive utility.

![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXdWix5pbgr3Bv9r8lgoag2YF6JyzHhcH3NAr9fL_9jiMnWG_E0BRC82hQ-YPPMmg2g70SQHCOkAmjCwzE-DUgts59JVCaeHVrES6To8UYD5ev0-r2W6Ko_xOYYU6MBDyGdZ_c4V?key=mDSnHMRSbsVeGcOwzYXHEY0S)
### Step 5: Understanding Log Entries

Minecraft logs follow a straightforward format:

**[HH:MM:SS] [Server thread/INFO]: Player joined the game**

**[HH:MM:SS] [Server thread/WARN]: Can't keep up! Is the server overloaded?**

**[HH:MM:SS] [Server thread/ERROR]: Encountered an unexpected exception**

* **INFO** indicates standard events (player actions, server start-up/shutdown).
    
* **WARN** signals potential problems (lag warnings, minor plugin issues).
    
* **ERROR** points to significant problems, often needing immediate attention (crashes, plugin malfunctions, corrupt world data).

![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXcMg6-lJnzFKAcj1i47oCCJBlJhFpKxg71MwgwEymkqWGbOke5pJg8ie0bDhIat1Ozx2rsG64n4ww7Lvu5WrlftIzVmXL83oUVMDVUvsIyg_JRa3JOkD9iFvEZxdNloAoGPsHiC4A?key=mDSnHMRSbsVeGcOwzYXHEY0S)
Here are a few example log messages and their meanings:

* [Can't keep up!](https://www.partitionwizard.com/clone-disk/minecraft-server-cant-keep-up.html): Your server is lagging. Check CPU or RAM resources, or consider adjusting plugins or mods.

* [Failed to bind to port!](https://help.sparkedhost.com/en/article/how-to-fix-failed-to-bind-to-port-on-minecraft-server-107fr8o/#:~:text=This%20issue%20usually%20means%20the,very%20common%20and%20thankfully%2C%20fixable.): Another instance of the server may already be running, or your configured port is occupied.

* Player moved wrongly!: Usually harmless, but frequent occurrences might indicate network latency or misconfigured anti-cheat plugins.

* Encountered an unexpected exception: Indicates severe server errors, often mod conflicts or corrupt files.

### Step 6: How to Troubleshoot Using Logs

When troubleshooting an issue, your logs are your best starting point:

* **Check the timestamps** around when the problem happened. Logs are time-stamped clearly, so you can pinpoint exactly when things went wrong.

* **Focus on ERROR and WARN entries first**, since these messages highlight actual or potential issues.

* Once you've identified these specific messages, you can use them to search for solutions online or share them directly with support to clearly explain what's happening on your server.

**