-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
#401 AUTH_KEY_UNREGISTERED #725
Comments
The first time was able to log in, work a few days, then made a left, but the re-authorization issues such error .... error for query #6180314910434795724: #401 AUTH_KEY_UNREGISTERED |
telegram-cli not authenticated after I took an active session through Telegram Web |
delete folder .telegram-cli and all ok. |
+1 tglq_query_error function at queries.c tries to handle 401 error_code but leaves it unhandled (existing condition only handles if SESSION_PASSWORD_NEEDED string exists in error message), so later processing fails at assertion: telegram-cli: tgl/queries.c:4084: tgl_started_cb: Assertion `success' failed. Program received signal SIGABRT, Aborted. |
sergey@ubuntu:~/tg/bin$ ./telegram-cli -k tg-server.pub -vvvvv
Telegram-cli version 1.3.3, Copyright (C) 2013-2015 Vitaly Valtman
Telegram-cli comes with ABSOLUTELY NO WARRANTY; for details type
show_license'. This is free software, and you are welcome to redistribute it under certain conditions; type
show_license' for details.Telegram-cli uses libtgl version 2.0.3
Telegram-cli includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit. (http://www.openssl.org/)
Telegram-cli uses libpython version 2.7.6
I: config dir=[/home/sergey/.telegram-cli]
*** public key 'tg-server.pub' loaded successfully
*** Couldn't open public key file: /etc/telegram-cli/server.pub
*** Can not load key /etc/telegram-cli/server.pub
*** public key 'tg-server.pub' loaded successfully
*** DC1 'DC' update: 149.154.175.50:443
*** DC2 'DC' update: 149.154.167.51:443
*** DC3 'DC' update: 149.154.175.100:443
*** DC4 'DC' update: 149.154.167.91:443
*** DC5 'DC' update: 91.108.56.165:443
*** outbound rpc connection from dc #2 becomed ready
*** outbound rpc connection from dc #4 becomed ready
*** outbound rpc connection from dc #1 becomed ready
*** outbound rpc connection from dc #3 becomed ready
*** restarting query 505764321097276
*** Alarm query 505764321097276
*** restarting query 505764332886688
*** Alarm query 505764332886688
*** outbound rpc connection from dc #5 becomed ready
*** bad_msg_notification: msg_id = 6180314886469606380, seq = 2, error = 64
*** bad_msg_notification: msg_id = 6180314886469606380, seq = 2, error = 64
*** failing session 6404857466529644773
*** bad_msg_notification: msg_id = 6180314886469230640, seq = 2, error = 64
*** bad_msg_notification: msg_id = 6180314886469230640, seq = 2, error = 64
*** failing session -3735179620475051446
*** restarting query 505764391485748
*** Alarm query 505764391485748
*** restarting query 505764395480236
*** Alarm query 505764395480236
*** outbound rpc connection from dc #2 becomed ready
*** outbound rpc connection from dc #4 becomed ready
*** adjusting CLOCK_MONOTONIC delta to 0.182601
*** DC1 '' update: 2001:0b28:f23d:f001:0000:0000:0000:000a:443
*** DC2 '' update: 2001:067c:04e8:f002:0000:0000:0000:000a:443
*** DC3 '' update: 2001:0b28:f23d:f003:0000:0000:0000:000a:443
*** DC4 '' update: 2001:067c:04e8:f004:0000:0000:0000:000a:443
*** DC4 '' update: 149.154.165.120:443
*** DC5 '' update: 2001:0b28:f23f:f005:0000:0000:0000:000a:443
*** adjusting CLOCK_MONOTONIC delta to 0.190541
*** DC5 '' update: 91.108.56.101:443
*** bad_msg_notification: msg_id = 6180314886468478844, seq = 2, error = 64
*** bad_msg_notification: msg_id = 6180314886468478844, seq = 2, error = 64
*** failing session 5630999941781025234
*** bad_msg_notification: msg_id = 6180314886469223620, seq = 2, error = 64
*** bad_msg_notification: msg_id = 6180314886469223620, seq = 2, error = 64
*** failing session -548891041960055255
*** restarting query 505764762733344
*** Alarm query 505764762733344
*** outbound rpc connection from dc #1 becomed ready
*** outbound rpc connection from dc #3 becomed ready
*** bad_msg_notification: msg_id = 6180314886472639312, seq = 2, error = 64
*** bad_msg_notification: msg_id = 6180314886472639312, seq = 2, error = 64
*** failing session -144894069499040779
*** adjusting CLOCK_MONOTONIC delta to 0.495458
*** adjusting CLOCK_MONOTONIC delta to 0.496858
*** outbound rpc connection from dc #5 becomed ready
*** adjusting CLOCK_MONOTONIC delta to -0.235857
*** Alarm query 505763642842436
*** error for query #6180314910434795724: #401 AUTH_KEY_UNREGISTERED
The text was updated successfully, but these errors were encountered: