Troubleshooting & FAQ

Database connection fails

Check database host, port, credentials, TLS setting and database permissions. All network nodes must share the database and table prefix. Do not share SQLite over a filesystem. Login checks fail closed on database timeouts; chat and blocked commands fail closed when synchronization is over 10 seconds stale.

Template missing or denied

Grant wrongpunish.punish plus the next step's policy permission. Tab completion requires access to all configured step permissions; a currently permitted step can still be typed. Check duration limits, target exemptions and LuckPerms hierarchy.

Proxy mute does not block chat

Install the adapter on every backend. Proxy adapters deliberately do not cancel signed normal chat. Check mutes.enabled, blocked commands and shared database synchronization.

Duplicate broadcasts

Use broadcasts.delivery: BACKEND when both backend and proxy adapters are installed. ALL explicitly permits both.

Proxy GUI does not open

Check backend installation, enabled database sync, matching database/prefix and backend names matching the proxy's actual server names. Backend permissions are checked independently.

Reload fails

Read the reported file/property or YAML line and column. Fix the selected locale, GUI material/sound, slot overlap, alias collision or invalid policy before retrying. Successful reload closes existing inventories and clears reason prompts. Customized files do not automatically receive new defaults.

Which versions work?

See Installation for Java and platform requirements and Compatibility for testing guidance.