telegramdesktop / tdesktop

Telegram Desktop messaging app
https://desktop.telegram.org/
Other
26.35k stars 5.24k forks source link

Connection drops with medium sized files #28430

Open UpscaleAnon opened 2 months ago

UpscaleAnon commented 2 months ago

Steps to reproduce

Upload files around 200-400MB

Expected behaviour

It should just upload and not disconnect constantly

Actual behaviour

After uploading 1 or 2 files around 200-400MB, it keeps disconnecting and needs approximately 36 seconds to reconnect, uploads 1 or 2 files, disconnects again, repeat. The same happens if you upload something like a thousand 1MB files, which is understandable, but 200-400MB files? This does not happen if I'm uploading files that are 1GB or bigger, because the upload is slow enough that it won't disconnect. Which makes no sense really, I wouldn't call uploading one file every 5-10 seconds "flooding", which is what the logs say I'm doing, as it's spamming this: -429 flood code returned! This has been happening for quite a while now, and it's starting to get annoying lol. Let me know if you want me to DM you full logs again

Operating system

Windows 10 Home 22H2

Version of Telegram Desktop

5.5.5

Installation source

Static binary from official website

Crash ID

No response

Logs

[2024.09.19 03:45:28] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:28] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:28] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:28] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:28] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:28] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:28] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:28] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:28] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:28] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:29] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:29] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:29] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:29] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:29] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:29] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:29] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:29] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:30] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:30] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:30] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:30] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:30] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:30] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:30] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:30] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:30] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:30] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:30] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:30] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:30] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:30] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:30] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:30] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:30] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:30] Protocol Error: -429 flood code returned!
[2024.09.19 03:45:30] Protocol Error: -429 flood code returned!
Aokromes commented 2 months ago

i confirm this bug, maybe telegram desktop is to agressive uploading?

UpscaleAnon commented 2 months ago

Just checked, and this 429 flood code shit appears even when you send big files like 4GB, but it at least doesn't disconnect for over half a minute, but stutters like once a second for maybe 100ms or so. But it's not nearly as much of an issue as medium sized files

AndryS0 commented 1 month ago

UDP: there is no 429 error in logs, so I think it's not related to this issue

AyuGram_jPCIns6jMk Can confirm it on AyuGram and web.telegram.org too, likely telegram backend issue. It's very disappointing because the only reason I bought premium is because of the high download/upload speeds that work every once in a while. Switching to different VPNs doesn't help, apparently the limitation is for the whole account

UpscaleAnon commented 1 month ago

UDP: there is no 429 error in logs, so I think it's not related to this issue Can confirm it on AyuGram and web.telegram.org too, likely telegram backend issue. It's very disappointing because the only reason I bought premium is because of the high download/upload speeds that work every once in a while. Switching to different VPNs doesn't help, apparently the limitation is for the whole account

Your gif isn't at all like the issue I mentioned, you just have obnoxiously slow speed. If you bought Telegram premium for the sake of faster upload speed, I believe you've been misled, as nowhere is it stated that premium gives you faster upload. Only faster download. I used to have those slow speeds too, but that was before telegram desktop got the upload update which significantly sped up the uploads. If you still have slow speeds, make sure you use telegram desktop and have it up to date, not some other third party software or the shitty web version.