# Troubleshooting ### Widget not appearing on my site Check that the `data-key` attribute in your script tag matches the API key shown in your project's Embed section. The key starts with `pk_live_`. Also confirm the script tag is in the ``, not the ``. Your project may not be linked. Open the project in the dashboard. If the status shows **Not linked**, click **Link Telegram** and complete the flow. The bot must be in the group and have admin rights. ### Origin mismatch error The domain saved in your project settings must exactly match the domain your site runs on. Enter it without `https://` and without a trailing slash. For example: `example.com`, not `https://example.com/`. Subdomains count as different domains. The bot needs admin rights. Open your Telegram group, go to **Administrators**, find the bot, and ensure it has permission to manage topics, post messages, and delete messages. Without these, topic creation fails silently. ### I set up forwarding in Gmail but no email arrives Almost always the last step. Go back to Gmail's **Forwarding and POP/IMAP** tab and check that **Forward a copy of incoming mail to** is actually selected, then scroll down and click **Save Changes**. Verifying the address does not switch forwarding on by itself, and Gmail throws the setting away if you leave the page without saving. After that, send yourself a test email from a different account. Only mail arriving after you saved gets forwarded. This is Gmail failing before it sends anything, not a problem with your Bubblegram address. The usual cause is being signed into several Google accounts in the same browser: open an incognito window, sign into just the one account, and try again. On Google Workspace, forwarding may be disabled for your organization, in which case your admin needs to allow it under Admin Console > Apps > Google Workspace > Gmail > End User Access. Ad blockers and privacy extensions can also break the verification popup. If you've tried several times in a row, wait an hour before retrying. Click **Re-send email** next to the pending address in Gmail and watch the Email tab. The code appears within a few seconds and is also posted to your Telegram group. If it still doesn't show up, the confirmation never reached us, which usually means the address was pasted with a typo. Compare it against the address on the Email tab character for character, or remove it in Gmail and add it again. ### My test email never showed up in Telegram Check what you sent. Newsletters, notifications and anything from a `noreply@` address are filtered out on purpose, so they make a poor test. Send an ordinary message from a personal mailbox instead. Also confirm your plan is still Pro: on the Free plan the email channel is set up but incoming mail is not delivered, and we post a notice in your Telegram group once a day when that happens. ### Replies are coming from noreply@mail.bubblegram.co That's the default sender until your own domain is verified. Finish step 3 on the Email tab by adding the SPF, DKIM and DMARC records at your registrar. Until all three verify, replies still send and still thread correctly, they just come from our address rather than yours. ### Link token expired Link tokens are valid for 10 minutes. If you waited too long between generating the token and completing the setup, go back to your project in the dashboard, click **Link Telegram** again, and use the newly generated token.