How to Whitelist Players on Your GlassHosting Minecraft Server

Why whitelist

A whitelist is the simplest privacy control for a friend SMP or family realm on GlassHosting. Only listed Java usernames (or UUIDs) can join. Combine whitelist with strong ops discipline so random scanners on the internet cannot wander your builds.

Enable and manage via console

1. Open your server console on panel.glasshosting.com.
2. Run whitelist on.
3. Add friends: whitelist add PlayerName (exact Java username).
4. Confirm with whitelist list.
5. Remove access: whitelist remove PlayerName.
6. Optional: set white-list=true in server.properties via file manager or SFTP so it survives rewrites consistently.

Example console flow:

whitelist on
whitelist add Alex
whitelist add Steve
whitelist list

Ops vs whitelist

Whitelist controls who can connect. Ops (operators) control who can run privileged commands. For a private realm, whitelist everyone you trust to play, and only op a small admin set. Use permission plugins later if you outgrow vanilla ops.

Bedrock-only realms and Geyser/Floodgate setups may need extra identity mapping—see our Geyser overview article and test one Bedrock friend before inviting the whole group.

Operational tips on GlassHosting

• Keep a text list of approved usernames in Discord or notes for when you rebuild.
• After restoring a backup, re-check whitelist and ops files.
• If a friend changed their Minecraft username, remove the old name and add the new one.
• Public GlassHosting servers that should be open must leave whitelist off and rely on anti-cheat/firewall practices instead.

GlassHosting does not publish your player list publicly; whitelist is entirely your configuration. When friends cannot join, verify whitelist first, then IP:port, then version mismatch.

Measure before you guess

Open the resource graphs on panel.glasshosting.com during a normal play window and during a busy one. Write down approximate CPU and memory percentages alongside how the game felt. That habit turns vague “it lags” reports into actionable upgrades or config tweaks.

If graphs look calm while players stutter, ask whether the issue is client FPS, wifi, or a single loaded farm chunk. If graphs are pegged, stop adding content packs until you either tune view distance/entities or upgrade the GlassHosting plan from the client area.

When to involve GlassHosting support

Open a ticket from billing.glasshosting.com when the platform itself looks wrong: panel cannot start the process, allocations seem missing, or multiple unrelated networks cannot reach the service. Include service name, timestamps, and console excerpts without secrets.

For game-logic questions (plugin conflicts, datapack design), include what you already tried. Skim related knowledgebase articles first—many “outages” are EULA flags, edition mismatches, or whitelist misses.

Backup discipline (repeat until boring)

Create a named backup before every risky change: version upgrades, mod installs, permission overhauls, or world-edit events. Download a copy of irreplaceable worlds over SFTP to your PC at least occasionally so you are not relying on a single storage location. After a restore, verify spawn, inventories, and plugin folders before declaring victory in Discord.

GlassHosting makes backups accessible in the panel—use them. A backup you never tested is only a hopeful file. Once per season, restore to confirm the process while the stakes are low.

Beginner pitfalls we see constantly

• Skipping the EULA or auth step and assuming the host is broken
• Installing dozens of plugins before the first successful join
• Sharing the wrong edition address (Java vs Bedrock)
• Editing files while the server is still writing them
• Reinstalling as a first step instead of reading the console

Slow down, read the console, backup first, and change one variable at a time. That pattern alone prevents most first-week disasters on GlassHosting.

Why leaving a home PC behind helps

Residential uploads, CGNAT, dynamic addressing, Wi‑Fi interference, and sleep schedules fight always-on multiplayer. Moving the authoritative server to GlassHosting lets everyone—including the former host—play as clients on equal footing.

Bring your world via SFTP, match versions carefully, run a two-player test, then announce the new address. Keep the old PC as a backup archive for a week, not as the live source of truth.

Networking notes for real humans

Friends should connect using the exact address shown in the GlassHosting panel. If one friend fails, have them try a phone hotspot to rule out school/work UDP or TCP filters. Home CGNAT and router forwards are irrelevant for a datacenter-hosted server—you should not be opening ports on your living-room gateway for a GlassHosting world.

Do not publish SFTP credentials, API keys, or admin passwords next to the game IP. Share join info in private channels, and update pinned messages when endpoints change.

Documentation habit

Keep a one-page note with: panel URL, who is lead admin, current game version, last backup name, and the exact join string. When you hand off admin duties, that note prevents accidental reinstalls and wrong-version clients.

Change windows

Batch non-urgent updates into a weekly maintenance window. Tell players ahead of time. After the window, post a short “what changed” message. Predictability builds trust in GlassHosting communities more than surprise restarts.

Related links: panel.glasshosting.com · billing.glasshosting.com · glasshosting.com.