Skip to main content
If a channel won’t connect, the good news is that the error message almost always tells you exactly what to fix. Most connection failures are permission or account-setup issues on the platform’s side (Facebook, Instagram, LINE), not a problem with Cura. Find the message you’re seeing below and follow the steps.

Before you begin

  • Go to Integrations → Channels and start the Add Channel flow again so you can read the exact error.
  • Have the right admin access ready: for Messenger / Instagram / WhatsApp, log in with the Facebook account that administers the Business Page; for LINE and Telegram, have your console credentials to hand.

Meta channels (Messenger, Instagram, WhatsApp)

Messenger, Instagram, and WhatsApp all connect through the same Facebook login and permission screen, so they share the same handful of errors.

”No Facebook Pages found” (Messenger)

What you see: After logging into Facebook in Cura’s popup, you get “No Facebook Pages found for this account.” or “Failed to fetch Messenger page or no pages found” and no inbox is created. Why it happens: Facebook only shows Cura the Pages that the logged-in user administers. If you’re not an Admin of the Page — or you logged in with the wrong Facebook account — the Page simply doesn’t appear, so there’s nothing to connect.
1

Log in with the Page admin account

In Cura’s connect popup, make sure you’re signing in with the Facebook account that is an Admin of the Business Page.
2

Confirm your Page role in Meta

In Meta Business Suite → Settings → People, check that your user has full / admin control of the Page. If not, have an existing admin grant it.
3

Retry the connect

Back in Cura, run Add Channel → Messenger again. Your Page should now appear.
Once you can select the Page, the connection completes and the inbox is created.

”Missing required permissions” (Messenger, Instagram, WhatsApp)

What you see: You finish the Facebook consent dialog, but Cura shows “Missing required permissions: …” and refuses to connect. Why it happens: Each channel needs a specific set of permissions to work — for example Messenger needs page messaging access, WhatsApp needs WhatsApp business management, Instagram needs Instagram message access. On Facebook’s blue permission screen there’s an Edit access option, and if you untick even one requested item, a required permission is missing and Cura stops before creating any inbox.
1

Start the connect again

Return to Add Channel and begin the flow for the same channel.
2

Leave every permission toggled ON

On Facebook’s blue permission screen, click Edit access and make sure every requested item stays ON. Don’t deselect Pages, WhatsApp, or Instagram messaging access.
3

Complete the flow

Finish the dialog. With all permissions granted, the connection goes through.
If you still see “Missing required permissions”, you likely unticked an item again — retry and leave the toggles alone.

”No Instagram Business Account found” (Instagram)

What you see: Add Instagram fails with “No Instagram Business Account found linked to your Facebook Pages.” Why it happens: Cura can only connect an Instagram account that is a Business or Creator account and is linked to a Facebook Page you administer. A personal Instagram account, or a professional one that isn’t linked to any of your Pages, can’t be found.
1

Switch Instagram to a professional account

In the Instagram app: Settings → Account type → switch to Business or Creator.
2

Link it to a Facebook Page you admin

In your Facebook Page settings → Linked accounts, link that Instagram account to a Page you administer.
3

Reconnect in Cura

Run Add Channel → Instagram again. The Instagram account will now be found.
Instagram DMs will start arriving in the Inbox once the account is professional and linked to your Page.

The Facebook popup closed or you clicked Cancel

What you see: The login popup closes immediately, or you get “User denied permission” / “Login failed”, and nothing connects. Why it happens: The Facebook dialog was cancelled or denied, or the Facebook login script never loaded — often because an ad-blocker or tracker-blocker got in the way.
1

Allow popups and disable blockers

Allow popups for app.cura.so and turn off any ad-blocker or tracker-blocker for that site.
2

Click Continue, not Cancel

Retry, and click Continue / Allow all the way through Facebook’s dialog. Make sure you’re signed into the correct Facebook account.
When you complete the dialog without cancelling, the connection proceeds.

A generic server error asking you to contact support

What you see: The connect fails with a generic server error before any inbox is created, and there’s nothing about Pages, permissions, or accounts to fix. Why it happens: This is a Cura-side configuration issue (a missing platform setting), not something you did wrong. There’s nothing on your account you can change.
This one is on us, not you. Contact support@cura.so and include the date and time you tried to connect and which channel it was. Our team will fix the platform setting and let you know when to retry.

LINE and Telegram prerequisites

LINE and Telegram don’t use the Facebook login. They connect with credentials you copy from their own consoles, so the connection itself rarely fails — but it needs the right details.

LINE

LINE needs three values copied from the LINE Developers Console, and one manual step:
  • Channel ID, Channel secret, and a long-lived Channel access token — all pasted into Cura.
  • After connecting, you must paste Cura’s webhook URL into the LINE Developers Console yourself and turn on “Use webhook”. Cura can’t register a LINE webhook automatically, so if you skip this, LINE connects but no messages ever arrive.
See Connect LINE OA for the full walkthrough.

Telegram

Telegram needs a single bot token from BotFather. Cura tries to register the webhook for you, but if the token is wrong or already used by another server, the bot won’t forward messages. See Connect Telegram.
If a channel connects but never receives messages, it usually isn’t a connection error — see A channel shows as disconnected, which covers webhook and credential checks for LINE and Telegram.

Still stuck?

If you’ve matched your error above and it still won’t connect, contact support@cura.so. Include the channel, the exact error message, and the time you tried — that’s enough for us to trace it.