What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Prefer not to run the server on your own PC? Godlike.Host offers hosted Minecraft Java servers with free DDoS protection and up to three free backups a day.
To disable the server-side requirement that enables signed chat reporting, stop your Java Edition server, open server.properties, change enforce-secure-profile=true to enforce-secure-profile=false, save the file, and restart the server. This allows players without Mojang-signed profile keys to join. It does not make every chat message reportable: messages from unverified players and unsigned system messages cannot be reported to Mojang.
This setting applies to Minecraft Java Edition servers. Bedrock Edition was not covered by the available documentation, so do not assume the same file or option exists there.
What disabling chat reporting actually changes
Minecraft’s enforce-secure-profile option controls whether connecting players must present a valid Mojang-signed public key. The server’s default is true. With that value, a player who has no signed key cannot join, and a key that is missing, expired, invalid, or badly signed is rejected during connection.
Chat reporting relies on signed player messages. When you set the option to false, the server no longer requires every player to have a verified key. Players with unverified profiles can therefore connect, but their messages do not have the verification needed for Mojang reporting. The change is best understood as removing a join requirement, not as a universal switch that erases every reporting control in every client.
#1 Best Overall
enforce-secure-profile |
Who can join | Reporting consequence |
|---|---|---|
true (default) |
Players must present a valid Mojang-signed public key. Missing or invalid keys are rejected. | Signed player messages can participate in the reporting system. |
false |
Players without verified keys can join, subject to the server’s other authentication and access settings. | Messages from unverified players cannot be reported to Mojang; unsigned system messages also cannot be reported. |
The setting does not turn off moderation for every kind of message, and it does not guarantee that a report button disappears from a player’s client. Whether the client-side report control remains visible for signed players is not firmly established, so treat that behavior as client- and message-dependent.
Before you edit the server
Confirm that this is a Java Edition server
The option is a Java server property. The available information does not establish an equivalent procedure for Bedrock Edition. If your server is Bedrock, look for edition-specific documentation rather than creating a Java-style server.properties change that may be ignored.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsCheck that you can stop and restart the server
The property is read when the server starts. Plan a maintenance window, notify players, and use the host’s normal stop function instead of terminating the process while it is writing world data.
Make a backup of the configuration
Copy server.properties before editing it. Keep the original copy outside the active server folder or give it a clearly different name. This makes it easy to restore the previous value if another setting is changed accidentally.
Use plain text editing
Open the file with a text editor that does not add rich-text formatting. Preserve the property name, equals sign, and lowercase value exactly as shown. Do not add quotation marks around false.
Step-by-step: set enforce-secure-profile=false
- Stop the server cleanly. Use the server console’s stop control or your hosting panel’s Stop button. Wait until the process has fully stopped before opening the file.
- Open the server folder. Locate the same directory that contains the server’s world folders, startup files, and
server.properties. - Open
server.properties. Search for the lineenforce-secure-profile=true. On a newly created server, the property should normally be present with the default valuetrue. - Change only the value. Replace the line with
enforce-secure-profile=false. Keep the spelling and hyphens inenforce-secure-profileunchanged. - Save the file. Confirm that the editor did not save a second extension such as
.txt. The active file must remain namedserver.properties. - Start the server again. Use the normal start command or hosting-panel control and wait for the server to finish loading.
- Test a connection. First connect with an account that previously failed because it lacked a verified profile key. Then check the console for the absence of the secure-profile rejection and confirm that ordinary players can still join.
Some managed hosts expose the same property as a checkbox or text field in a configuration panel. If you use that interface, set the secure-profile requirement to disabled or set the underlying value to false, apply the change, and restart. If the panel overwrites manual edits, make the change in the panel rather than editing a generated file.
What players see before and after the change
When the value is true
A client with no Mojang-signed public key is disconnected instead of being admitted. The same can happen when the presented key is invalid, expired, or incorrectly signed. Connection logs may refer to an invalid signature or a profile public-key problem. Those messages indicate a verification failure, although the exact wording can vary by server and client version.
When the value is false
The server stops enforcing the signed-key requirement at join time. A player who lacks a verified key can connect, assuming the player passes the server’s other checks. The server still receives chat and system messages, but an unverified player’s chat is not eligible for Mojang reporting because it lacks the required signature.
Rank #3
- The classic UNO card game builds fun on game night with a Minecraft theme.
- UNO Minecraft features a deck and storage tin decorated with graphics from the popular video game.
- Players match colors and numbers to the card on top of the discard pile as in the classic game.
- The Creeper card unique to this deck forces other players to draw 3 cards.
- Makes a great gift for kid, teen, adult and family game nights with 2 to 10 players ages 7 years and older, especially Minecraft and video game fans.
Signed and unsigned messages are different
Turning off enforcement does not transform unsigned text into signed text. A player who does have a valid key may continue to send signed messages, while an unverified player sends messages without that verification. Custom chat plugins that use the System Chat Message packet also send unsigned messages; those messages cannot be reported through Mojang’s signed-message reporting mechanism.
Security and moderation trade-offs
The main benefit: broader account compatibility
Disabling enforcement is useful when legitimate players are being blocked by missing or unusable profile keys. It can also help when a server’s connection path, launcher arrangement, or account setup produces verification failures that the server owner cannot resolve quickly. The practical result is that the server accepts a wider range of profiles.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchThe main cost: unverified accounts are admitted
The same change that admits affected players also admits any other account that does not present a verified key. You therefore lose the guarantee that every connected player is participating with a key the server can verify. Consider this a security and trust trade-off, not merely a cosmetic chat preference.
Reporting coverage becomes mixed
On a server with enforcement disabled, reporting capability depends on how a message was produced. Signed messages from verified players retain the relevant verification, while messages from unverified players cannot be reported to Mojang. Unsigned system messages generated by plugins are likewise outside that reporting path.
Rank #4
- Now Minecraft lovers can play a special version of UNO!
- Same as Basic UNO but features Minecraft characters and includes special Creeper rule card. Draw this card and the other players have to draw three more cards from the pile!
- The goal is to get rid of all the cards in your hand.
- First player or team to 500 wins.
- When you're down to one card, don't forget to yell "UNO"!
Do not promise that the report button vanishes
The available evidence does not establish whether the client-side report button disappears for signed players after this server change. Avoid telling players that all reporting UI will be removed. The reliable, server-side effect is the removal of the mandatory signed-key check and the resulting inability to report messages that are not signed.
Version and default-value notes
The final Minecraft 1.19.1 release is generally treated as using true by default. There is an important pre-release distinction: an analysis of 1.19.1-pre1 described the default as false, while a later account states that the option has been true from 1.19.1 onward. Pre-release builds and final releases can differ, so use the value actually present in your server’s file rather than relying on a version assumption.
Free tools Windows power users keep installed
One-click scans. No signup required.
If the property is absent, first verify that you are editing the active Java server’s file and that the server version supports the option. Do not add unrelated properties or copy a value from a different server instance without checking which startup directory is in use.
Troubleshooting after changing the property
The same invalid-signature error still appears
- Stop the server again and confirm the active file contains exactly
enforce-secure-profile=false. - Check for duplicate lines. If the file contains the property more than once, remove the duplicate and leave one unambiguous entry.
- Make sure the editor did not save
server.properties.txtor a second copy in another directory. - Verify that the hosting panel is not regenerating the file from a separate configuration value.
- Restart the server after every change; editing a running file does not reload the property.
Players can join, but chat still cannot be reported
This is expected for messages from players without verified keys. Disabling enforcement allows those players to connect; it does not provide a signature that was never present. The same limitation applies to unsigned system messages sent by custom chat plugins.
The property keeps returning to true
- Look for a host-panel setting that controls secure-profile enforcement and change it there.
- Check whether a startup script, container image, or provisioning tool rewrites
server.propertiesduring boot. - Confirm that you are editing the instance the panel actually starts, especially if several server folders exist.
- Stop the server before saving, then restart from the same control surface used to stop it.
One player still cannot connect
With enforcement disabled, the signed-key requirement is no longer the explanation for that specific rejection. Check the remaining server checks, including allow-list status, bans, authentication mode, network reachability, and client/server version compatibility. The property only governs the secure-profile requirement; it does not override other access controls.
A plugin’s chat behaves differently
Identify whether the plugin sends a signed player message or an unsigned System Chat Message packet. Unsigned plugin-generated messages cannot be reported through the signed-message mechanism, regardless of whether secure-profile enforcement is enabled.
How to re-enable the requirement
To restore the original policy, stop the server, change the line back to enforce-secure-profile=true, save the file, and restart. Players without valid Mojang-signed keys will again be rejected. If you used a host panel, re-enable the corresponding secure-profile option there and apply the restart.
After re-enabling it, test with a verified account and with an account that previously lacked a key. Keep the backup you made before editing until both tests and the server logs show the intended behavior.
Alternatives to changing the server property
Keep enforcement enabled and fix the affected profiles
If your priority is retaining the signed-key requirement, leave the property at true and investigate why a particular player’s key is missing, expired, invalid, or badly signed. This preserves the narrower admission policy but may require the affected player to correct the account or client condition that caused verification to fail.
Evaluate a third-party “No Chat Reports” mod
A third-party Modrinth mod with that name exists, but its compatibility and exact behavior were not verified here. Treat it as a separate software choice, not as an equivalent one-line server setting. Check that its Minecraft version, loader, server/client placement, and interaction with your plugins are explicitly supported before deploying it, and test on a copy of the server first.
Recommended Free Tools
Use plugin-specific controls carefully
A chat plugin may alter whether messages are signed by choosing a system-chat packet. Such a plugin can change reporting eligibility for its own messages, but it does not replace the server’s enforce-secure-profile decision about who may join.
Quick Recap
Recommended decision checklist
- Choose
falsewhen allowing players without verified keys is more important than requiring every player to present one. - Keep
truewhen your server depends on the narrower, verified-profile admission policy. - Explain the consequence to players: unverified players can join with enforcement disabled, but their messages are not reportable through Mojang’s signed-message system.
- Test plugins separately: unsigned system messages remain unreportable even when a player account is otherwise verified.
- Document the change: record the old value, the new value, the restart time, and the result of a test connection so another administrator can reverse it safely.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
