search

kenorb-contrib / tg

`telegram-cli` for Telegram IM
https://github.com/telegramdesktop/tdesktop
GNU General Public License v2.0
382 stars 52 forks source link

Error for query 'get difference' : #420 FLOOD_WAIT_333 #54

Open abitmore opened 2 years ago

abitmore commented 2 years ago

Today after a restart my client started to get FLOOD_WAIT_333 errors when trying to login and fail. With -vvvv it seems the server is rejecting the get difference call. Log messages are here:

$ ./telegram-cli --json -vvvv
 *** 1638630887.448025 Couldn't open public key file: /etc/telegram-cli/server.pub
 *** 1638630887.448049 Can not load key /etc/telegram-cli/server.pub
 *** 1638630887.448066 Couldn't open public key file: tg-server.pub
 *** 1638630887.448075 Can not load key tg-server.pub
 *** 1638630887.448095 'direct' public key loaded successfully
 *** 1638630887.448133 DC1 'DC' update: 149.154.175.60:443
 *** 1638630887.448153 DC2 'DC' update: 149.154.167.50:443
 *** 1638630887.448261 DC3 'DC' update: 149.154.175.100:443
 *** 1638630887.448276 DC4 'DC' update: 149.154.167.92:443
 *** 1638630887.448296 DC5 'DC' update: 91.108.56.191:443
 *** 1638630887.448361 Secret chat in ok state
 *** 1638630887.448433 Secret chat in ok state
 *** 1638630887.449043 Sent query #156619901502455040 of size 152 to DC 2
 *** 1638630887.532119 outbound rpc connection from dc #2 becomed ready
 *** 1638630887.532201 Sent query #156619901859504960 of size 140 to DC 2
 *** 1638630887.615706 restarting query 156619901859504960
 *** 1638630887.615736 Alarm query 156619901859504960 (type 'get config')
 *** 1638630887.703677 bad_msg_notification: msg_id = 7037866069880766464, seq = 2, error = 64
 *** 1638630887.703772 bad_msg_notification: msg_id = 7037866069880766464, seq = 2, error = 64
 *** 1638630887.703853 failing session 4743754658146467039
 *** 1638630887.784295 outbound rpc connection from dc #2 becomed ready
 *** 1638630887.784366 Sent query #7037866070604781568 of size 140 to DC 2
 *** 1638630887.865070 adjusting CLOCK_MONOTONIC delta to 0.249365
 *** 1638630887.865100 work_new_session_created: msg_id = 7037866073420205057, dc = 2
 *** 1638630887.865121 regen query from old session 156619901502455040
 *** 1638630887.865139 regen query from old session 156619901859504960
 *** 1638630887.869421 Alarm query 156619901859504960 (type 'get config')
 *** 1638630887.869473 Resent query #156619901859504960 as #7037866070604781572 of size 140 to DC 2
 *** 1638630887.871214 DC1 '' update: 149.154.175.56:443
 *** 1638630887.871238 DC1 '' update: 2001:0b28:f23d:f001:0000:0000:0000:000a:443
 *** 1638630887.871257 DC2 '' update: 149.154.167.151:443
 *** 1638630887.871276 DC2 '' update: 2001:067c:04e8:f002:0000:0000:0000:000a:443
 *** 1638630887.871295 DC2 '' update: 2001:067c:04e8:f002:0000:0000:0000:000b:443
 *** 1638630887.871315 DC3 '' update: 2001:0b28:f23d:f003:0000:0000:0000:000a:443
 *** 1638630887.871334 DC4 '' update: 2001:067c:04e8:f004:0000:0000:0000:000a:443
 *** 1638630887.871354 DC4 '' update: 149.154.166.120:443
 *** 1638630887.871373 DC4 '' update: 2001:067c:04e8:f004:0000:0000:0000:000b:443
 *** 1638630887.871392 DC5 '' update: 2001:0b28:f23f:f005:0000:0000:0000:000a:443
 *** 1638630887.871408 DC5 '' update: 91.108.56.132:443
 *** 1638630887.967595 Alarm query 156619901502455040 (type 'get difference')
 *** 1638630887.967662 Resent query #156619901502455040 as #7037866070604781576 of size 152 to DC 2
 *** 1638630888.083668 error for query 'get difference' #7037866070604781576: #420 FLOOD_WAIT_333
 *** 1638630888.083919 login problem: error #71 (RPC_CALL_FAIL 420: FLOOD_WAIT_333)
 *** 1638630888.084130 login failed
 *** 1638630888.084323 login error #71: RPC_CALL_FAIL 420: FLOOD_WAIT_333
 *** 1638630888.084496 you can relogin by deleting auth file or running telegram-cli with '-q' flag

If run telegram-cli -q, it shows the API_64BIT_LOGIN_APP_OUTDATED error (see #51).