Direct answer

Check enable-command-block=true in Java Edition server.properties, then restart the server. Verify command syntax and whether region/plugin restrictions are blocking the command block.

What it means

Disabled command blocks cannot execute even if a player has permission to place one. Other failures result from activation, the command itself, or permissions in a protected world.

If you are a player

  • Ask whether the command block can be placed and whether it activates when powered.
  • Do not ask for unrestricted operator access; provide the specific failed command and location.

If you run the server

  1. On a Java Edition server, set enable-command-block=true and perform a full restart.
  2. Test a simple command block in an isolated test world with a known-good redstone trigger.
  3. Check whether the command requires coordinates, dimensions or selectors that differ from console use.
  4. If the block executes but its effect fails, inspect plugin permissions, WorldGuard restrictions and the current server log.

Confirm the fix: Do not enable arbitrary command-block access for untrusted builders; commands can alter player data and world state.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000