Hello, I got the error after I switched from ipv4

Question

Hello, I got the error after I switched from ipv4

to ipv6 (I changed dc_id - from 2 to 5 and IPV6_IP from '2001:67c:4e8:f002::a' to '2001:b28:f23f:f005::a') .

I use accounts that have been authorized with ipv4, but even recreating the session with ipv6 does not solve the problem.

What do I need to do for telegram to accept these auth_keys?

P.S. Some accounts work after switching from ipv4 to ipv6, and some give an error (not yet why)

telethon.errors.common.AuthKeyNotFound:
The server claims it doesn't know about the authorization key (session
file) currently being used. This might be because it either has never
seen this authorization key, or it used to know about the authorization
key but has forgotten it, either temporarily or permanently (possibly
due to server errors).

If the issue persists, you may need to recreate the session file and login
again. This is not done automatically because it is not possible to know
if the issue is temporary or permanent.

0

04.09.2023

5 ответов

12 просмотров

Kevin Автор вопроса

⎞ .·. ⎝ ⎝
You're doing something unstable and needs proper i...

I'm trying to use ipv6, they only worked with the fifth datacenter on some accounts. If you know of another stable way to use ipv6, I would be grateful for the information. Thank you.

0

04.09.2023

⎞ .·. ⎝ ⎝

Kevin
I'm trying to use ipv6, they only worked with the ...

You can't use random datacenters for authKeys. iirc it will terminate them when you connect to wrong one

0

04.09.2023

Kevin Автор вопроса

⎞ .·. ⎝ ⎝
You can't use random datacenters for authKeys. iir...

In last telethon update it won’t terminate them

0

04.09.2023

⎞ .·. ⎝ ⎝

Kevin
In last telethon update it won’t terminate them

You got your answer then, you must connect to the correct dc id.

0

04.09.2023

⎞ .·. ⎝ ⎝ · Accepted Answer

⎞ .·. ⎝ ⎝

You're doing something unstable and needs proper info. if server thinks that auth key isn't found, you're likely making request to wrong datacenter or it's just invalid and never existed

0

04.09.2023

Похожие чаты

Hello, I got the error after I switched from ipv4

5 ответов

Похожие вопросы