This page contains a number of common issues and how you can troubleshoot and resolve them.
Duplicate UUIDs in database
This is most frequently caused by running a cracked “offline mode” network of servers. We don’t provide support for problems caused by cracked servers and the most advice we can offer you is:
bungee_online_modeis set to the correct value in the
paper.ymlconfig file on each of your Bukkit servers
- Ensure your authenticator plugin is passing valid, unique IDs to each backend Spigot server.
Cannot set data with newer Minecraft version than the server
This is caused when you attempt to downgrade user data from a newer version of Minecraft to an older one, or when your Spigot servers are running mismatched Minecraft versions.
HuskSync will identify this and safely prevent the synchronisation from occuring. Your Spigot servers must be running the same version of both Minecraft and HuskSync.
User data failing to synchronise
This can occur due to misaligned timings between your Spigot servers and your Redis server. HuskSync has a built in way of tuning this. Try continously increasing the
network_latency_milliseconds option in your config to a higher value.
Exceptions when compressing data via Snappy (lightweight Linux distros)
Some lightweight Linux distros such as Alpine Linux (used on Pterodactyl) might not have the dependencies needed for the Snappy compressor. It’s possible to disable data compression by changing
compress_data to false in your config. Note that after changing this setting you will need to reset your database. Alternatively, find the right libraries for your distro!
Redis connection problems on Pterodactyl
The internal firewall on Pterodactyl can block Redis connections between servers. Add an allocation to each server allowing them to communicate with your Redis server. It may be easier to install Redis in an egg than trying to use the backend internal service.