Telegram X error 400

[MAHDITX]

I sometimes get this error on Telegram X

error (400: response hash mismatch)

Telegram X support gave me this link : https://github.com/tdlib/td/issues/292

What do I need to change to solve this problem?

[alexbers]

Ok, I'll try to dig into that issue, thanks

[someoneIG]

I also saw this error a lot

[alexbers]

I am trying to reproduce the issue and it seems the proxy working for me. Could you please provide more details to reproduce the bug:

• what is the Telegram client os and version?
• what proxy mode do you use? Is it ee mode or dd mode, or the classic one?
• what version of the proxy do you use? the lattest one from the master branch? Do you use Docker? Are there some interesting messages in the proxy log?

[someoneIG]

My OS is Android 10, Telegram X v0.22.8.1361 ee mode (TLS) Yes, I use the latest version and I don't use Docker No, there is nothing interesting in the log

proxy works on official Telegram and Plus Most of the time, when I open Telegram after a few hours, I see this error (response hash mismatch)

After connecting to a proxy with the official source or Erlang that error is cleared and I can connect to python proxy

Also, my friends with Telegram X have the same problem with different phones and ISPs

[alexbers]

could you please try to add IGNORE_TIME_SKEW=True in the end of config.py and restart the proxy. Does the problem persists?

[MAHDITX]

could you please try to add IGNORE_TIME_SKEW=True in the end of config.py and restart the proxy. Does the problem persists?

I tested it and it works this "TIME_SKEW" does it effect on filtering?

[alexbers]

some clients on telegram X are trying to reach the proxy with the bad time. This is detected as a replay-attack to detect the proxy. The IGNORE_TIME_SKEW=False disables this protection

[skipik]

The IGNORE_TIME_SKEW=False disables this protection

Actually =True in this case disables the protection. I think you misspelled :-)

[alexbers]

Yes, you are right