-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Unable to send messages due to not being able to retrieve private keys because rate limiting. #2180
Comments
5-10 minutes later, I see that it retreieved the keys, and I can send messages again. Update: from the desktop, phone is still wonky. The messages from the phone are being received, but on the phone they show as not sent. Phone debug log:
|
Rebooted phone, reset sessions again, finally working phone and desktop |
Thanks for letting us know about this, glad it ended up in good shape. Can you tell us any more about what you did right before all this to cause the rate limiting to kick in? |
I was attempting to back everything up before I wasted my messages and started over.. So I did it i believe the wrong way. I rolled back to the chrome app, so that I could export the DB again.. And then reimported it into desktop. It apparently tried to pull a bunch of messages from the missing time inbetween the previous export, and the time I rolled it back. Then when I reimpoted the new backup, it ratelimited me. |
Bug description
Unable to send messages after opening a client that had not synched in a month
Steps to reproduce
Actual result:
Every message including (Secure session Reset) Fails.
Expected result:
The message sends
Screenshots
Debug log:
Platform info
Android & Desktop on windows
Signal version:
4.16.9 on android 8.0
1.6.1 on Windows 10
Link to debug log
Android log: hastebin.com/uhoqoxivoq
Windows desktop log above.
The text was updated successfully, but these errors were encountered: