What enforce-secure-profile Does on a Minecraft Server

Direct answer

The enforce-secure-profile property controls whether connecting players must provide Mojang-signed public profile keys. Changing it is not a general solution for timeout or username-authentication failures.

Recommended procedure

1. Open server.properties on the actual Java backend you intend to configure.
2. Check the current enforce-secure-profile value and whether the proxy, client versions and chat plugins are compatible with it.
3. For a normal authenticated Java server, prefer the secure default supported by your software and use official documentation before disabling it.
4. If a trusted proxy network has a specific compatibility requirement, verify its documented player information forwarding and backend configuration.
5. Restart the server after a controlled change, then test multiple normal player accounts.

Why this matters

Secure profiles concern signed identity keys, not whether a router port is open. A player rejected for version mismatch, missing mods or authentication timeout needs a different diagnosis.

Practical example: Example: if only one modified or outdated client is rejected but normal current clients connect, the issue may be client capability rather than server-wide secure-profile enforcement. Changing enforce-secure-profile has a security tradeoff and may not affect the real error. Keep a saved config and compare exact login logs when evaluating any change.

How to verify the result

• Check whether eligible Java accounts can log in and chat normally.
• Review the exact disconnect message before and after, not only the broad category of connection failure.
• Revert changes that weaken security without fixing a documented compatibility issue.

Version and compatibility notes

• Available defaults and behavior can vary with Java version, Minecraft version and proxy configuration.
• Do not switch online-mode off as a shortcut for a secure-profile rejection.

Official references

These sources were checked for the current MSH revision. Version-sensitive details should always be confirmed against the project documentation for the release you run.

• Paper server.properties reference
• Paper configuration

Related guides