If OnyxBot is missing from your server's member list, the invite most likely never finished. OnyxBot is saved only when Discord's Authorize screen completes and redirects back to your dashboard, so a cancelled invite leaves nothing behind. Re-run the invite from your OnyxBot dashboard, then check the Connected Server card on Configuration, which shows Online, Offline, or Error.
How do I re-run the invite?
- Open Configuration in the dashboard sidebar, under AI.
- If no server is connected yet, press Connect server. On a paid plan the button is Get started, which opens a dialog with Shared bot and Custom bot tabs. If your account has no server at all, the dashboard shows a checklist instead, and step one, Connect your server, has a Connect button.
- If a server is already connected, open the server switcher at the top of the sidebar and choose Add server.
- On Discord's Authorize screen, leave every permission ticked and finish the flow.
Cancelling sends you back with "Bot invitation was cancelled." An old bookmark, or a link you built in the Discord developer portal, reports that the connection link was invalid or expired. The dashboard buttons always generate a fresh link, so start there, not from a bookmark.
If you unticked permissions, OnyxBot joins but cannot open tickets: it needs Manage Channels and Manage Roles. On the shared OnyxBot, the dashboard then shows an amber Action needed banner with a Re-authorize button. It takes one click, and nothing is removed or reset.
Where does the OnyxBot role position matter?
It matters where OnyxBot acts on other roles. For Tebex customer roles to sync, the OnyxBot role must sit above every role mapped to a package. Separately, a Discord category that does not allow OnyxBot to view and manage channels blocks ticket creation in that category, even when server-wide permissions look fine.
What does the status dot mean?
On Configuration, the Connected Server card shows Online (green), Offline (grey), or Error (red). One caveat: on Free, or on a paid plan without the dedicated bot add-on, your server is served by the shared OnyxBot, so that dot reports the shared service overall, not your server on its own.
The dashboard is showing a different server
Every dashboard page is scoped to one server. The sidebar switcher shows the active one and lists the rest under Servers. If the invite says the server is already connected to a different account, log in with the account that originally added it.
My dedicated bot will not start
With the dedicated bot add-on, Configuration names the cause in a red alert:
- Message Content Intent is disabled. Enable it in the Discord Developer Portal under your bot's Bot settings, then press Retry Connection.
- Discord rejected the bot token. This happens right after the token is reset in the Developer Portal. Press Enter new token on the alert (or Replace token on the Your bot card), paste a fresh token from your application's Bot settings, and OnyxBot restarts your bot with it.
- Startup is rate-limited by Discord. Wait a few minutes, then press Retry Connection.
Retry Connection allows 3 attempts with a 60 second cooldown between them, then points you at support. A rejected token has no retry button, because only a new token can fix it. If the $7/mo add-on is inactive, an amber notice says so, and the shared OnyxBot keeps serving the server, so tickets and AI replies keep working.
My ticket buttons reply with a message that is not from OnyxBot
If pressing Close or Claim on your dedicated bot answers with something like "No handler available for this interaction", another program is signed in with your bot's token. Discord sends every click to every program using the token, and only the first answer counts, so that program answers before OnyxBot can.
Find what else runs on the token (txAdmin's Discord bot, another bot, a hosting panel) and turn it off or give it its own application. If you cannot find it, reset the token in the Discord Developer Portal, since resetting signs every other program out, then paste the new one with Replace token on Configuration. Until then, close tickets from the dashboard: open the ticket under Tickets and press Force close.