Set up a whitelist on a Minecraft server

A Minecraft whitelist, also called an allow list, restricts access to a server to the players you have authorized. It is a simple setting for a private server among friends, a community that is just launching, or a testing phase. This guide explains how to enable it, add and remove players, then verify that the filtering works without confusing whitelist, operator, ban, and network settings.

Before you begin

You must be able to administer the server's files or use its console. Back up the configuration file before any modification and note the exact name of the players to authorize. On Minecraft Java Edition, the name used by the whitelist must match the player's account identifier. A typo or a username change can therefore block a legitimate connection.

The whitelist filters players after their connection attempt. It does not fix an incorrect IP address, a misconfigured domain name, a closed port, or a stopped server. Before inviting your community, verify that the server responds from another network and that the address you share points to the right machine.

The whitelist does not replace general security. Use a strong RCON password if RCON is enabled, limit administrative access, and keep the server up to date. To choose a machine suited to your project, see our guide on hosting a Minecraft server.

Choosing the server environment

A Minecraft server can be installed on a personal computer, a VPS, or a dedicated server. On a Linux VPS, administration is often done remotely with SSH and a root or sudo account. On Ubuntu or Debian, keep the system and packages up to date before exposing the server to the Internet. The available CPU, RAM, SSD storage, and bandwidth affect smoothness when several players explore the world or load areas.

The firewall must allow the intended game port without unnecessarily opening administration ports. A secure remote connection, an SSH key, and separate accounts reduce the risk of error. The whitelist concerns Minecraft connections, while the firewall protects the machine's services. For other protection settings, see the first security settings for a dedicated server.

If you go through a hosting provider, ask where the files, logs, and backups are kept. A control panel can simplify installation, updates, and console access, but the administrator must always know which instance is active. Check the available disk space, the date of the last backup, and the ability to recover the configuration without depending on a single machine.

The choice between a physical server, a VPS, and a cloud server depends on the number of players, the budget, and the flexibility you need. Virtualization lets you isolate several servers on the same infrastructure, but each instance must keep its own files, ports, and backups. If you run several Minecraft servers, give each one a clear configuration and test the accesses separately.

Configuring maintenance and administration

To manage a virtual server, document the configurations that concern the game, the network, and the backups. Note the path of the world, the startup scripts, and the processor and memory reserved for Java. This sheet makes recovery easier when the virtual machine restarts or when an administrator must intervene remotely.

Schedule updates during a quiet period, check the storage space, and keep several backups. A high-availability backup does not remove the need for a restore test. If the server changes machines, compare the IP address, the DNS, the ports, and the whitelist files before reopening player connections.

Enabling the whitelist in the configuration

Stop the server cleanly before modifying its configuration. In the server.properties file, look for the white-list property. Set it to true, save the file, then restart the server. The value must be written without unnecessary spaces and with the syntax the file expects.

After restarting, check the console and try a connection with an authorized account, then with an account that is not on the list. Don't test only from the administration console: an operator can have special rights and give a misleading impression of the result.

If you use a control panel, the same operation may appear as a "Whitelist" checkbox. The panel must not be considered sufficient proof: always check the configuration the server actually loaded and the startup log.

Adding an authorized player

The server console generally accepts the whitelist add NomDuJoueur command. Replace NomDuJoueur with the exact account name, without adding a comment. You can then check the list with whitelist list. If your interface offers a dedicated button, use it only after confirming that the corresponding command was actually executed.

Add players one by one when you are preparing an opening. This method reduces errors and makes diagnosis easier. Send the connection details to the player through an appropriate channel, without publishing the server's IP address in an open space if your goal is to keep the community private.

A whitelist concerns access to the game server. It does not automatically grant operator permissions. Keep elevated rights for identified administrators and explain to each team member the difference between connection authorization and command permission.

Removing a player and checking access

To revoke an authorization, use whitelist remove NomDuJoueur, then verify the result with whitelist list. Removing someone from the whitelist is not a ban. If a player is already connected, check their status after the change and apply the measure suited to your administration policy.

Keep a record of important changes: date, administrator, reason, and test result. A short written procedure avoids mistakenly re-authorizing an old account and helps resolve access requests quickly. For backups, see our guide to dedicated server backups.

Troubleshooting common problems

If an authorized player cannot get in, first check the exact spelling of their name, the game version, the address used, and the server log. Also confirm that the whitelist is enabled on the server the player is connecting to, not on a local copy or another environment.

If the server is visible but the connection times out, check the IP address, the domain name, the configured port, and the machine's firewall. A Minecraft server installed on a VPS or a dedicated server must accept the necessary traffic on its network interface. DNS can also keep an old address for some time after a change. These checks are about network access, not the whitelist.

If an unauthorized player manages to connect, check the active value after restart, the loaded list, and any proxy placed in front of the server. A proxy or a multi-server architecture may require separate configuration on each instance. Don't grant operator rights to work around a whitelist problem: the operator has administrative privileges and this is not a filtering solution.

Finally, back up the configuration files regularly and test their restoration. Our guide on Pterodactyl backups details a method for checking backups and restoring. To compare the resources you need, also see VPS vs dedicated server and our Minecraft hosting solutions.

Checklist before opening

• the whitelist is enabled in the loaded configuration;
• the names of authorized players have been checked individually;
• a positive test and a negative test have been performed;
• the IP address, DNS, port, and firewall have been checked;
• SSH access and administration accounts are protected separately;
• the CPU, RAM, SSD storage, and bandwidth are adequate;
• the server configuration and data are backed up;
• the add and remove procedure is known to the administrators.