Skip to content

Troubleshooting

12. Troubleshooting

⚠ "Invalid token format"

Cause: The bot token you pasted is malformed.

Fix: Go back to BotFather, find your bot using /mybots, and copy the token again. Make sure there are no extra spaces before or after it. A valid token looks like: 123456789:ABCdefGHIjklMNOpqrsTUVwxyz-1234567

⚠ "This bot is already registered. Use Update Existing mode."

Cause: You selected Register New Bot but this token was already registered in the system.

Fix: Switch to Update Existing mode at the top. If you are setting up a genuinely new bot, make sure you are using the correct (new) token from BotFather.

⚠ Channel does not appear automatically in Register mode

Cause: The bot was either added to the channel before clicking Validate (Rufoof only detects the channel at the moment of joining, not before), or the wrong bot was added.

Fix: 1. In Telegram, go to your channel → Administrators → remove the bot. 2. In Rufoof, click Validate and wait for the green confirmation message. 3. Go back to Telegram and add the bot as an Administrator again — the channel should appear in Rufoof within a few seconds. 4. Also confirm that the bot you are adding matches the token you entered in Rufoof.

⚠ "Bot not found. Please register it first."

Cause: You are trying to use Update Existing or Append/Delete mode with a bot that has not been registered yet.

Fix: Use Register New Bot mode first to complete the initial setup.

⚠ "No admin channels found for this bot." (Update or Append/Delete mode)

Cause: The bot is not currently an admin in any Telegram channel, so Rufoof cannot retrieve the channel list from the server.

Fix: Open Telegram, go to your files channel, and confirm the bot is still listed as an Administrator. If it was removed, re-add it. Then click ↻ Fetch again in Rufoof.

⚠ Files Too Large dialog appears

Cause: One or more of your files exceed Telegram's 50 MB per-file limit.

Fix: Choose one of the three options: - Skip the oversized files if they are not critical. - Upload Manually After to handle them file by file. - Abort and compress or split the files before trying again.

⚠ Folder Button Limit dialog appears

Cause: One of your folders contains 100 or more items (files + subfolders), which exceeds the maximum number of buttons Telegram can show in a keyboard.

Fix: Choose Skip All Problematic to proceed with the rest of your content, or Abort and reorganize the oversized folder into smaller subfolders before trying again.

⚠ Upload fails midway with a network error

Cause: Your internet connection was interrupted, or Telegram's servers experienced a temporary issue.

Fix: Wait a minute and click ▶ Start Upload (or 📤 Register) again. In Update mode, Rufoof will skip files that were already successfully uploaded and only retry the ones that failed.

⚠ "Session expired. Click Validate to try again."

Cause: You were in Register mode, clicked Validate, but then waited too long (more than a few minutes) without proceeding. The registration session expired.

Fix: Click Validate again to start a fresh session.

⚠ Token rotation fails with "old token must be revoked first"

Cause: You tried to update the token using the Change Token tab, but the old token is still active.

Fix: Go to BotFather, revoke the old token (/mybots → select your bot → API Token → Revoke), then try the token update in Rufoof again.

⚠ "No changes detected."

Cause: You clicked Save in Append/Delete mode but did not make any changes to the file structure.

Fix: This is not an error — it is just informational. If you intended to make changes, review the file manager and make your edits before clicking Save.

My bot shows "Pending" and never gets approved

Cause: The review process can take a few hours. Occasionally it may take longer if there is high volume.

Fix: Wait and check again. Make sure you completed Step 7.9 — clicking the activation link in Telegram — because without that step, the system cannot confirm you as the bot's owner and approval cannot proceed.

⚠ "Invalid folder structure" error during upload

Cause: One or more file or folder names in your upload triggered a security filter. This is usually caused by special characters or patterns in file names that the system flags as potentially unsafe.

Fix: Contact Mariam Initiative support at t.me/blessed_tree and describe which folder you were uploading from. They will identify the problematic file name and advise you.

⚠ "Token rotation fails" / bot token lost or changed

Cause: Token management requires verifying your identity against the system's records.

Fix: Contact support at t.me/blessed_tree with your bot's @username. They will guide you through the process. If you're experience enough, you can change it yourself via clicking Customize Bot button and clicking the "Changed Token? ..." message.

The Rufoof window is blank or does not open

Cause: Rarely, antivirus software can block the application.

Fix: Check your antivirus quarantine and whitelist Rufoof, then try running it again. If the problem persists, re-download the latest version from t.me/MariamInitiative or contact support at t.me/blessed_tree.

For questions, feature requests, or to follow new releases: t.me/MariamInitiative For direct support: t.me/blessed_tree

Rufoof v1.0 — Mariam Initiative