Time-Farm: Claim issue

[thebrumby]

Regarding your output

I tried uninstalling start over. But it doesn't seem to see the claim button on Time farm.
CHROME DRIVER INITIALISED: Try not to exit the script before it detaches.
Step 101 - Attempting to check for the start button (should not be present)...
Step 102 - Attempting to open a link for the app...
Step 103 - Attempting to click the 'Launch' button (may not be present)...
Step 104 - Attempting to switch to the app's iFrame...
Step 106 - Attempting to click the 'Start' button (may not be present)...
Step 108 - Attempting to look for the claim button....
STATUS: The claim button wasn't clickable on this occassion.

It's hard to see exactly which stage it's failing on.

Option 1:

If you go to the Time-Farm tab on your Telegram app / Telegram web, if you delete the existing conversation with the bot (method to delete varies by device (right click on PC or long press on mobile device) - but make sure you don't delete and block. Then restart a new "conversation" before handing over to the script again.

Option 2:

This will vary slightly depending whether you are on Docker or Standalone Ubuntu, but in settings, if you enable the debug setting (it will take screenshots of each stage of the process, which might highlight where the issue is) and also change verbose to level 3, this will show far more details about each stage of the claim. Here's an example from my Time Farm:

85|Time-Fa | CHROME DRIVER INITIALISED: Try not to exit the script before it detaches.
85|Time-Fa | Step 100 - Attempting to verify if we are logged in (hopefully QR code is not present).

85|Time-Farm:Phil  | Step 100 - nothing found to action. The QR code test passed.
85|Time-Farm:Phil  | Step 101 - Attempting to check for the start button (should not be present)...
85|Time-Farm:Phil  | Step 101 - Timeout while trying to check for the start button (should not be present).
85|Time-Farm:Phil  | Step 102 - Attempting to open a link for the app...
85|Time-Farm:Phil  | Step 102 - Successfully able to open a link for the app..
85|Time-Farm:Phil  | Step 103 - Attempting to click the 'Launch' button (may not be present)...
85|Time-Farm:Phil  | Step 103 - Timeout while trying to click the 'Launch' button (may not be present).
85|Time-Farm:Phil  | Step 104 - Attempting to switch to the app's iFrame...
85|Time-Farm:Phil  | Step 104 - Was successfully able to switch to the app's iFrame.
85|Time-Farm:Phil  | Step 105 - Found 1 elements with XPath: //div[@class='balance']
85|Time-Farm:Phil  | Step 105 - Before BALANCE: $123,456
85|Time-Farm:Phil  | Step 106 - Attempting to click the 'Start' button (may not be present)...
85|Time-Farm:Phil  | Step 106 - Timeout while trying to click the 'Start' button (may not be present).
85|Time-Farm:Phil  | Step 107 - check if the timer is elapsing...
85|Time-Farm:Phil  | Step 107 - Found 0 elements with XPath: //table[@class='scroller-table']
85|Time-Farm:Phil  | Step 108 - Attempting to look for the claim button....
85|Time-Farm:Phil  | Step 108 - Removed 0 overlay(s) covering the target.
85|Time-Farm:Phil  | Step 108 - Removed 0 overlay(s) covering the target.
85|Time-Farm:Phil  | STATUS: We appear to have correctly clicked the claim button.
85|Time-Farm:Phil  | Step 109 - Attempting to click the 'Start' button...
85|Time-Farm:Phil  | Step 109 - Removed 0 overlay(s) covering the target.
85|Time-Farm:Phil  | Step 109 - Successfully moved to the element using ActionChains.
85|Time-Farm:Phil  | Step 109 - Removed 0 overlay(s) covering the target.
85|Time-Farm:Phil  | Step 110 - check if the timer is elapsing...
85|Time-Farm:Phil  | Step 110 - Found 0 elements with XPath: //table[@class='scroller-table']
85|Time-Farm:Phil  | Step 111 - Found 1 elements with XPath: //div[@class='balance']
85|Time-Farm:Phil  | Step 111 - After BALANCE: $234,567
85|Time-Farm:Phil  | Step 111 - Random offset applied to the wait timer of: 11 minutes.
85|Time-Farm:Phil  | Session released: ./selenium/Time-Farm:Phil
85|Time-Farm:Phil  | CHROME DRIVER DETACHED: It is now safe to exit the script.

[mexxuz]

I was able to get it running. Clearing the chat really helped. I was able to see in real time how the game bot was starting. Thx! But I ran into a problem when running Blum, that option didn't work there :(

[thebrumby]

I'm pleased to hear you're connected OK with Time-Farm. Blum requires the use of the built-in proxy to remove certain response headers to make the connection, is the PM2 process "http-proxy" starting OK?

[mexxuz]

Я рад слышать, что у вас все в порядке с Time-Farm. Blum требует использования встроенного прокси-сервера для удаления определенных заголовков ответа для установления соединения, нормально ли запускается процесс PM2 "http-proxy"?

Can you tell me more about this or where can I read more about it? I am not good at understanding code, so I need an explanation of how and what to do. So far I don't understand how to run it or test it, with what commands to implement it.

[thebrumby]

pm2 list

Will show the running processes, first thing with Blum is to know if the "http-proxy" is running :)

[mexxuz]

pm2 list

Will show the running processes, first thing with Blum is to know if the "http-proxy" is running :)

Yes, such a process is present.

[thebrumby]

OK good. Can you screenshot any errors you get when launching Blum, please?

[mexxuz]

Хорошо. Не могли бы вы сделать скриншот ошибок, которые возникают при запуске Blum?

Here's what's been going on since installation. It doesn't detect the input correctly, doesn't see the balance, and does nothing in the end.

[mexxuz]

Maybe I'm doing something wrong at the startup stage? Do I need to enter some kind of proxy? I set everything by default.

[mexxuz]

Here's what the Blum log gives me

[thebrumby]

Hi,

For some reason it's having a lot of connection issues.

I would try to delete one of the accounts like this:

./launch.sh status

and then within status script:

delete Blum:Mexx

and finally, hit enter to go back to the command line

./launch.sh blum Blum:Mexx

And try to set up again :)

[mexxuz]

Привет

По какой-то причине у него много проблем с подключением.

Я бы попробовал удалить один из аккаунтов так:

./launch.sh status

а затем в сценарии состояния:

delete Blum:Mexx

и, наконец, нажмите Enter, чтобы вернуться в командную строку

./launch.sh blum Blum:Mexx

И попробуйте снова настроить :)

I've already done the reinstall and uninstall several times, but it hasn't worked for me. What else can I try to do? After all attempts now I can see that the bot I have starts in telegram, but gets stuck further.

I also tried it on another accanut, the situation is exactly the same.

[thebrumby]

From all the screenshots you included above, it seems that from the first step, it's not able to connect to the chat window in Telegram, even before it tries to connect to Blum.

As an experiment, you could try a separate Docker container for Blum.

docker run -d --name blum --restart unless-stopped thebrumby/telegram-claim-bot:latest
docker exec -it blum /bin/bash

[thebrumby]

Update: Actually, if your saved TG sessions were saved before the built-in proxy was enabled (it’s mandatory for Blum), the error is probably just that you need to use a new Telegram session not the saved one?

[mexxuz]

Update: Actually, if your saved TG sessions were saved before the built-in proxy was enabled (it’s mandatory for Blum), the error is probably just that you need to use a new Telegram session not the saved one?

I created a new docker as you wrote above and put only Blum in there. But the problem still remains. This created a new session with a QR login, right?

[thebrumby]

This looks much more promising, it’s connecting now. Depending on the state of the game on first run, it might take a couple of attempts to get in sync.

pm2 restart Blum:Mexx

[thebrumby]

Also, if you set verbose level to 3 in settings, it will help more fault finding.