Need a Minecraft server? BeastNode offers the highest performance servers with DDoS protection!

Shop for plans now


Server Not Starting - "Caused by: com.google.gson.stream.MalformedJsonException"

With the update to UUID's in 1.7.9, Minecraft also updated the file formats used for the OPs, Whitelist and Banned Players/IPs files from .txt to .json (plus the usercache.json file which stores player UUID's once they have logged in).

These files have a considerably different layout (see the guide HERE on the whitelist for an example of the changes) and any breaks in the layout, even a missing piece of punctuation or spacing error, can cause the server to crash on startup. In Vanilla this will occur if any of the .json files have a broken layout - some server versions, such as Spigot, will ignore the whitelist.json file if the layout is broken. The whitelist will not work in this case, and the server will still start up fine, but crash if the other .json files are broken.

The easiest way to fix this, if you are not familiar with the .json file layout, is to simply make a note of the names in the file and reset it (There should be nothing but two brackets, [], in the file when it is reset). When the file has been reset and the changes saved, restart the server to start it up. To add people to these files afterwards use the following commands through the console (or ingame with a slash infront as normal if you have the permissions/are already OP'd ingame):

ops.json:
- op [name]
- deop [name]

banned-players.json:
- ban [name]
- pardon [name]

banned-ips.json:
- ban-ip [IP]
- pardon-ip [IP]

whitelist.json:
- whitelist add [name]
- whitelist remove [name]

Was this answer helpful?

 Print this Article

Also Read

Whitelist enabled in the server.properties but not working

This is caused if the whitelist.json file format is broken. Whilst the other .json files will...

Troubleshoot Lag Problems with Spigot

With Spigot, it is possible to pin-point potential causes of lag on your server by using the...

Chunk Corruption Errors

[INFO] Chunk (42, -2) stored at (35, -28) [SEVERE] java.lang.Throwable[SEVERE] at...

Failed to check session lock

Failed to check session lock errors can occur randomly and usually begin with this...

Out of Memory

Usually, out of memory errors (and other errors that are similar) is due to your server basically...