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
Switching from IPv4 to IPv6 breaks existing authorization data #3196
Comments
This is not very high priority because it is unlikely someone will keep switching back-and-forth between IPv4 and IPv6. |
Maybe raise an error on switching so the user knows they need to auth again? It is not always easy to re-auth. |
For me, this problem is relevant. I register accounts on ipv4, and for further work they use IPV6, and in this case, these accounts do not work ( |
You're welcome to review if this is still an issue in the current master version and try to correct it. |
I tried it in the current version master (pip3 install -U https://github.com/LonamiWebs/Telethon/archive/master.zip ) the error has been preserved. I do not know how to solve this problem. |
Sorry, maybe I'm digging absolutely in the wrong place, and I'm wrong in my judgments and searches. I also don't know how transmission protocols work in general, but the only thing I have unearthed is that the response body from the server when switching to IPV6 is very short. Perhaps there are ideas why this is so? There is no such problem in the pyrogram, it works on layer 138, attempts to change the layer in telethon did not give results.
maybe this will help |
@Lonami How save and use SessionsString on V2? |
@w1ld32 that's offtopic here. |
Checklist
pip install -U https://github.com/LonamiWebs/Telethon/archive/master.zip
and triggered the bug in the latest version.When I enabled IPv6 for the client, reusing an existing session that has been connecting via IPv4, I got this error:
Then I reran the program, and it asked to authorize:
It seems that the authorization data doesn't work with different protocols? There is also #1661 which sounds similar but I don't use a proxy.
Update: the reverse is also true: switching from IPv6 to IPv4 broke the session again.
The text was updated successfully, but these errors were encountered: