Closed BraveCanister closed 3 weeks ago
Alright, after about an hour of stepping away it suggests it timed out trying to find an iframe:
I started everything from scratch step by step and it got stuck nonetheless, now at step 5:
Hi,
The setup process should only take a couple of minutes—I recently recreated over 60 accounts in about an hour.
What server specifications are you using? It sounds like you might be running out of RAM.
You can check your memory usage with the following command:
free -m
As mentioned in some of the closed issues, if you’re on a limited RAM AWS account, consider using an ARM64 server. This setup is tied to an older version of Chrome, which tends to use less memory.
I followed the video setting up an Amazon VPS 1:1 with a default instance type t3.micro.
I'll try ARM64 for sure.
At the time of recording the video, the setup was successfully hosting 8 or 9 accounts using that method. Unfortunately, since then, the baseline RAM requirements of the third-party software seem to have increased, impacting its ability to run on a 1 GB server.
Right, so would I have to go with an instance of at least 2gb of memory? Is there any clue as to how much it would cost per month running say 10 HOT accounts given that the free tier is limited to micro with 1gb of memory?
Hi,
The costs can vary depending on the data center hosting the script, but there’s an option that might work well for testing:
When creating an instance, search for:
Minimal Ubuntu 22.04 LTS - Jammy
I set up a test instance on an AMD-64 bit, t2.micro instance (free-tier eligible), and was able to create six accounts with some RAM to spare.
If the free tier doesn’t quite cover the number of accounts you want, it might be worth moving to a different provider after testing. Many offer servers with 2 GB RAM for around $2-3 per month, which could be a good alternative.
Awesome, I got it working finally. Are there any particular providers at that cost that I could check out?
Well, while I managed to add the processes successfully after upgrading an instance to x64 ARM and bigger RAM, it still fails:
Error encountered: expected string or bytes-like object, got 'bool' right after it attempts to locate storage.
Hi,
You need to follow the troubleshooting guide: https://github.com/thebrumby/HotWalletClaimer/issues/166
1) Enable verbose 3 2) Enable debugging and look at the screenshots from the virtual browser
Alright well, it didn't get to the storage step this time:
I just re-ran the exact same thing again and no chrome crash happened.
Despite the log saying "Was successfully able to enter the seed phrase", based on the screenshots it doesn't do anything:
All the rest of the screenshots for the consequent steps are just staring at the import wallet starting screen on the app.
However, there is one account that I claimed manually just a short while ago, and the debug screenshots show that it does enter the seed and access the wallet:
I don't know what to make of any of this. The other handful of accounts that I run from my PC work fine.
For the accounts that don't get stuck on the entry screen. I set up the forced claim in settings but judging from screenshots it's stuck because of the "check news" button.
I'm trying to set up a HOT wallet claimer via AWS and after inputting the seed phrase it gets stuck at Step 12:
"Attempting to click the storage link"
In one of my many attempts it went a little further, claiming that an error occurred while trying to clear overlays:
I think it bricks my EC2 instance because restarting the ShellNGN window gives me a "connection closed" timeout error and I have to reboot the instance via AWS panel.