Auth key creation failed. Let's try again: KeyError(225735525,) about pyrogram HOT 5 CLOSED

Hi there, you did nothing wrong, but I'm not able to reproduce this on my machine. To see what's going on update Pyrogram using pip install --upgrade git+https://github.com/pyrogram/pyrogram.git@issue-12 and show me the full logs again. Also tell me where you are running it: OS, Python version.

from pyrogram.

Ooops, may be it's our vpn+proxy:

>>> b'TTP/1.0 400 Bad Request\r\nServer: squid/2.6.STABLE21\r\nDate: Mon, 29 Jan 2018 10:49:53 GMT\r\nContent-Type: text/html\r\nContent-Length: 1162\r\nExpires: Mon, 29 Jan 2018 10:49:53 GMT\r\nX-Squid-Error: ERR_INVALID_REQ 0\r\nX-Cache: MISS from openvpn.serv\r\nX-Cache-Lookup: NONE from openvpn.serv:3121\r'

I use Ubuntu 16.04, python 3.5.

May be I can change port, because I guess proxy catches all connection on 80 port.

from pyrogram.

Yep. I've extensively tested Pyrogram with proxies, but let me know if you think it should work by kindly opening a new issue. If it works with another proxy there's definitely something wrong with yours. Thanks.

from pyrogram.

Do I have a possibility to change datacenter ip and port? Because I have recommended ip/port on telegram panel. When I changed in connection.py:

self.address = (ipv4, 80)

to

self.address = ("149.154.167.50", 443)

I successfully logged. It's not a proxy like package expects, it's just transparent and caching proxy in our office. I can't bypass it without modifying source code.

from pyrogram.

The recommended ip/port you see on your panel are only meaningful for client developers, the DC IP changes depending on where the user is located - Pyrogram automatically manages this. Port 80 and 443 offer the exact same service, but I found Telegram switching off port 443 rather often, that's why I'm using port 80. You don't really have to mess with this.

If you can confirm self.address = (ipv4, 443) works for you without changing the IP, then I might think of switching back to port 443 as default.

But again, I think is just your proxy misbehaving and we really should discuss this in another issue you can open.

from pyrogram.