painor
painor
when you download a file from a different DC you need to create a new connection. That's what line does. It tries to create a new connection in the new...
yes, clearly there is an issue somewhere in the library's code. how many connections do you have open btw.? Also do you have any specific attributes when creating a new...
``` connectionRetries: 2, requestRetries: 2, autoReconnect: false, ``` can you put theses to 5 and true and see if the error stays?
I've pushed a potential fix to the latest version, can you try it out? I've been trying to reproduce the issue but I'm not able to.
> I have the same issue on latest version `2.8.2` from npm. I'm using single account but did received FLOOD_WAIT with 86400s. The client never waits for this time and...
> Well, after checking the source code I see that FLOOD_WAIT errors are handled only in the `invoke` function, but not in `connect`, I just added something like `onError: async...
PEER_FLOOD is related to the account that makes the request not the IP. even if you used proxies it would not change the error. in any case if you want...
not really. this is an anti spam filter by telegram. They do not want people to send 100 messages. Maybe try using bots instead of users.
hmm that's weird. does this happen even if you don't use ignoreMigrated? can you look into your dialogs and see if there is any dialogs that is deleted/unaccessible ?
are you able to use telegram normally without a proxy? are you maybe using ipv6 ?. try pinging that IP and see the result.