search

thebrumby / HotWalletClaimer

Looking to optimize your earnings with HOT tokens on the Near Protocol? How about Wave on SUI? Tree on BSC? Or Vertus on Ton? This Python script simplifies the process by monitoring your account status within popular Telegram apps, ensuring rewards are claimed at the correct time.
MIT License
84 stars 31 forks source link

FIXED: Blum issues #39

Closed oleksandr-roskovynskyi closed 2 weeks ago

oleksandr-roskovynskyi commented 3 weeks ago

Hi,

Blum is not working, please, check

thnks you

Edit from Welly

thebrumby commented 3 weeks ago

Hi,

Yes, we removed Blum from the list of supported games as Blum has blocked access via Telegram Web. We didn't remove from the repository yet in case we found a work-around, but currently is not working.

Thanks

image

S26T commented 3 weeks ago

Hi,

Yes, we removed Blum from the list of supported games as Blum has blocked access via Telegram Web. We didn't remove from the repository yet in case we found a work-around, but currently is not working.

Thanks

image

Hello! I have solution for this. I added this extension with rules for my puppeteer script and it's works https://www.youtube.com/shorts/1pd2RkSFDIg. Maybe you know how make it without chrome extension....

thebrumby commented 3 weeks ago

Ah, great! I'll take a look once I finish my "real" job for the week and can spend some time again on this project here. Be nice to have it running again :)

thebrumby commented 2 weeks ago

Great info from the YouTube thank you! We have Blum working in our test environment. We'll look to update the Docker and installer files in the next few days to return Blum to service!

bscongluanbui commented 2 weeks ago

Great info from the YouTube thank you! We have Blum working in our test environment. We'll look to update the Docker and installer files in the next few days to return Blum to service!

yeah I'm using docker and get this error

Step 01 - An error occurred: Message: unknown error: net::ERR_PROXY_CONNECTION_FAILED (Session info: headless chrome=112.0.5615.49) Stacktrace:

0 0x005585af2bf4

1 0x00558585e040

2 0x00558585b2f8

3 0x00558584e734

4 0x00558584fb9c

5 0x00558584ea60

6 0x00558584da9c

7 0x00558584d968

8 0x00558584c9bc

9 0x00558584cc6c

10 0x00558585ff58

11 0x0055858c7bf4

12 0x0055858c7544

13 0x005585889064

14 0x00558588a550

15 0x005585b1adf4

16 0x005585ad539c

17 0x005585ad4ecc

18 0x005585b175dc

19 0x005585ad5d78

20 0x005585ab94c8

21 0x005585ae05e4

22 0x005585ae0788

23 0x005585aeafa0

24 0x007fb675597c

25 0x007fb67bb7dc

thebrumby commented 2 weeks ago

Hi @bscongluanbui ,

For sure you'll get that error. The post above mentions the time frame for a return-to-service, which will be 1 to 2 days! The script is working fine, but you need to set up a proxy that removes the response headers - we will provide an additional script that Blum users can use for that, but it will first need writing, testing, and deployment!

thebrumby commented 2 weeks ago

Hi all,

To resolve the issue with Blum, you need to take the following steps:

  1. Remove existing Blum & Telegram sessions (if any):

    ./remove-process.sh
    • Select option 1 to remove any active Blum sessions.
    • Select option 2 to remove any inactive Blum sessions and any Telegram accounts you will use to log into Blum (this won't affect other active game sessions).

If you try and reuse a saved TG account, you will likely get returned to the QR log-in page when accessing it using the Proxy Server - you will then see a lot of errors in the flow.

  1. Enable proxy and install dependencies:
./launch.sh enable-proxy

This will install the required dependencies within the standard virtual environment and create a new PM2 process called http-proxy.

  1. Set up new Blum accounts:
./launch.sh blum

Set up new accounts for each Blum user you wish to automate.

Following these steps should resolve the issues you're experiencing with Blum. If you encounter any further problems, feel free to ask for assistance.

bscongluanbui commented 2 weeks ago

Hi all,

To resolve the issue with Blum, you need to take the following steps:

  1. Remove existing Blum & Telegram sessions (if any):
./remove-process.sh
  • Select option 1 to remove any active Blum sessions.
  • Select option 2 to remove any inactive Blum sessions and any Telegram accounts you will use to log into Blum (this won't affect other active game sessions).

If you try and reuse a saved TG account, you will likely get returned to the QR log-in page when accessing it using the Proxy Server - you will then see a lot of errors in the flow.

  1. Enable proxy and install dependencies:
./launch.sh enable-proxy

This will install the required dependencies within the standard virtual environment and create a new PM2 process called http-proxy.

  1. Set up new Blum accounts:
./launch.sh blum

Set up new accounts for each Blum user you wish to automate.

Following these steps should resolve the issues you're experiencing with Blum. If you encounter any further problems, feel free to ask for assistance.

HI Did it working on docker?

bscongluanbui commented 2 weeks ago

I got this after do the follow step CHROME DRIVER INITIALISED: Try not to exit the script before it detaches. Step 10 - Attempting to check for the start button (should not be present)... Step 11 - Attempting to open a link for the app... Step 11 - Failed to find the 'Open Wallet' button within the expected timeframe.

Step 11 - Attempting to find the chat window/message input box... Step 12 - Attempting to send the '/start' command... Step 12 - An error occurred: Message: element not interactable (Session info: headless chrome=112.0.5615.49) Stacktrace:

0 0x005556c42bf4

1 0x0055569adec0

2 0x0055569dfb4c

3 0x0055569df31c

4 0x0055569dac18

5 0x005556a17544

6 0x0055569d9064

7 0x0055569da550

8 0x005556c6adf4

9 0x005556c2539c

10 0x005556c24ecc

11 0x005556c675dc

12 0x005556c25d78

13 0x005556c094c8

14 0x005556c305e4

15 0x005556c30788

16 0x005556c3afa0

17 0x007fa596597c

18 0x007fa59cb7dc

thebrumby commented 2 weeks ago

Hi, looks like the Telegram session is not working correctly. Did you delete the existing Blum and Telegram sessions and start again with a newly scanned QR code or OTP?

thebrumby commented 2 weeks ago

And if you type

pm2 logs http-proxy

Do you see normal output?

94|http-pr | 127.0.0.1:56310 <- WebSocket binary message <- kws4.web.telegram.org:443/apiws 94|http-pr | 127.0.0.1:56310 -> WebSocket binary message -> kws4.web.telegram.org:443/apiws 94|http-pr | 127.0.0.1:56308 <- WebSocket binary message <- kws4.web.telegram.org:443/apiws 94|http-pr | 127.0.0.1:56308 <- WebSocket binary message <- kws4.web.telegram.org:443/apiws 94|http-pr | 127.0.0.1:56308 -> WebSocket binary message -> kws4.web.telegram.org:443/apiws 94|http-pr | 127.0.0.1:56308 -> WebSocket binary message -> kws4.web.telegram.org:443/apiws 94|http-pr | 127.0.0.1:56310 -> WebSocket binary message -> kws4.web.telegram.org:443/apiws 94|http-pr | 127.0.0.1:56310 <- WebSocket binary message <- kws4.web.telegram.org:443/apiws 94|http-pr | 127.0.0.1:56308 -> WebSocket binary message -> kws4.web.telegram.org:443/apiws 94|http-pr | 127.0.0.1:56308 <- WebSocket binary message <- kws4.web.telegram.org:443/apiws

bscongluanbui commented 2 weeks ago

Hi, looks like the Telegram session is not working correctly. Did you delete the existing Blum and Telegram sessions and start again with a newly scanned QR code or OTP?

yes. I do it, delete all blum and telegram sesion, create new session but got this. I'm using docker and using ./pull-games.sh to update

thebrumby commented 2 weeks ago

Can you see the healthly response from the http-proxy output in PM2 logs?

bscongluanbui commented 2 weeks ago

Can you see the healthly response from the http-proxy output in PM2 logs?

oh no something wrong [TAILING] Tailing last 15 lines for [http-proxy] process (change the value with --lines option) /root/.pm2/logs/http-proxy-error.log last 15 lines: /root/.pm2/logs/http-proxy-out.log last 15 lines: 14|http-pr | WebSocket connection closed by client: 1001 14|http-pr | 127.0.0.1:40504: GET https://kws2-1.web.telegram.org/apiws 14|http-pr | << Client disconnected. 14|http-pr | WebSocket connection closed by client: 1001 14|http-pr | [19:01:38.741][127.0.0.1:40438] client disconnect 14|http-pr | [19:01:38.745][127.0.0.1:40488] server disconnect kws5-1.web.telegram.org:443 (149.154.170.100:443) 14|http-pr | [19:01:38.749][127.0.0.1:40458] server disconnect kws2-1.web.telegram.org:443 (149.154.167.99:443) 14|http-pr | [19:01:38.752][127.0.0.1:40472] server disconnect kws1-1.web.telegram.org:443 (149.154.174.100:443) 14|http-pr | [19:01:38.756][127.0.0.1:40494] server disconnect kws5-1.web.telegram.org:443 (149.154.170.100:443) 14|http-pr | [19:01:38.759][127.0.0.1:40504] server disconnect kws2-1.web.telegram.org:443 (149.154.167.99:443) 14|http-pr | [19:01:38.764][127.0.0.1:40468] server disconnect kws5-1.web.telegram.org:443 (149.154.170.100:443) 14|http-pr | WebSocket connection closed by client: 1001 14|http-pr | 127.0.0.1:34708: GET https://web.telegram.org/k/rlottie-wasm.wasm HTTP/2.0 14|http-pr | << HTTP/2.0 200 OK (content missing) 14|http-pr | << peer closed connection

thebrumby commented 2 weeks ago

Is it worth trying to create a new container for Blum? See if it also has the issue. I pre-tested on AWS-Linux & Ubuntu 24 machines both as raw installs and docker containers (both AMD64 and ARM64) and could not create any issue:

docker run -d --name telegram-claim-bot2 --restart unless-stopped thebrumby/telegram-claim-bot:latest
docker exec -it telegram-claim-bot2 /bin/bash
bscongluanbui commented 2 weeks ago

Is it worth trying to create a new container for Blum? See if it also has the issue. I pre-tested on AWS-Linux & Ubuntu 24 machines both as raw installs and docker containers (both AMD64 and ARM64) and could not create any issue:

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

thanks for help. I reinstall and it's working but sometime account it's claim but not start farm

thebrumby commented 2 weeks ago

No problem! :)

Regarding Blum, there might need to be some tweaks to the code in the coming days because they have made alterations to the GUI. Now that the game is live again, we will monitor it closely to identify any changes they have made.