Skip to content
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

Connection drops with medium sized files #28430

Open
UpscaleAnon opened this issue Sep 19, 2024 · 3 comments
Open

Connection drops with medium sized files #28430

UpscaleAnon opened this issue Sep 19, 2024 · 3 comments
Labels

Comments

@UpscaleAnon
Copy link

UpscaleAnon commented Sep 19, 2024

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
Copy link
Collaborator

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

@UpscaleAnon
Copy link
Author

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
Copy link

AndryS0 commented Sep 25, 2024

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

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

No branches or pull requests

3 participants