-
Notifications
You must be signed in to change notification settings - Fork 59
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
Wrong server_salt #32
Comments
change your connection protocol of your client app to http in order to see the result! @SadeghHayeri |
I try with 'HTTP' and "TCP' but doesn't work again :( |
can you send your code? |
var telegramLink = require('telegram.link')(); my code works correctly |
@farhadamjady I use your code in first time, i use signup and signin to get authKey
but in your code, you only use id! I try run this code:
but get other error again:
how use that authKey? |
if you have singup and get registered authkey please remove createAuthKey method and just use messages.getDialogs when you connected to telegram |
hi
i try to save authKey in my system and then i use telegramLink.retrieveAuthKey method to get my authKey back and it doesn't get null, it return real authKey and i make new client with this authKey
but when i try to get information like calling 'client.messages.getDialogs' method
but print this in terminal:
[INFO] Sun, 28 Aug 2016 22:38:17 GMT net.EncryptedRpcChannel Call of 'mtproto.service.invokeWithLayer' took 1299ms
[INFO] Sun, 28 Aug 2016 22:38:17 GMT net.EncryptedRpcChannel Wrong server_salt in message [0x57c367d88ac07c18]
[INFO] Sun, 28 Aug 2016 22:38:18 GMT net.EncryptedRpcChannel Call of 'mtproto.service.invokeAfterMsg' took 477ms
and stop working
why this happens and what can i do?
The text was updated successfully, but these errors were encountered: