Confirm the official destination, the current access rules and your exact Java profile name. If approval is missing or does not match, the server team must resolve it. A client setting cannot grant whitelist access.
What “not whitelisted” means
A whitelist is a server-controlled list of permitted players, also commonly called an allowlist. Paper’s server documentation describes its whitelist setting as limiting connections to selected users. When you receive a not-whitelisted message, start with admission approval—not graphics settings.
A community may use an application, invitation or temporary testing window. These are possible policies, not universal Minecraft requirements. Read that server’s current instructions. Joining its Discord or receiving a Discord role is not, by itself, evidence that your Minecraft account has been approved.
Make sure this is an access problem
Copy the complete message before changing anything. Similar-looking disconnect screens can need different fixes. This table routes the next check; it is not a guarantee of the underlying cause on a customized server.
| Message or situation | Next check |
|---|---|
| Not whitelisted / not on the allowlist | Confirm access approval for this account and this destination. |
| Incompatible or outdated version | Match the edition and release required by the server. |
| Unknown host / unresolved address | Compare the saved address with the official joining instructions. |
| Timed out / connection refused | Check service announcements and the connection, rather than assuming a whitelist. |
| A ban or suspension notice | Use the stated appeal route; a whitelist request is not an appeal. |
Four checks you can do yourself
Official Minecraft guidance uses “Java profile name” to identify a player in Java. Do not assume every name displayed across your launcher, Discord and other services is interchangeable. You only need to identify the game account; staff do not need your sign-in secrets.
This guide is aimed at Java server admission. If the community explicitly supports Bedrock cross-play or you are joining a Realm, use its specific invitation and identity instructions. Do not invent a username prefix or copy an administrator command from an unrelated platform.
- Destination: compare your saved server address with the latest official announcement, including any supplied port. Do not substitute an old test address or a website URL.
- Access: read whether applications are open, whether your request is still pending, and whether approval applies to a particular event or test.
- Identity: check the Minecraft account used by the game you launched. Give staff the exact Java profile name, not an assumed Discord nickname or account email.
- Confirmation: compare the name and destination in the approval message with the account and server entry you just checked. Ask about any discrepancy before retrying.
Already approved, but still rejected?
Here is a hypothetical example: staff approved CloudBuilder, but the game on a shared computer was launched with IslandCrafter. Reconnecting repeatedly with IslandCrafter would not resolve that approval mismatch. First confirm which of your own accounts should be used; do not rename an account or borrow somebody else’s login as a workaround.
If the account and destination match, reply in the original official support conversation. Ask staff to check whether approval has been applied to the actual server you are reaching. They can examine their admission system and logs; you cannot determine its internal state from the disconnect message alone.
- If you recently changed your Java profile name, mention both the approved name and the current one. Let staff decide whether their records need attention.
- If access worked previously, include the last successful connection time and any relevant official maintenance announcement.
- Wait for confirmation that the change is applied, then make one controlled retry. Record the new error if it differs.
Send staff a report they can check
A cropped screenshot of the error can help. Review it for account emails, private chat, other players’ details and anything unrelated before sending. Never include passwords, recovery codes, browser cookies or authentication tokens. Minecraft’s official safety guidance explicitly warns against sharing account passwords.
| Field | What to include |
|---|---|
| Request | “Could you check my access approval for this server?” |
| Game account | Your exact current Java profile name and the name originally approved, if different. |
| Destination | The official server entry or event you intended to join. Keep private test addresses in the private ticket. |
| Attempt | Date, time and timezone, plus the complete disconnect message. |
| Client | Java Edition and the complete launched version; mention a required modpack if relevant. |
| Approval | The existing ticket or approval reference, and whether this account connected successfully before. |
| Checks already done | “I compared my account and saved address with the official instructions.” |
Know when to stop troubleshooting
If applications are closed or approval is pending, waiting for the operator is the correct next step. Reinstalling Minecraft, lowering render distance or repeatedly changing versions does not add your account to an admission list. Do not disable security software, use a supposed whitelist-bypass download or ask staff to remove server protections.
Once staff confirms access and you retry with the intended account, treat any different error as a new clue. Use the joining or version-mismatch guide for that next stage instead of continuing to diagnose every disconnect as a whitelist issue.
Aetheria is still in development. This general guide does not announce an Aetheria whitelist application, public server address, access entitlement or launch date. Follow the official Aetheria announcements for confirmed joining details.
References & further reading
These are general guides, not a claim that every server uses vanilla mechanics. Check your server’s own rules and supported version.