rate limit exceeded, code 413, with one contact, others work #2913
Comments
|
#2914 is a duplicate of this. |
|
@bxkx I see that you've cut your log down to only the most recent entries. If you could provide the full log, it would give some good background. For example, when was the last time you successfully sent a message to the contact whose number ends with @tuxayo @rfc805 @KolyaKorruptis @rainerzufall I see that you've liked the original issue - I presume that you've run into this issue as well? Please provide your logs, as well any information about the category of contact you're seeing this with. We need more information to help track this down. |
|
Not sure what 'categories' there are - from one signal user to another signal user. As of 1.18.x I get a 413 on any attempt to send any message. Using 1.17 all is fine. I submitted debug logs from the application, but it's unclear to me if those actually go anywhere. |
|
@rfc805 When you upload a debug log, all you do is put it online. You need to give us the URL and give us some additional context and then we'll take a look at the job. Regarding 'categories' - We're looking for any way to assign some common traits to the kinds of people you see this error with. Are they people with lots of devices? Just one device? People you've never messaged rom desktop before, or only ones you have messaged from this desktop instance before? Are they users who have never messaged you back, or only ones where you have exchanged messages back and forth? |
|
Ah, I talk with them on signal all the time. I can still see message I send them from my mobile device, and I can see their inbound messages. I can not successfully send any messages, though I can retry as many times as I like. |
|
I'm experiencing a very similar issue on my Signal Desktop ever since I upgraded to 1.18.x. However, in my case it's the sync message to the sibling devices fail to be sent. FYI, I'm on Signal Android Beta and Signal Desktop Beta. |
|
I've provided several debug logs in #2914 as well. |
|
Similar issue here as well. I have 5 linked devices. One device is windows, the others are linux. I cannot send a message to myself (this worked before 1.18.x). My friend is also unable to send me messages from a windows box, but from their phone it works find. |
|
I am unable to figure out how to rollback my version on linux. The new version 1.18.0 seriously breaks things. Is there a way to go back that I am not seeing? I understand the need for security updates, but there does not seem to be any recourse when essential functionality breaks. |
|
I also get this bug but it turns out that messages are still sent to all recipients. (by looking at the message info) |
|
Does anyone have examples where server delivery receipt isn't here? (after one minute) |
|
No. The messages that fail for me don't get send at all. |
|
I've left messages for days, the only information on a failed message that appears under the "more info" button is: Rate limit exceeded, please try again later. (original: promiseAjax: invalid response; code: 413) And I can confirm the recipients do NOT receive the message. I've been using my phone since 1.18.0 released. |
|
I got a new error on receive on my desktop client, "Bad Mac" I reset the session via the desktop app, and subsequently lost the ability to receive from the impacted user as well as send. This time however, it was both on my phone and my desktop app. So whatever this is, it seems to be impacting the desktop's ability to properly handle the encryption keys. |
|
@azulskyknight Please provide debug logs from both your phone and desktop app. This appears to be a worse behavior than before! |
|
I think I have the desktop app working again (receive only) after having it delete all settings and relinking it to my phone. But, I did get a debug log before I cleared the desktop client here: https://debuglogs.org/0d6e1d504eb0850aca9e1d454efadcd607bd3cb7c381e23e9d731ceaf98c74b0 And, a debug from my mobile device is here: https://debuglogs.org/0fed7bfd3ee4e90e110d9c2db3b43957c17e39d096348cc2d42a3008b98fea56 |
|
@scottnonnenberg I believe I am seeing this behavior as well and it's especially frustrating because I don't know who it is impacting and who it is not. My clients (1 on phone & 2 on desktop) seem out of sync and some clients have no issues while others only see portions of a conversation. For example, in 1 group chat with 2 others (3 total) I was seeing my own messages and the messages of 1 other person ... only to later find out from talking to the 3rd contact in person they were also posting messages in the chat that the 2nd person was seeing but I was not. In another example, one of my contacts can send & receive messages to me on their phone client, but their desktop client cannot send to me (gets the rate limited error message). I don't see a way to get debug logs from a desktop client, but I grabbed on from this contact's phone client: https://debuglogs.org/8a6b99cd0c2b7f93290210c5823e92376e5540e5ad3d8c0bbc560685e82486e9.zip |
|
@fleish debug logs on the Windows desktop client are under the view menu |
|
Thanks @azulskyknight Debug from one of my desktop clients: https://debuglogs.org/76ec513d190335a3b15a75fb8413a1b58c423ddf0bcb757b3a537c53ffa4c28f Debug from the desktop client mentioned in "another example" from my last post where I provided their mobile debug logs: https://debuglogs.org/2303498cd6f359de5d8f297989dee3f8e25b2fe535b056c3f88e300fd794056d |
|
Just got Signal v1.18.1 on my desktop, it seems to have cured me. The contact that I was having trouble communicating with isn't generating errors anymore, but he's not online to confirm reception. However, what I type into my desktop app is showing up on my phone now, so again, seems to be working. |
|
@azulskyknight You beat me to it! |
|
@scottnonnenberg, I just confirmed working communications with the formerly broken contact, and my phone is happily keeping pace as well untouched as expected. Sure looks like you can stick a fork in this one from my end! |
|
Can confirm it seems to have fixed mine as well. Thanks @scottnonnenberg |
|
Fixed issue from #2936. Thanks |
|
What was the issue? I'm hitting the rate limit with the libsignal-service library and I'm wondering if it might be caused by the same issue: signalapp/libsignal-service-java#67 Apparently this is fixed in v1.18.1? I can't see anything obvious that would have caused or fixed the issue when doing a comparison with v1.18.0, but perhaps the issue was fixed earlier. |
|
@jmnyv It was a database problem, a problem with serialization of the session data. |
|
So, Is this problem a server-side or client-side database problem? I'm having same trouble on my local environment. Works fine with mobile calls but fails on desktop message send calls. May I ask how did you fix the problem? Thanks. |
|
@shyos Please enter a new bug with a full debug log, following the bug template. You're very likely running into a separate issue. |
|
FYI: This bug has not yet been fixed. Why has it been closed? |
|
@jkpubsrc We want new people who run into it to file new bugs, following the bug template. I'm going to lock this now. |
Bug description
I booted up my computer, started Signal, wrote a message to a contact, but it failed, saying "Rate limit exceeded, please try again later. (original: promiseAjax: invalid response; code: 413)" That was almost a day ago and it is still not working. It is working with other contacts, though. I can send messages from the phone and the messages also show up in the Desktop client as well as the answers of that contact.
Steps to reproduce
Just start Signal, try to send message...
Actual result:
Failed to send, Rate limit exceeded, please try again later. (original: promiseAjax: invalid response; code: 413)
Expected result:
Sent message
Screenshots
Platform info
Signal version:
1.18.0
Operating System:
Windows 10 1709
Linked device version:
4.30.6
Link to debug log
https://debuglogs.org/8c0172cccbcbe6483c1264edd7ed401c438c873d9fb8cd42c00456351078660d
The text was updated successfully, but these errors were encountered: