Skip to main content

Channel Not Connecting

If a channel shows as Disconnected or Error in your dashboard after you have entered credentials, use this guide to diagnose the problem.

General Checks​

Before looking at channel-specific issues, verify these basics:

  1. Instance is running: Go to Instance and confirm the status is Running. A stopped instance cannot connect to any channel.
  2. Token was copied correctly: Re-paste the token to make sure there are no extra spaces, line breaks, or missing characters.
  3. Token is still valid: Tokens can expire or be revoked. Generate a fresh token from the platform and try again.
  4. Check the logs: Go to Instance > Logs for detailed error messages about the connection failure.

Telegram​

"401 Unauthorized"​

Your bot token is invalid. Common causes:

  • The token was copied incorrectly (missing characters).
  • The token was revoked. Send /revoke then /newbot or /token to @BotFather to get a new one.

Bot was deleted​

If you deleted the bot in BotFather, the token is permanently invalid. Create a new bot and use the new token.

Discord​

"Invalid token"​

  • Make sure you copied the bot token, not the client ID or client secret.
  • If you reset the token in the Developer Portal, the old token is permanently invalid. Copy the new one.

Bot is offline in the server​

  • Verify the token in your dashboard matches the current token in the Developer Portal.
  • Check that you enabled Message Content Intent under Bot > Privileged Gateway Intents. Without this, the bot connects but cannot read messages.

"Missing Access" errors​

The bot does not have permission to access certain channels in your server.

  • In Discord, right-click the channel > Edit Channel > Permissions.
  • Make sure your bot's role has View Channel and Send Messages permissions.

Slack​

"Invalid auth" or token errors​

Slack requires two tokens. Make sure you are pasting them in the correct fields:

FieldToken prefixSource
Bot Tokenxoxb-OAuth & Permissions page
App-Level Tokenxapp-Basic Information > App-Level Tokens

If you swapped them, the connection will fail. Double-check which token goes where.

Bot does not receive messages​

  • Verify Socket Mode is enabled in your Slack app settings.
  • Check that you subscribed to the correct events (message.im, app_mention) under Event Subscriptions.
  • Confirm the required scopes are added: chat:write, channels:history, im:history, users:read.

"not_allowed_token_type"​

This error means you are using the wrong token type. The app-level token (xapp-) must have the connections:write scope. Regenerate it if needed.

WhatsApp​

QR code expired​

WhatsApp QR codes expire after about 60 seconds. If the QR code disappears or says it is expired:

  1. Click Disconnect in the dashboard.
  2. Click Connect again to generate a fresh QR code.
  3. Scan it promptly with your phone.

"Connection closed" after scanning​

This can happen if another device is already linked. WhatsApp limits the number of linked devices. Try unlinking an unused device from WhatsApp > Settings > Linked Devices on your phone, then reconnect.

Signal​

Connection fails immediately​

Signal requires a linked account via the Signal CLI. This is a more advanced setup. Make sure:

  • Signal CLI is properly configured in the instance.
  • The phone number is registered and verified.
  • Check logs for specific Signal error messages.

Still Not Working?​

If none of the above resolves your issue:

  1. Try disconnecting and reconnecting the channel in the dashboard.
  2. Restart your instance from Instance > Restart Instance.
  3. Check the logs for specific error messages.
  4. Contact support with the channel name, error messages, and relevant log entries.