This is a Telegram Bot written in Python for mirroring files on the Internet to your Google Drive or Telegram.

Fork of Anasty’s Repo

Extra Features implemented by Arsh :

  • Leech Log
  • Mirror logs
  • Source link logs
  • Alt Leech log – You can forward leeched files and alternative channels/groups
  • Special permissions to group moderators
  • Database Support for leech logs and alt leech logs
  • Sending Leeched files and Mirror links in user’s PM
  • Force Subscriber Module
  • Auto Delete all bot related message to prevent copyright issue
  • Appdrive Support
  • Megasdkrest Client implimentation
  • Special permissions for MOD_USERS – Moderator for groups
  • Change commands directly from config.env
  • And many more little changes can’t remember
  • Turn on/off Leech Features from config.env

How to deploy?

  • Check Deploy branch for deploy on heroku

Prerequisites

Click here for Deployement guide for newbie
  • Tutorial Video from A to Z:

1. Installing requirements

  • Clone this repo:
git clone https://github.com/arshsisodiya/helios-mirror mirrorbot/ && cd mirrorbot
  • For Debian based distros
sudo apt install python3 python3-pip

Install Docker by following the official Docker docs or by commands below.

sudo apt install snapd
sudo snap install docker
  • For Arch and it’s derivatives:
sudo pacman -S docker python
  • Install dependencies for running setup scripts:
pip3 install -r requirements-cli.txt

2. Setting up config file

cp config_sample.env config.env
  • Remove the first line saying:
_____REMOVE_THIS_LINE_____=True

Fill up rest of the fields. Meaning of each field is discussed below:

**0. Special Vars for features added by Arsh **

  • AUTO_DELETE_UPLOAD_MESSAGE_DURATION : Interval of time (in seconds), after which the bot deletes it’s message and source message which is expected to be viewed instantly. NOTE: Set to -1 to disable auto message deletion.
  • MOD_USERS – The Telegram User ID (not username) of users you want to promote as Moderator in your group, separate by space
  • LEECH_LOG – Chat id of channel/group where leeched files will be uploaded, NOTE: only put 1 channel/group id, if you leave this empty bot will not send leeched files anywhere.
  • LEECH_LOG_ALT – Chat id of channels/groups where you want to forward leeched files, separate by space
  • MIRROR_LOGS – Chat id of channels/groups where you want to store Mirror logs
  • LINK_LOGS – Chat id of channels/groups where you want to store mirrored/leeched source links
  • BOT_PM – set it true if you want to send mirror links and leeched files in user’s PM
  • FSUB – set it true if you want to enable Force Subscriber module
  • FSUB_CHANNEL_ID – chat id of channel you want users to subscribe NOTE: if you don’t wanna use fsub remove this var entirely from your configs.
  • CHANNEL_USERNAME – username of channel you want users to subscribe
  • IMAGE_LEECH – set it true if you want to enable to leeech images, by default its False to prevent users from leeching thousands of images
  • MEGAREST – set it True if you want to use Megasdkrest
  • APPDRIVE_EMAIL – Your Appdrive account email
  • APPDRIVE_PASS – Your Appdrive account password
  • MIN_LIMIT – Set minimum file size, files below given size will not be downloaded
  • LEECH_ENABLED – Set it True if you want to use leech features

1. Required Fields

  • BOT_TOKEN: The Telegram Bot Token that you got from @BotFather
  • TELEGRAM_API: This is to authenticate your Telegram account for downloading Telegram files. You can get this from https://my.telegram.org. NOTE: DO NOT put this in quotes.
  • TELEGRAM_HASH: This is to authenticate your Telegram account for downloading Telegram files. You can get this from https://my.telegram.org
  • OWNER_ID: The Telegram User ID (not username) of the Owner of the bot.
  • GDRIVE_FOLDER_ID: This is the Folder/TeamDrive ID of the Google Drive Folder to which you want to upload all the mirrors.
  • DOWNLOAD_DIR: The path to the local folder where the downloads should be downloaded to.
  • DOWNLOAD_STATUS_UPDATE_INTERVAL: Time in seconds after which the progress/status message will be updated. Recommended 10 seconds at least.
  • AUTO_DELETE_MESSAGE_DURATION: Interval of time (in seconds), after which the bot deletes it’s message and command message which is expected to be viewed instantly. NOTE: Set to -1 to disable auto message deletion.
  • BASE_URL_OF_BOT: Valid BASE URL where the bot is deployed to use qbittorrent web selection. Format of URL should be http://myip, where myip is the IP/Domain(public) of your bot or if you have chosen port other than 80 so write it in this format http://myip:port (http and not https). This Var is optional on VPS and required for Heroku specially to avoid app sleeping/idling. For Heroku fill https://yourappname.herokuapp.com. Still got idling? You can use http://cron-job.org to ping your Heroku app.

2. Optional Fields

  • ACCOUNTS_ZIP_URL: Only if you want to load your Service Account externally from an Index Link or by any direct download link NOT webpage link. Archive the accounts folder to ZIP file. Fill this with the direct download link of zip file. If index need authentication so add direct download as shown below:
  • TOKEN_PICKLE_URL: Only if you want to load your token.pickle externally from an Index Link. Fill this with the direct link of that file.
  • MULTI_SEARCH_URL: Check drive_folder setup here. Write drive_folder file here. Open the raw file of that gist, it’s URL will be your required variable. Should be in this form after removing commit id: https://gist.githubusercontent.com/username/gist-id/raw/drive_folder
  • YT_COOKIES_URL: Youtube authentication cookies. Check setup Here. Use gist raw link and remove commit id from the link, so you can edit it from gists only.
  • NETRC_URL: To create .netrc file contains authentication for aria2c and yt-dlp. Use gist raw link and remove commit id from the link, so you can edit it from gists only. NOTE: After editing .nterc you need to restart the docker or if deployed on heroku so restart dyno in case your edits related to aria2c authentication.
    • NOTE: All above url variables used incase you want edit them in future easily without deploying again or if you want to deploy from public fork. If deploying using cli or private fork you can leave these variables empty add token.pickle, accounts folder, drive_folder, .netrc and cookies.txt directly to root but you can’t update them without rebuild OR simply leave all above variables and use private UPSTREAM_REPO.
  • DATABASE_URL: Your Database URL. Follow this Generate Database to generate database. Data will be saved in Database: auth and sudo users, leech settings including thumbnails for each user and rss data. NOTE: If deploying on heroku and using heroku postgresql delete this variable from config.env file. DATABASE_URL will be grabbed from heroku variables.
  • AUTHORIZED_CHATS: Fill user_id and chat_id of groups/users you want to authorize. Separate them by space.
  • SUDO_USERS: Fill user_id of users whom you want to give sudo permission. Separate them by space.
  • IS_TEAM_DRIVE: Set to False or leave it empty to get public google drive links else True so only who have access to your Folder/TeamDrive can open the links. Bool
  • USE_SERVICE_ACCOUNTS: Whether to use Service Accounts or not. For this to work see Using Service Accounts section below.
  • INDEX_URL: Refer to https://gitlab.com/ParveenBhadooOfficial/Google-Drive-Index.
  • MEGA_API_KEY: Mega.nz API key to mirror mega.nz links. Get it from Mega SDK Page
  • MEGA_EMAIL_ID: E-Mail ID used to sign up on mega.nz for using premium account (Leave though)
  • MEGA_PASSWORD: Password for mega.nz account
  • BLOCK_MEGA_FOLDER: If you want to remove mega.nz folder support, set it to True. Bool
  • BLOCK_MEGA_LINKS: If you want to remove mega.nz mirror support, set it to True. Bool
  • STOP_DUPLICATE: (Leave empty if unsure) if this field is set to True, bot will check file in Drive, if it is present in Drive, downloading or cloning will be stopped. (NOTE: File will be checked using filename not file hash, so this feature is not perfect yet). Bool
  • CLONE_LIMIT: To limit the size of Google Drive folder/file which you can clone. Don’t add unit, the default unit is GB.
  • MEGA_LIMIT: To limit the size of Mega download. Don’t add unit, the default unit is GB.
  • TORRENT_DIRECT_LIMIT: To limit the Torrent/Direct mirror size. Don’t add unit, the default unit is GB.
  • ZIP_UNZIP_LIMIT: To limit the size of zip and unzip commands. Don’t add unit, the default unit is GB.
  • STORAGE_THRESHOLD: To leave specific storage free and any download will lead to leave free storage less than this value will be cancelled. Don’t add unit, the default unit is GB.
  • VIEW_LINK: View Link button to open file Index Link in browser instead of direct download link, you can figure out if it’s compatible with your Index code or not, open any video from you Index and check if its URL ends with ?a=view, if yes make it True, compatible with BhadooIndex Code. Bool
  • UPTOBOX_TOKEN: Uptobox token to mirror uptobox links. Get it from Uptobox Premium Account.
  • IGNORE_PENDING_REQUESTS: If you want the bot to ignore pending requests after it restarts, set this to True. Bool
  • STATUS_LIMIT: Limit the no. of tasks shown in status message with buttons. NOTE: Recommended limit is 4 tasks.
  • SERVER_PORT: Only For VPS even if IS_VPS is False, which is the BASE_URL_OF_BOT Port.
  • WEB_PINCODE: If empty or False means no more pincode required while qbit web selection. Bool
  • QB_SEED: If True QB torrent will be seeded after and while uploading until reaching specific ratio or time, edit MaxRatio or GlobalMaxSeedingMinutes or both from qbittorrent.conf (-1 means no limit, but u can cancel manually by gid). NOTE: 1. Don’t change MaxRatioAction, 2. Only works with /qbmirror and /qbzipmirror. Bool
  • QB_TIMEOUT: Timeout of dead torrents downloading with qBittorrent in seconds.
    • Qbittorrent NOTE: If your facing ram exceeded issue then set limit for MaxConnecs and decrease AsyncIOThreadsCount in qbittorrent config.
  • TG_SPLIT_SIZE: Size of split in bytes, leave it empty for max size 2GB.
  • AS_DOCUMENT: Default Telegram file type upload. Empty or False means as media. Bool
  • EQUAL_SPLITS: Split files larger than TG_SPLIT_SIZE into equal parts size (Not working with zip cmd). Bool
  • CUSTOM_FILENAME: Add custom word to leeched file name.
  • UPSTREAM_REPO: Your github repository link, if your repo is private add https://username:{githubtoken}@github.com/{username}/{reponame} format. Get token from Github settings. So you can update your appllication from filled repository on each restart. NOTE: Any change in docker or requirements you need to deploy/build again with updated repo to take effect – DON’T delete .gitignore file. Read this also.
  • UPSTREAM_BRANCH: Upstream branch for update. Empty means master..
  • SEARCH_API_LINK: Search api app link. Get your api from deploying this repository.
    • Supported Sites:

    1337x, Piratebay, Nyaasi, Torlock, Torrent Galaxy, Zooqle, Kickass, Bitsearch, MagnetDL, Libgen, YTS, Limetorrent, TorrentFunk, Glodls, TorrentProject and YourBittorrent

  • SEARCH_LIMIT: Search limit for search api, limit for each site and not overall result limit. Default is zero (Default api limit for each site).
  • CRYPT: Cookie for gdtot google drive link generator. Follow these steps.
  • SEARCH_PLUGINS: List of qBittorrent search plugins (github raw links). I have added some plugins, you can remove/add plugins as you want. Main Source: qBittorrent Search Plugins (Official/Unofficial).
  • RSS_DELAY: Time in seconds for rss refresh interval. Recommended 900 seconds at least. Empty means 900 s (default time).
  • RSS_COMMAND: Choose command for the desired action.
  • RSS_CHAT_ID: Chat ID where rss links will be sent.
  • USER_STRING_SESSION: To send rss links from your telegram account instead of adding bot to channel then adding channel to group to get rss link since bot will not read command from itself or other bot. To generate string session use this command python3 generate_string_session.py after mounting repo folder for sure.
    • RSS NOTE: DATABASE_URL and RSS_CHAT_ID is required, otherwise all rss commands will not work. Add the bot in grop for better experience, since if you are using USER_STRING_SESSION you need to send a private message to bot after each restart. You can add the bot to a channel and add this channel to group so messages sent by bot to channel will be forwarded to group without using USER_STRING_SESSION.
  • Three buttons are already added including Drive Link, Index Link, and View Link, you can add extra buttons, if you don’t know what are the below entries, simply leave them empty.
    • BUTTON_FOUR_NAME:
    • BUTTON_FOUR_URL:
    • BUTTON_FIVE_NAME:
    • BUTTON_FIVE_URL:

Getting Google OAuth API credential file and token.pickle

3. Click here to open Getting Google OAuth API credential file and token.pickle

**NOTES** – Old authentication changed, now we can’t use bot to generate token.pickle. You need OS with a browser. – You should set default browser. For linux refer to this [link](https://askubuntu.com/questions/609863/what-environment-variable-should-i-use-to-set-a-default-web-browser). – Windows users should install python3 and pip. You can find how to install them from google or from this [telegraph](https://telegra.ph/Create-Telegram-Mirror-Leech-Bot-by-Deploying-App-with-Heroku-Branch-using-Github-Workflow-12-06) from [Wiszky](https://github.com/vishnoe115) tutorial.

  1. Visit the Google Cloud Console
  2. Go to the OAuth Consent tab, fill it, and save.
  3. Go to the Credentials tab and click Create Credentials -> OAuth Client ID
  4. Choose Desktop and Create.
  5. Publish your OAuth consent screen App to prevent token.pickle from expire
  6. Use the download button to download your credentials.
  7. Move that file to the root of mirrorbot, and rename it to credentials.json
  8. Visit Google API page
  9. Search for Google Drive Api and enable it
  10. Finally, run the script to generate token.pickle file for Google Drive:

pip install google-api-python-client google-auth-httplib2 google-auth-oauthlib
python3 generate_drive_token.py
  • For linux user use pip3 instead of pip.

Deploying on VPS

Click here to open Deploying on VPS

IMPORTANT NOTES:

  1. You must set SERVER_PORT variable to 80 or any other port you want to use.
  2. To clear the container (this will not affect on the image):
sudo docker container prune
  1. To delete the images:
sudo docker image prune -a
  1. Check the number of processing units of your machine with nproc cmd and times it by 4, then edit AsyncIOThreadsCount in qBittorrent.conf.
  2. Use anasty17/mltb-oracle:latest for oracle or if u faced problem with arm64 docker run.
    • Tutorial Video for Deploying on Oracle VPS:
      • Thanks to Wiszky
      • No need to use sudo su, you can also use sudo before each cmd!


Deploying on VPS Using Docker

  • Start Docker daemon (skip if already running), if installed by snap then use 2nd command:
sudo dockerd
sudo snap start docker
  • Note: If not started or not starting, run the command below then try to start.
sudo apt install docker.io
  • Build Docker image:
sudo docker build . -t mirror-bot
  • Run the image:
sudo docker run -p 80:80 mirror-bot
  • To stop the image:
sudo docker ps
sudo docker stop id

Deploying on VPS Using docker-compose

NOTE: If you want to use port other than 80, change it in docker-compose.yml also.

sudo apt install docker-compose
  • Build and run Docker image:
sudo docker-compose up
  • After editing files with nano for example (nano start.sh):
sudo docker-compose up --build
  • To stop the image:
sudo docker-compose stop
  • To run the image:
sudo docker-compose start
  • Tutorial video from Tortoolkit repo for docker-compose and checking ports


Deploying on Heroku


Extras

Bot commands to be set in @BotFather

mirror - Mirror
zipmirror - Mirror and upload as zip
unzipmirror - Mirror and extract files
qbmirror - Mirror torrent using qBittorrent
qbzipmirror - Mirror torrent and upload as zip using qb
qbunzipmirror - Mirror torrent and extract files using qb
leech - Leech
zipleech - Leech and upload as zip
unzipleech - Leech and extract files
qbleech - Leech torrent using qBittorrent
qbzipleech - Leech torrent and upload as zip using qb
qbunzipleech - Leech torrent and extract using qb
clone - Copy file/folder to Drive
count - Count file/folder of Drive
watch - Mirror yt-dlp supported link
zipwatch - Mirror yt-dlp supported link as zip
leechwatch - Leech through yt-dlp supported link
leechzipwatch - Leech yt-dlp support link as zip
leechset - Leech settings
setthumb - Set thumbnail
status - Get Mirror Status message
rsslist - List all subscribed rss feed info
rssget - Get specific No. of links from specific rss feed
rsssub - Subscribe new rss feed
rssunsub - Unsubscribe rss feed by title
rssset - Rss Settings
list - Search files in Drive
ts - Search for torrents with API
cancel - Cancel a task
cancelall - Cancel all tasks
del - Delete file/folder from Drive
log - Get the Bot Log
shell - Run commands in Shell
restart - Restart the Bot
stats - Bot Usage Stats
ping - Ping the Bot
help - All cmds with description
addleechlog - Add alt leech log in database
rmleechlog - Remove alt leech log from database
adll - Add Primary leech log in database
rmll - Remove Primary leech log from database

UPSTREAM REPO (Recommended)

  • UPSTREAM_REPO variable can be used for edit/add/update any file in repository.
  • You can add private/public repository link to grab all files from it.
  • You can skip adding the privates files like token.pickle or accounts folder before deploying, also no need to add variables direct links except config.env, simply fill UPSTREAM_REPO private one in case you want to grab all files including private files.
  • UPSTREAM_BRANCH don’t ever fill heroku here.

Using Service Accounts for uploading to avoid user rate limit

Using Service Accounts for uploading to avoid user rate limit

For Service Account to work, you must set USE_SERVICE_ACCOUNTS = “True” in config file or environment variables. NOTE: Using Service Accounts is only recommended while uploading to a Team Drive.

1. Generate Service Accounts. What is Service Account?

Let us create only the Service Accounts that we need.

Warning: Abuse of this feature is not the aim of this project and we do NOT recommend that you make a lot of projects, just one project and 100 SAs allow you plenty of use, its also possible that over abuse might get your projects banned by Google.

NOTE: If you have created SAs in past from this script, you can also just re download the keys by running:

python3 gen_sa_accounts.py --download-keys project_id

NOTE: 1 Service Account can upload/copy around 750 GB a day, 1 project can make 100 Service Accounts so you can upload 75 TB a day or clone 2 TB from each file creator (uploader email).

Two methods to create service accounts

Choose one of these methods

1. Create Service Accounts in existed Project (Recommended Method)
  • List your projects ids
python3 gen_sa_accounts.py --list-projects
  • Enable services automatically by this command
python3 gen_sa_accounts.py --enable-services $PROJECTID
  • Create Sevice Accounts to current project
python3 gen_sa_accounts.py --create-sas $PROJECTID
  • Download Sevice Accounts as accounts folder
python3 gen_sa_accounts.py --download-keys $PROJECTID
2. Create Service Accounts in New Project
python3 gen_sa_accounts.py --quick-setup 1 --new-only

A folder named accounts will be created which will contain keys for the Service Accounts.

2. Add Service Accounts

Two methods to add service accounts

Choose one of these methods

1. Add Them To Google Group then to Team Drive (Recommended)
  • Mount accounts folder
cd accounts
  • Grab emails form all accounts to emails.txt file that would be created in accounts folder
  • For Windows using PowerShell
$emails = Get-ChildItem .\**.json |Get-Content -Raw |ConvertFrom-Json |Select -ExpandProperty client_email >>emails.txt
  • For Linux / MacOs
grep -oPh '"client_email": "\K[^"]+' *.json > emails.txt
  • Unmount acounts folder
cd ..

Then add emails from emails.txt to Google Group, after that add this Google Group to your Shared Drive and promote it to manager and delete email.txt file from accounts folder

2. Add Them To Team Drive Directly
  • Run:
python3 add_to_team_drive.py -d SharedTeamDriveSrcID

Generate Database

1. Using Railway

  • Go to railway and create account
  • Start new project
  • Press on Provision PostgreSQL
  • After creating database press on PostgresSQL
  • Go to Connect column
  • Copy Postgres Connection URL and fill DATABASE_URL variable with it

2. Using Heroku PostgreSQL

3. Using ElephantSQL

  • Go to elephantsql and create account
  • Hit Create New Instance
  • Follow the further instructions in the screen
  • Hit Select Region
  • Hit Review
  • Hit Create instance
  • Select your database name
  • Copy your database url, and fill DATABASE_URL variable with it

Multi Search IDs

To use list from multi TD/folder. Run driveid.py in your terminal and follow it. It will generate drive_folder file or u can simply create drive_folder file in working directory and fill it, check below format:

MyTdName folderID/tdID IndexLink(if available)
MyTdName2 folderID/tdID IndexLink(if available)

Yt-dlp and Aria2c Authentication Using .netrc File

Click here to open Yt-dlp and Aria2c Authentication Using .netrc File

For using your premium accounts in yt-dlp or for protected Index Links, create .netrc file according to following format:

Note: Create .netrc and not netrc, this file will be hidden, so view hidden files to edit it after creation.

Format:

machine host login username password my_password

Example:

machine instagram login anas.tayyar password mypassword

Instagram Note: You must login even if you want to download public posts and after first try you must confirm that this was you logged in from different ip(you can confirm from phone app).

Youtube Note: For youtube authentication use cookies.txt file.

For Index Link with only password without username, even http auth will not work, so this is the solution.

machine example.workers.dev password index_password

Where host is the name of extractor (eg. instagram, Twitch). Multiple accounts of different hosts can be added each separated by a new line.


Gdtot Cookies

To Clone or Leech gdtot link follow these steps:

  1. Login/Register to gdtot.
  2. Copy this script and paste it in browser address bar.
    • Note: After pasting it check at the beginning of the script in broswer address bar if¬†javascript:¬†exists or not, if not so write it as shown below.

    javascript:(function () {
      const input = document.createElement('input');
      input.value = JSON.stringify({url : window.location.href, cookie : document.cookie});
      document.body.appendChild(input);
      input.focus();
      input.select();
      var result = document.execCommand('copy');
      document.body.removeChild(input);
      if(result)
        alert('Cookie copied to clipboard');
      else
        prompt('Failed to copy cookie. Manually copy below cookie\n\n', input.value);
    })();
    
    • After pressing enter your browser will prompt a alert.
  3. Now you’ll get this type of data in your clipboard

    {"url":"https://new.gdtot.org/","cookie":"PHPSESSID=k2xxxxxxxxxxxxxxxxxxxxj63o; crypt=NGxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxWdSVT0%3D"}
    
    
  4. From this you have to paste value of crypt in config.env file.

Credits

P.s – Credit goes to all original developers of python, pyrogram, linux, heroku, mirror bots, leech bots, Mega, megasdkrest, sql database, google drive, telegram, and everything used in this project, hopefully now people will not cry for credits.

GitHub

View Github