Bug: [no QRcode settings]

[devCarlosHenSil]

Olá, Phill pode me ajudar não estou conseguindo utilizar a sua aplicação pois segui todo passado em ambos sistemas operacionais porem me deparo sempre com o mesmo problema , ele não aparece o QRcode para que eu possa scanear e outro ponto é que está bem diferente do video a forma de instalação uma vez que mudou muito de lá para cá com seus comiits se puder me ajudar agradeço. Abraço.

[thebrumby]

Oi,

Você está usando Docker ou Ubuntu? Pode ser que existam algumas configurações extras no sistema, mas o processo geral deve ser o mesmo. Parece que o script não está conseguindo detectar o QR code do Telegram.

Para verificar a conexão com o Telegram Web, você pode usar o comando curl no terminal. Siga estas instruções:

1.  Abra o terminal.
2.  Digite o seguinte comando e pressione Enter:

curl -I https://web.telegram.org

Isso deve retornar algumas informações sobre a conexão. Se você conseguir ver algo como HTTP/1.1 200 OK, significa que a conexão com o site está funcionando corretamente.

Se não conseguir essa resposta, pode haver um problema de rede ou firewall bloqueando o acesso ao Telegram Web. Me avise o que aparecer para poder ajudar mais!

[thebrumby]

Se o QR code não aparecer, talvez devido a uma conexão de internet lenta ou algum outro problema, você pode desativar a captura de tela do QR code nas configurações. Assim, será solicitado o número de telefone registrado, e o Telegram enviará um código OTP para o seu dispositivo.

[thebrumby]

Hi,

The recommended setting is have the built-in proxy turned off, or at least until you have everything working correctly.

To debug it further, you will need to enable the screenshots from the virtual web browser as described in the troubleshooting guide.

[devCarlosHenSil]

Hello, Phill, it worked as you instructed me to use the method via phone number and disable the proxy, however it is very risky to use multiple accounts with the same IP address, do you know what could be the problem when using a proxy, I tested the proxy itself and it is operating normally.

[thebrumby]

Hi @devCarlosHenSil

do you know what could be the problem when using a proxy,

Did you try enabling the proxy again now that the QR code validation is complete? Sometimes, authentication methods like phone numbers and QR codes can be sensitive to proxy use during the initial setup but might work fine once that step is done. I made a slight tweak to the code to try and make it more resilient - previously it had 8 seconds to see the QR code, it now gives 20 seconds until the first code appears, and then refreshes at 3-second intervals.

I tested the proxy itself and it is operating normally.

I also did a quick test myself, I configured the proxy using

./launch.sh setup-proxy

After entering the host, port, username and password, it connected correctly and my SmartProxy dashboard reflected the usage, confirming the traffic passed through the proxy.

however it is very risky to use multiple accounts with the same IP address,

From my experience, managing multiple Telegram accounts from a single IP address generally doesn’t pose issues. My personal belief is that this is quite common due to how ISPs handle their networks. For instance, mobile ISPs like Vodafone UK have around 17 million subscribers but only a limited pool of IPv4 addresses. To manage this, they use Carrier-Grade NAT (CGNAT), meaning hundreds or even thousands of customers might share a single public IP address.

Or another example might be hotel Wi-Fi—many guests might access the same online service without issues, even though they're sharing an IP address. Most platforms are designed to recognize that multiple users can share an IP, so it’s unlikely to be flagged automatically. I don't think people are likely to get banned for checking their account on hotel Wi-Fi the same day another user checked their own on the same network.

However, it's just my 2 cents, and feel free to take whatever precautions you feel are necessary to avoid detection.

[thebrumby]

Just as an FYI, some users who initially experienced issues logging in a proxy reported that they got the proxy to work by modifying this in setup-proxy.py:

def update_start_script(host, port, username, password):
    start_script_content = f"""#!/bin/bash
./venv/bin/mitmdump --mode upstream:https://{host}:{port} --upstream-auth {username}:{password} -s {os.path.join(PROXY_DIR, 'modify_requests_responses.py')} > /dev/null 2>&1
"""
    with open(START_SCRIPT_PATH, 'w') as file:
        file.write(start_script_content)
    os.chmod(START_SCRIPT_PATH, 0o755)

They changed the https to http. From a personal perspective, I don't want to send unencrypted login credentials over the internet as they could be intercepted by any relay between your Docker setup and the VPN host. If you aren't using a metered VPN, you might be more open to try it than I was.

[thebrumby]

I added the option to switch to HTTP authentication in the script, along with a test to see what level of anonymity the proxy provides and a link to WebShare where people can get a free account with some included monthly bandwidth.

[devCarlosHenSil]

Thank you very much Phill for your willingness to help. I will check the changes you committed.****