String

[BitQuanta]

2021-09-20T07:56:14.131070+00:00 app[worker.1]: [20-Sep-21 07:56:14 - INFO] - bot - @Oloclon_bot started!
2021-09-20T07:56:15.864823+00:00 app[worker.1]: [20-Sep-21 07:56:15 - INFO] - user - @None started!
2021-09-20T07:56:16.106626+00:00 app[worker.1]: Bot is blocked by the session user !
2021-09-20T07:56:16.378755+00:00 heroku[worker.1]: Process exited with status 0
2021-09-20T07:56:16.556946+00:00 heroku[worker.1]: State changed from up to crashed

I think this issue is due to Telegram latest update where Telegram migrated from 32 to 64 bit if no is there any solution ? 😅

[m4mallu]

This is not a bug at all .. !
This is a security feature in clonebot-ui.

When the bot is deployed in the Heroku or any other platforms, bot PMs the Session user with a particular message. The message contains an option to terminate the deployment . When the same is happened, and the bot is blocked by the session user, the above message will be shown in the logs.

So many peoples uses some others session string for their unwanted / perverted activities. That's y the facility is introduced in this bot.

If you are using your own session string, don't block the bot from your profile. If you have already blocked the bot, unblock the bot and try again later.

[BitQuanta]

I am using my own string session and bot is not blocked too ☹️

…

On Mon, Sep 20, 2021, 2:47 PM Renjith Mangal ***@***.***> wrote: This is not a bug at all .. ! This is a security feature in clonebot-ui. When the bot is deployed in the Heroku or any other platforms, bot PMs the Session user with a particular message. The message contains an option to terminate the deployment . When the same is happened, and the bot is blocked by the session user, the above message will be shown in the logs. So many peoples uses some others session string for their unwanted / perverted activities. That's y the facility is introduced in this bot. If you are using your own session string, don't block the bot from your profile. If you have already blocked the bot, unblock the bot and try again later. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/m4mallu/clonebot-ui/issues/22#issuecomment-922757694>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATLDVJHNW6Q7QEZDWI7HEXTUC332FANCNFSM5ELL4S6A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[m4mallu]

Do you got a message from bot in PM when deployed ?
If yes .. You will definitely have that option in that message. Keep look in to it.

make sure that you are dealing the bot with the same account which the session string have generated.

[BitQuanta]

*No didn't get the message to terminate session that's why I thought its some bug and I am dealing with same account 😔*

…

On Mon, Sep 20, 2021, 2:53 PM Renjith Mangal ***@***.***> wrote: Do you got a message from bot in PM when deployed ? If yes .. You will definitely have that option in that message. Keep look in to it. make sure that you are dealing the bot with the same account which the session string have generated. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/m4mallu/clonebot-ui/issues/22#issuecomment-922761621>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATLDVJEI5RXNK2KZGCS2BETUC34PHANCNFSM5ELL4S6A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[m4mallu]

When you are the session owner and dealing bot with the same account, you should have get a PM from the bot.

I think your session string is not valid.
I clearly says in your message like >> 2021-09-20T07:56:15.864823+00:00 app[worker.1]: [20-Sep-21 07:56:15 - INFO] - user - @None started!

Keep reading the docs carefully and make a valid session string and try gain later.

[BitQuanta]

Hehe good news I just deployed other version with same values and it also showed the same error @none started but it didn't crash and bot is cloning files two :)

…

On Mon, Sep 20, 2021, 3:01 PM Renjith Mangal ***@***.***> wrote: When you are the session owner and dealing bot with the same account, you should have get a PM from the bot. I think your session string is not valid. I clearly says in your message like >> 2021-09-20T07:56:15.864823+00:00 app[worker.1]: [20-Sep-21 07:56:15 - INFO] - user - @None started! Keep reading the docs carefully and make a valid session string and try gain later. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/m4mallu/clonebot-ui/issues/22#issuecomment-922767062>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATLDVJCLQQAULVDIGKLWRC3UC35QRANCNFSM5ELL4S6A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.