Servers · 6 min
Set up a server whitelist
Control who can join a Minecraft server and reduce random access.
What you will accomplish
Control who can join a Minecraft server and reduce random access. The goal is a repeatable result you can verify, not a pile of unexplained files.
- You know your Minecraft version
- You are using the correct loader or platform
- Important worlds are backed up
- The file came from an official project page
Protect the live server before changing it
Control who can join a Minecraft server and reduce random access. Server work affects other players, world data, permissions, and uptime. Use backups, maintenance windows, staging tests, and console logs before treating a change as finished.
Use this guide when the goal is set up a server whitelist. Work from a copy or clean instance when the task can affect saves, configs, servers, or account settings.
What to verify first
Before starting, write down the target Minecraft version, loader or platform, and the folder or account area this task changes. That small note makes rollback and support requests much easier.
After restart, join the server, test the affected feature, and read logs for warnings that were not visible in-game.
How to know you are finished
For set up a server whitelist, the work is not finished when a file is merely downloaded. Treat it as finished when you can point to the setup you changed, explain why it matches the intended Minecraft version or platform, and repeat the result in a clean test or copied world.
Use the checklist as the exit test: you know your minecraft version, you are using the correct loader or platform, important worlds are backed up. If one of those checks is still uncertain, stop and verify that detail before moving to a main world, public server, or shared pack.
If the first failure you hit is "Minecraft crashes after the change", start with this fix: Remove the last file you added, relaunch once, then check the latest.log or crash report for the missing dependency or wrong loader. This keeps recovery tied to the guide instead of turning into unrelated guesswork.
Step-by-step process
Open the server console or use an account with permission
Open the server console or use an account with permission.
Run /whitelist on to enable the whitelist
Run /whitelist on to enable the whitelist.
Add players with /whitelist add playerName
Add players with /whitelist add playerName.
Use /whitelist list to confirm entries
Use /whitelist list to confirm entries.
Save and restart if your host requires it
Save and restart if your host requires it.
Remove players with /whitelist remove playerName when needed
Remove players with /whitelist remove playerName when needed.
Verification checklist
You know your Minecraft version
You are using the correct loader or platform
Important worlds are backed up
The file came from an official project page
Whitelist is enabled
Player names are typed correctly
Troubleshooting
Remove the last file you added, relaunch once, then check the latest.log or crash report for the missing dependency or wrong loader.
Confirm the file is in the correct folder and is not trapped inside an extra zip/folder layer.
Test in a clean instance and add one file at a time until the issue returns.
Practical notes
- If a player cannot join, check spelling and account name changes.
- If whitelist commands fail, check operator permissions.
- If using a panel, make sure it edits the active server instance.
Official-source standard
FreeMinecraftMods does not mirror project files. When this guide involves a download, verify the creator, version, loader, file availability, license, and final official source before installing anything.
Read how project listings are reviewed or report a correction.