Skip to main content
If you’re running into issues, start here. Check the Activity page log for error messages first.

”Not connected to Telegram” error

  • Make sure you have an active internet connection
  • Try logging out and logging back in
  • Verify your API credentials are correct at my.telegram.org/apps
  • If a first sign-in keeps stalling on your network, change the Telegram Server Region on the login screen from Auto to another option (see Logging In)

The connection drops while scraping

The footer shows your connection status: Connected, Connecting…, Error, or Disconnected. If the connection quietly drops mid-scrape, the app detects it and updates the footer, then recovers on its own once messages start flowing again. You don’t need to restart it. To check your link at any time while connected, hover the Connected indicator in the footer to see your datacenter and current ping (for example AMS2: 123 ms), and click it to copy that.

Connecting hangs or never finishes

Connecting no longer waits forever. If the handshake stalls, the app surfaces a clear error so you can try again instead of leaving you on Connecting… indefinitely. If it keeps failing on a first sign-in, try a different Telegram Server Region.

No channels showing up

  • Click the Refresh button on the Channels page
  • Make sure you’re connected to Telegram (check the connection status)
  • If you recently joined new channels, it may take a moment for them to appear

An older channel is missing from the list

  • The Channels page lists up to your 5,000 most recently active chats. If you’re in more chats than that, older ones are omitted and an amber banner appears at the top of the page.
  • To surface a missing older chat, open it in Telegram (sending or reading a message refreshes its activity timestamp), then click Refresh on the Channels page.

Addresses not being detected

  • Verify that the channel is being scraped (its Tracking dropdown on the Channels page should not show None)
  • Check that the correct option is enabled in the row’s Tracking dropdown (e.g., if the address comes from a human admin, make sure Admins → Humans is on; if from an admin bot, make sure Admins → Bots is on)
  • The address format must match one of the supported patterns (see Supported Blockchains)
  • Check the Activity page log for any error messages

Addresses not being forwarded

  • Make sure the Maestro bot (@maestro or @maestropro) is accessible from your Telegram account
  • Start a conversation with the Maestro bot on Telegram first if you haven’t already
  • Check the activity log for “error” entries that may explain the failure

Duplicate addresses being skipped

  • This is expected behavior when “Ignore Duplicates” is enabled in Settings
  • Duplicates are detected per channel - the same address from a different channel will still be forwarded
  • To reset duplicate detection, go to Settings and click Clear Address History

App feels slow

  • Check Settings for warnings about large activity logs or address histories
  • Clear your activity logs and/or address history
  • Lower the log retention period

Login issues

ErrorSolution
”API ID must be a valid number”Enter only the numeric API ID from my.telegram.org
”API Hash must be 32 characters”Copy the full API Hash string from my.telegram.org
”Invalid phone number format”Include your country code (e.g., +1 for US, +44 for UK)
“Invalid verification code”Double-check the code from your Telegram app
”Verification code expired”Click “Resend code” to get a new one
”Incorrect password”This is your Telegram 2FA cloud password, not your app password
”Too many attempts”Wait a few minutes before trying again
”This phone number is banned”Contact Telegram support

”Keychain access is unavailable” warning (macOS)

If you see this warning when enabling “Remember credentials”:
  • You previously denied Keychain access when macOS prompted you
  • Go to System Settings → Privacy & Security and allow Keychain access for Maestro Scraper
  • Restart the app and try again
Without Keychain access, your credentials and session cannot be saved, so you will need to log in again each time you restart the app.