Closed mrdarkerr closed 2 weeks ago
After disabling the script and passing a few minutes, the problem was solved automatically
how to disable the script? mine get that error too, already running a few min still the error exist
I use docker to keep the script running in the vps background and disable the script by stopping the container, but I checked again and found that the script is not stable and it gets the same error
Something like this Unclosed client session HamsterKombatBot | client_session: <aiohttp.client.ClientSession object at 0x7f7485583490> Or connections: ['[(<aiohttp.client_proto.ResponseHandler object at 0x7fc35ea3ea50>, 139177.231788663)]', '[(<aiohttp.client_proto.ResponseHandler object at 0x7fc35e0f8050>, 139177.59331447)]', '[(<aiohttp.client_proto.ResponseHandler object at 0x7fc35e0f8050>, 139177.231788663)]' object at 0x7fc35d80d010>, 139178.30941403)]', '[(<aiohttp.client_proto.ResponseHandler object at 0x7fc35e1727b0>, 139174.494861983)]'] and even Unknown error while getting Access Token: 422, message='Unprocessable Entity'
And the point is that sometimes there are errors and sometimes there is no problem
Problem solution: 1) Log in to this telegram account from any device; 2) Close all sessions with the Pyrogram header 3) Recreate the session inside your bot (instead of a token, use a phone number in international format) 4) Disable proxy or use SOCKS5 instead of HTTP 5) Synchronize the system time on your computer
See also:
Unknown error while getting Access Token: 422, message='Unprocessable Entity', url=URL('https://api.hamsterkombat.io/auth/auth-by-telegram-webapp') | Response text: {"type":"validation","on":"body","found":{"initDataRaw":null,"fingerprint":{"visitorId":"5425ed84e59c293f4e30b7161cc85612"}}}...