-
-
Notifications
You must be signed in to change notification settings - Fork 66
FAQ
If you see this error you where blocked from using the TGTG API. It is usually caused by a too high request rate. Since tools like this scanner violate the terms and conditions of TGTG they try to detect the corresponding request patterns and block them. These bans are usually temporary.
- Make sure you are using the latest version of the tgtg-scanner.
- Increase the sleepTime (
config.ini
) orSLEEP_TIME
(environment variable) between API requests. - Make sure you don't run multiple instances of the tgtg-scanner at the same time.
- Try using a different IP. Most ISP provide a new IP when you reconnect your internet connection.
- Wait some time. In most cases the error disappears after 24h.
Create the container as described in the official documentation Creating a Container. Set up the environment as described in the docker-compose.yml
. You don't have to set up any volumes. The container will create a volume for persistent storage of your tgtg credentials by itself.
If you see the error ERROR SAVING CREDENTIALS! - [ERRNO 13]
in your log (#310), the scanner has no permission to write the token files into the /token
directory. To fix the permission run chown 1001:1001 /volume1/docker/tgtg/tokens
on your Synology. You may need to adjust the path according to your setup.
You can create a new bot using @BotFather. Simply start a conversation with @BotFather and send /newbot
. You will receive an API token for the bot. Enter this token in your config. On the next start, the scanner will help you obtain the chat_id.
For more information about the @BotFather please refer to the official documentation: https://core.telegram.org/bots#6-botfather