Common Errors and Troubleshooting

When encountering startup halts or connection failures, use the following troubleshooting resolutions.

---

Issue 1: "Connection Refused: connect" or "Can't connect to server"

Cause:

The game client reached the target host, but no active Minecraft server application accepted traffic on that specific port.

Resolution Steps:

1. Verify the server is running and the console displays the final confirmation: Done! For help, type "help".
2. Confirm you included the colon and port number (e.g., 45.13.237.208:25582), not just the raw IP address.
3. Check status.freemchosting.com for ongoing node maintenance.

---

Issue 2: Server Stops Immediately (EULA Agreement)

Cause:

Mojang requires affirmative acceptance of their End User License Agreement before a server will generate initial world files.

Resolution Steps:

1. Go to Files in your dashboard.
2. Open eula.txt.
3. Locate eula=false and change it to eula=true.
4. Save the file and start your server from the Console tab.

---

Issue 3: "java.lang.OutOfMemoryError" or Crash on Boot

Cause:

The server ran out of allocated RAM, often caused by heavy modpacks, memory leaks, or incompatible plugin versions.

Resolution Steps:

1. Open the File Manager and check logs/latest.log or examine files inside the crash-reports/ directory.
2. Confirm you have not installed client-only mods (such as Sodium, OptiFine, or minimap mods) on the server.
3. If running Fabric mods, ensure the FerriteCore memory optimization mod is added.
4. Remove redundant or unmaintained plugins.

---

Issue 4: Server Icon Does Not Display

Cause:

The image file fails to satisfy Minecraft's strict specification format.

Resolution Steps:

1. Verify the dimensions are exactly 64x64 pixels.
2. Verify the filename is strictly server-icon.png in lowercase.
3. Confirm the file is stored in the root server folder (/), alongside server.properties.
4. Refresh your Minecraft multiplayer list to clear the local client icon cache.