Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does the bot support proxy rotation? Dynamic proxy refetching? Is it possible to implement? #191

Open
salat-23 opened this issue Nov 1, 2023 · 3 comments

Comments

@salat-23
Copy link

salat-23 commented Nov 1, 2023

I basically have a pool of proxies that die after some time, so I want to refetch them periodically. I looked at the current implementation and didnt find anything that resembles proxy rotation, so if the account got assigned some proxy, and this proxy dies - this particular account will not function anymore?
I heard that steam login should be made on the single ip, so is it even possible to implement something like proxy pooling and refetching?

@nadyakott
Copy link

Hello, Timur! I am trying to start container but got an exception. Could you help me with running my container?
node:internal/process/promises:288
2023-11-21 21:23:02 triggerUncaughtException(err, true /* fromPromise */);
2023-11-21 21:23:02 ^
2023-11-21 21:23:02
2023-11-21 21:23:02 Error: connect ECONNREFUSED 127.0.0.1:5432
2023-11-21 21:23:02 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16) {
2023-11-21 21:23:02 errno: -111,
2023-11-21 21:23:02 code: 'ECONNREFUSED',
2023-11-21 21:23:02 syscall: 'connect',
2023-11-21 21:23:02 address: '127.0.0.1',
2023-11-21 21:23:02 port: 5432
2023-11-21 21:23:02 }

@salat-23
Copy link
Author

Hello, Timur! I am trying to start container but got an exception. Could you help me with running my container? node:internal/process/promises:288 2023-11-21 21:23:02 triggerUncaughtException(err, true /* fromPromise */); 2023-11-21 21:23:02 ^ 2023-11-21 21:23:02 2023-11-21 21:23:02 Error: connect ECONNREFUSED 127.0.0.1:5432 2023-11-21 21:23:02 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16) { 2023-11-21 21:23:02 errno: -111, 2023-11-21 21:23:02 code: 'ECONNREFUSED', 2023-11-21 21:23:02 syscall: 'connect', 2023-11-21 21:23:02 address: '127.0.0.1', 2023-11-21 21:23:02 port: 5432 2023-11-21 21:23:02 }

Although this is not related to my question in any way, your problem should be fixed by launching database instance

@Step7750
Copy link
Member

Step7750 commented Feb 8, 2024

Is it possible to implement?

Most definitely, feel free to create a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants