Proxy to all tg sesions

[oleginin]

Hi. It will very good and nice to add to each session, prxoy . Even without username and password because in proxy provider we can add ip using without autorization. So please add posibility to add proxy to tg accounts. It is very hard to manage a lot of containers with one account. Thanks.

[thebrumby]

Hi,

Thank you for your suggestion.

I understand that managing multiple containers with one account can be challenging, and adding proxy support per session could help streamline your workflow. However, I'd like to share my perspective on this.

In my experience, I operate multiple Telegram accounts from a single IP address without any issues. This is actually quite common due to how ISPs manage their networks. For example, a mobile ISP like Vodafone UK has around 17 million subscribers but only a limited pool of IPv4 addresses. As a result, hundreds or even thousands of customers share a single public IP address using technologies like Carrier-Grade NAT (CGNAT). This means it's normal for many users to appear from the same IP without causing problems.

Imagine checking your game account on hotel Wi-Fi and getting banned because another guest is using the same game—that typically doesn't happen. From what I've seen, operating multiple accounts from one IP doesn't raise red flags.

Regarding adding proxy support to individual Telegram sessions, the third-party modules we use don't support multiple proxies easily. For instance:

• Selenium: It can connect to a proxy but doesn't handle authentication with a username and password.
• MITMProxy: We use this for modifying data (necessary for integrating certain games like Blum). It supports proxy authentication but only with one set of credentials at a time.

If you need different IP addresses for each Telegram account, here are a couple of options:

1. Paid Rotating Proxies: Use proxies that rotate IPs every so often. This can provide different IP addresses without additional configuration.
2. Multiple MITMProxy Instances: Start multiple instances of MITMProxy, each on a different port, and point different account sessions to each one. This can be achieved by:
   • Running separate containers for each account.
   • Replicating the repository into different directories and setting up each with a different port.

While I don't use proxies myself, I have added VPN tunnel authentication to the MITMProxy setup based on user requests to assist those who need it, such as those dealing with national-level firewalls. If users need further modifications based on their own assessment of risk, they can fork and modify the project, develop it, and contribute back. However, in terms of development by myself, I've provided what is there as a courtesy to those who want it but won't be spending any more time adding further support in the near future, and probably not ever.

I hope this helps clarify the situation. Please let me know if you have any other questions or need further assistance.

Cheers,

Phil