How to Fix a Minecraft Server Whitelist That Keeps Resetting

Direct answer

Find file-write, UUID, panel, startup-script, or synchronization issues that overwrite whitelist.json.

What it means

The whitelist data is being overwritten, not saved, regenerated from another source, or interpreted under a changed player identity/authentication setup, so entries do not persist as expected.

If you are a player

Record whether your username is removed after a server restart, a network transfer or a host-panel sync.
Have staff inspect the exact Java username/UUID; do not try to bypass the list by using alternate accounts.
Do not publish player UUID lists in public support threads unless needed.

If you run the server

Back up whitelist.json and check whether its contents change before shutdown, during startup or when a panel automation runs.
Use Java whitelist list and whitelist add <name> from the server console, then whitelist reload if the file was edited externally.
Check write permissions, host template synchronization, plugin-managed allowlists and proxy/backend whitelist differences.
If online-mode or forwarding was changed, audit UUID identity mapping rather than deleting whitelist records blindly.

Verify the result: After a clean restart and panel sync, confirm the intended account stays listed and can join while an unlisted test account remains blocked.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

Was this article helpful?

Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.