🛠️ Troubleshooting

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 Settings dropdown on the Channels page should not show Tracking: None)
Check that the correct option is enabled in the row’s Settings 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
If you see Unverified (orange) entries, the sender couldn’t be matched to your tracking toggles, so the address was held back on purpose. Set the Humans and Bots toggles in the relevant section (Admins or Users) the same way to have those messages forwarded. See the Activity Page for details

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

Error	Solution
”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
No code arrives	Check the Telegram app on your other devices, since the code often goes there rather than as an SMS. Then use the resend button (for example Resend via SMS) to try another method. If the screen says no code will arrive here, sign in on the official Telegram app first, then try again
”Telegram is asking for an extra verification step…”	Telegram wants a check only its official apps can complete. Sign in once with the official Telegram app on your phone, then try again in Maestro Scraper
”You are signed in, but your account details could not be loaded”	The login itself worked and your session is saved. Restart the app and it will open already signed in
”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.

​”Not connected to Telegram” error

​The connection drops while scraping

​Connecting hangs or never finishes

​No channels showing up

​An older channel is missing from the list

​Addresses not being detected

​Addresses not being forwarded

​Duplicate addresses being skipped

​App feels slow

​Login issues

​”Keychain access is unavailable” warning (macOS)