Skip to content
This repository has been archived by the owner on Jan 27, 2024. It is now read-only.

unable to connect after "Terminate all sessions" #41

Closed
sherpya opened this issue Jan 29, 2015 · 9 comments
Closed

unable to connect after "Terminate all sessions" #41

sherpya opened this issue Jan 29, 2015 · 9 comments
Labels

Comments

@sherpya
Copy link

sherpya commented Jan 29, 2015

I used the plugin for a while but after issuing a "Terminate all sessions" from another client I was unable to reauth, I fixed it by deleting ~/.telegram-purple directory, so telegram issued new auth code, I think auth file should be deleted when it happens

(13:29:44) prpl-telegram: tgprpl_login()
 (13:29:44) prpl-telegram: base configuration path: '/home/sherpya/.telegram-purple/+39329053276' (13:29:44) prpl-telegram: public key '/etc/telegram-purple/server.pub' loaded successfully
 (13:29:44) prpl-telegram: DC1 'DC' update: 149.154.175.50:16777215
 (13:29:44) prpl-telegram: DC2 'DC' update: 149.154.167.51:443
 (13:29:44) prpl-telegram: DC3 'DC' update: 174.140.142.6:443
 (13:29:44) prpl-telegram: DC4 'DC' update: 149.154.167.91:443
 (13:29:44) prpl-telegram: DC5 'DC' update: 149.154.171.5:443
 (13:29:44) prpl-telegram: connect result: 15
 (13:29:44) prpl-telegram: outbound rpc connection from dc #2 becomed ready
 (13:29:45) prpl-telegram: connect result: 19
 (13:29:45) prpl-telegram: outbound rpc connection from dc #3 becomed ready
 (13:29:46) prpl-telegram: restarting query 10884399431156
 (13:29:46) prpl-telegram: Alarm query 10884399431156
 (13:29:46) prpl-telegram: bad_msg_notification: msg_id = 6109739524300635136, seq = 2, error = 64
 (13:29:46) prpl-telegram: bad_msg_notification: msg_id = 6109739524300635136, seq = 2, error = 64
 (13:29:46) prpl-telegram: failing session 1973613208042315913
 (13:29:47) prpl-telegram: connect result: 19
 (13:29:47) prpl-telegram: outbound rpc connection from dc #3 becomed ready
 (13:29:47) prpl-telegram: adjusting CLOCK_MONOTONIC delta to 0.111626
 (13:29:50) prpl-telegram: restarting query 10879619034404
 (13:29:50) prpl-telegram: Alarm query 10879619034404
 (13:29:50) prpl-telegram: bad_msg_notification: msg_id = 6109739541480553472, seq = 2, error = 64
 (13:29:50) prpl-telegram: bad_msg_notification: msg_id = 6109739541480553472, seq = 2, error = 64
 (13:29:50) prpl-telegram: failing session 3598709928102566275
 (13:29:50) prpl-telegram: connect result: 15
 (13:29:50) prpl-telegram: outbound rpc connection from dc #2 becomed ready
 (13:29:50) prpl-telegram: adjusting CLOCK_MONOTONIC delta to 0.958223
 (13:29:51) prpl-telegram: connect result: 20
 (13:29:51) prpl-telegram: outbound rpc connection from dc #4 becomed ready
 (13:29:51) prpl-telegram: restarting query 10909921261320
 (13:29:51) prpl-telegram: Alarm query 10909921261320
 (13:29:51) prpl-telegram: connect result: 21
 (13:29:51) prpl-telegram: outbound rpc connection from dc #5 becomed ready
 (13:29:52) prpl-telegram: bad_msg_notification: msg_id = 6109739545776637952, seq = 2, error = 64
 (13:29:52) prpl-telegram: bad_msg_notification: msg_id = 6109739545776637952, seq = 2, error = 64
 (13:29:52) prpl-telegram: failing session 5279545293522377993
 (13:29:52) prpl-telegram: connect result: 20
 (13:29:52) prpl-telegram: outbound rpc connection from dc #4 becomed ready
 (13:29:52) prpl-telegram: Alarm query 10884399431156
 (13:29:52) prpl-telegram: adjusting CLOCK_MONOTONIC delta to -0.292781
 (13:29:53) prpl-telegram: restarting query 10911407836184
 (13:29:53) prpl-telegram: Alarm query 10911407836184
 (13:29:54) prpl-telegram: bad_msg_notification: msg_id = 6109739554365455360, seq = 2, error = 64
 (13:29:54) prpl-telegram: bad_msg_notification: msg_id = 6109739554365455360, seq = 2, error = 64
 (13:29:54) prpl-telegram: failing session -3830159073898580804
 (13:29:55) prpl-telegram: connect result: 21
 (13:29:55) prpl-telegram: outbound rpc connection from dc #5 becomed ready
 (13:29:56) prpl-telegram: adjusting CLOCK_MONOTONIC delta to 0.532362
 (13:29:56) prpl-telegram: Alarm query 10879619034404
 (13:29:58) prpl-telegram: Alarm query 10909921261320
 (13:29:59) prpl-telegram: Alarm query 10911407836184
 (13:31:51) prpl-telegram: connect result: -1
@majn
Copy link
Owner

majn commented Apr 4, 2015

The same thing happens with telegram-cli too, which suggests that its a bug in libtgl. I will report this one upstream.

@kaputtnik
Copy link

I got a similar issue. After deleting the session, it is not possible to connect again.

I deleted the complete account in pidgin, the path .purple/telegram-purple/ and reinstalled the plugin, but when I try to authenticate, it doesn't accept the authentification code.

Here is the log:

(22:04:39) prpl-telegram: tgprpl_blist_node_menu()
(22:04:39) gtkconv: setting active conversation on toolbar 0x25695c0
(22:04:39) prpl-telegram: tgprpl_blist_node_menu()
(22:04:39) gtkconv: setting active conversation on toolbar 0x25695c0
(22:04:39) log: Failed to open log file "/home/nik/.purple/logs/777000.log" for reading: Datei oder Verzeichnis nicht gefunden
(22:04:39) Trillian log list: Reading /mnt/windows/Program Files/Trillian/users/default/logs/TELEGRAM/777000.log
(22:04:39) Trillian log list: Reading /mnt/windows/Program Files/Trillian/users/default/logs/TELEGRAM/Query/777000.log
(22:04:39) prefs: /pidgin/conversations/im/x changed, scheduling save.
(22:04:39) prefs: /pidgin/conversations/im/x changed, scheduling save.
(22:04:43) util: Writing file prefs.xml to directory /home/nik/.purple
(22:04:43) util: Writing file /home/nik/.purple/prefs.xml
(22:04:43) util: Writing file accounts.xml to directory /home/nik/.purple
(22:04:43) util: Writing file /home/nik/.purple/accounts.xml
(22:04:43) util: Writing file blist.xml to directory /home/nik/.purple
(22:04:43) util: Writing file /home/nik/.purple/blist.xml
(22:04:43) accels: saving accels to /home/nik/.purple/accels
(22:04:46) prpl-telegram: tgprpl_send_typing()
(22:04:48) prpl-telegram: tgprpl_send_im()
(22:04:48) prpl-telegram: tgprpl_send_typing()
(22:04:48) prpl-telegram: error for query #6172941265715685376: #400 PHONE_CODE_INVALID
(22:04:48) prpl-telegram: Bad code...
(22:04:48) prpl-telegram: Client is not registered, registering...
(22:05:01) sighandler: Caught signal 2
(22:05:01) imgstore: retrieved image id 1
(22:05:01) imgstore: retrieved image id 2
(22:05:01) imgstore: retrieved image id 3
(22:05:01) imgstore: retrieved image id 4
(22:05:01) account: Disconnecting account +4917652724330 (0x19b2c90)
(22:05:01) connection: Disconnecting connection 0x25a3b80
(22:05:01) prpl-telegram: tgprpl_close()

I tried it multiple times, the code is absolutely correct.

Is there a away, to solve it?

@majn
Copy link
Owner

majn commented Jul 18, 2015

Are you using some non-pidgin messenger with fallback chat for SMS authentication prompt and did you install some plugins like OTR? Cause that might be related...

@kaputtnik
Copy link

Thanks for your help.
In dead the problem was otr. I deactivated it for the authentification and it works.

The strange thing is, that I didn't deactivate otr before.

@ffuubarbuzz
Copy link

@kaputtnik, do you use telegram-purple with trillian?

@BenWiederhake
Copy link
Collaborator

@ThiRaBrTNK: That doesn't make any sense, as Trillian doesn't support libpurple and is closed source anyway.

Closing this issue since there seems to have been no activity for over half a year. (Silent-Hunter's reference is accidental due to a backtrace.)

@ffuubarbuzz
Copy link

@BenWiederhake I was just googling for trillian telegram plugin and found this issue. I got confused by 'Trillian' in @kaputtnik 's log, and although I didn't find any mention of trillian using libpurple, neither I found the confirmation that it isn't. So I asked just to be sure.

@EionRobb
Copy link
Contributor

@ThiRaBrTNK that's because he's got the Log Reader plugin which reads in Trillian logs into Pidgin :)

@ffuubarbuzz
Copy link

@EionRobb Thank you for clearing this thing up

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

6 participants