Problem centre
Troubleshooting Centre
Diagnose Discord, hosting, runtime, database, FiveM, Google, OAuth, API, and permission problems.
Use a consistent diagnostic order#
- Read the first error in the console, not only the final shutdown message.
- Confirm the required runtime version and dependency installation.
- Check that every required variable or configuration value exists and contains the correct type of value.
- Test network access to Discord, the database, FiveM server, backend, or external service.
- Confirm Discord intents, invite scopes, bot role hierarchy, and channel permissions.
- Restart once after corrections and capture the new error if the problem remains.
Common problems#
| Problem | Likely cause | How to check | How to fix |
|---|---|---|---|
| Slash commands missing | Wrong application ID, missing scope, or sync delay | Check invite scopes and startup logs | Invite with applications.commands, correct the ID, restart, and allow global propagation time. |
| MySQL connection fails | Wrong credential, blocked remote access, or missing grant | Compare each credential and provider access list | Correct values, grant the database user, and allow the bot host. |
| Bot immediately exits | Missing variable, unsupported runtime, or dependency error | Read the first console traceback | Install the required runtime/dependencies and supply the named variable. |
| FiveM shows offline | Host or port unreachable | Open or query the standard JSON endpoint from the bot host | Correct address/port and allow network access. |
| Role action fails | Bot role is too low | Inspect Discord role order | Move the bot role above the managed role. |
| Protected API rejects requests | API key, timestamp, nonce, signature, or shared secret mismatch | Compare sanitized server logs on both sides | Synchronize secrets and signing rules; never disable validation. |
When to contact support#
Contact support after recording the product, runtime version, hosting type, exact error text with secrets removed, the step that triggers it, and the checks already completed. Do not include bot tokens, database passwords, API keys, OAuth secrets, or private service-account credentials.