Failed to load properties from file: fix server.properties

A Vanilla or Fabric server that starts without a server.properties file prints this in red in the Console, then finishes booting a few lines later:

Failed to load properties from file: server.properties
java.nio.file.NoSuchFileException: server.properties

Minecraft can't find its settings file, so it uses default values for that start and writes a fresh server.properties straight away.

Why server.properties goes missing

Our install step writes a small starter server.properties before the first start, so a fresh install normally boots without this error. When you do see it, the file has usually been deleted or renamed, or its replacement was uploaded under a slightly different name, such as server.properties.txt from Notepad.

Can you ignore it?

Yes, when all three are true: it showed on only one start, the Console still reached Done (…s)!, and players can join. It's a real problem when:

• Players can't connect after that start - the server may be on the wrong port. See check 1.
• Your settings are back to defaults - the old file is gone. See check 2.
• It shows on every start - the new file isn't staying on the server. See check 3.
• The line under it names another exception, such as AccessDeniedException - the file exists but the server can't read it, and a restart won't fix that. Gather the details listed under If none of these fixed it.

1. Did the server start on the wrong port?

The panel writes your server's port into server.properties on each start. With no file to write to, Minecraft falls back to port 25565, which players can't reach.

1. In the Console, press Restart and wait for Done (…s)!. The red error shouldn't appear this time.

   

2. Scroll up to the line starting Starting Minecraft server on and note the port after the last colon. *:25565 means the server started without its settings file.

3. Open Settings (under More in the left rail). Under Network ports, the port on the Primary row should match.

If the ports still differ after a second restart, go to check 3. If they match and players still can't join, see Join your Minecraft server (and fix errors).

2. Did your settings go back to defaults?

A new file has default values, including a world folder called world. If your world lived in a folder with another name, the server has generated a new world and your old one is still on disk.

The new file also turns Whitelist off, so anyone with the address can join. If you used a whitelist, switch it back on in the Players tab first. It applies straight away, and your whitelist.json is untouched.

Then bring back your other settings:

• Set them again in the Config Editor, including World folder if your world had a custom folder name, then restart.
• Or use your old file if it's there under the wrong name, such as server.properties.txt. Delete the new server.properties, Rename yours to exactly server.properties, then restart.

Or recover the old file from a backup:

1. In Backups, press Download on a backup from before the file went missing. It saves as a .tar.gz archive.
2. Open the archive on your computer and copy out server.properties.
3. In the File Manager, upload that file to the top folder and choose Replace & overwrite.
4. Restart the server.

3. Is the error back on every start?

If the error shows on every start, the file Minecraft writes isn't staying on the server. Check whether it's there.

1. Restart the server and wait for Done (…s)! in the Console.
2. Open the File Manager and look for server.properties in the top folder.
3. If it's missing, or the error shows again on the next start, gather the details listed under If none of these fixed it.

Change a setting without breaking the file

The Config Editor tab (in the Content group) shows each setting as a labelled control, so there's no syntax to get wrong.

1. Search for the setting, for example difficulty.
2. Change it and press Save changes in that section.
3. Restart the server. Minecraft only reads the file when it starts.

For a setting the Config Editor doesn't list, take a backup in Backups, then edit the file in the File Manager and restart. Change only the value after the =: Minecraft ignores a key it doesn't recognise. How to manage your server files covers the editor.

If none of these fixed it

Gather these before you ask for help:

• The full Console error, from the first red line to the exception under it.
• The Starting Minecraft server on line from the same start.
• The Minecraft version and loader from the JAR Manager tab.
• What changed just before it started: a deleted or uploaded file, a restored backup, a new modpack.