Hello,

It looks like my Telegram bot keeps resetting every day, even mid-task and I have to re-send service accounts again and set up folders again. It's tedious and annoying, especially when the bot is running and it just says 'Welcome to CloneBot. Let's copy some data!' Could anyone help me please? I've attached some screenshots below.

Thank you :)

Hello; First of all thanks for the repo its really useful. I have created SAs but where to put them? Your heroku guide video url is dead, kindly update it

shadows@shadowdrivevm:~/clonebot/telegram_gcloner$ sudo python3 telegram_gcloner.py
2021-11-17 05:06:27,625 - utils.config_loader - INFO - Found telegram_token: 21xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
2021-11-17 05:06:27,626 - utils.config_loader - INFO - Found user_ids: -1,xxxxxxxxxxxxxx
2021-11-17 05:06:27,626 - utils.config_loader - INFO - Found group_ids: -1,xxxxxxxxxxxx
2021-11-17 05:06:27,626 - utils.config_loader - INFO - Found path_to_gclone: ./gclone
2021-11-17 05:06:27,626 - utils.config_loader - INFO - Found gclone_para_override:
2021-11-17 05:06:27,626 - utils.config_loader - WARNING - Gclone Executable was not found in the Drectory.
Press Enter to continue...

But its clearly in the file.

shadows@shadowdrivevm:~/clonebot/telegram_gcloner$ ls -a
.  ..  config.ini  gclone.exe  handlers  logs  telegram_gcloner.py  utils

Today I tried to clone a folder with 50 sub-folders. Bot says it successfully cloned the folder to my td. But when I check that folder in my td I get 39 subfolders. Then again tried with a folder of another 50 sub-folders this time bot actually cloned 45 folders and other 5 are missing. Any solution?

While deploying the bot, it was giving a geographical problem and I solved this problem with these codes. Screenshot of the problem: https://cdn.discordapp.com/attachments/955067308529832016/964244646324744192/unknown.png https://media.discordapp.net/attachments/955067308529832016/963851494984122469/unknown.png

If you are facing Error, where Heroku Showing Select Time Zone then just replace the code of Docker file with below code:

FROM ubuntu:20.04

WORKDIR /usr/src/app RUN chmod 777 /usr/src/app

ENV TZ=Asia/Kolkata RUN ln -snf "/usr/share/zoneinfo/$TZ" /etc/localtime RUN echo "$TZ" > /etc/timezone

RUN apt-get update RUN apt-get install -y tzdata RUN apt-get -qq update RUN apt-get -qq install -y git python3 python3-pip
locales python3-lxml aria2
curl pv jq nginx npm

COPY requirements.txt . RUN pip3 install --no-cache-dir -r requirements.txt &&
apt-get -qq purge git

RUN locale-gen en_US.UTF-8 ENV LANG en_US.UTF-8 ENV LANGUAGE en_US:en ENV LC_ALL en_US.UTF-8

COPY . .

RUN chmod +x start.sh RUN chmod +x gclone

CMD ["bash","start.sh"]

option to allow us to use delegated service accounts to our domain name (already done manually) to select a shared folder that is shared by service accounts (even if its in the my drive.) and to allow us to use --drive-impersonate [email protected] as a config option. (if you use rclone as the backend for it.)

im getting this error while deploying to heroku

Setting up libkrb5support0:amd64 (1.17-6ubuntu4.1) ...
Setting up libsasl2-modules-db:amd64 (2.1.27+dfsg-2ubuntu0.1) ...
Setting up tzdata (2022c-0ubuntu0.20.04.0) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
Configuring tzdata

Please select the geographic area in which you live. Subsequent configuration
questions will narrow this down by presenting a list of cities, representing
the time zones in which they are located.
  1. Africa        6. Asia            11. System V timezones
  2. America       7. Atlantic Ocean  12. US
  3. Antarctica    8. Europe          13. None of the above
  4. Australia     9. Indian Ocean
  5. Arctic Ocean  10. Pacific Ocean
Geographic area: =!= Build failed due to an error:
=!= Timed out compiling app
If this persists, please contact us at https://help.heroku.com/. 

Run akhileshns/[email protected] Created and wrote to ~/.netrc › Warning: Our terms of service have changed: › https://dashboard.heroku.com/terms-of-service ▸ not logged in Error: Error: Command failed: heroku container:login › Warning: Our terms of service have changed: › https://dashboard.heroku.com/terms-of-service ▸ not logged in