Signal-Desktop icon indicating copy to clipboard operation
Signal-Desktop copied to clipboard

Sometimes messages don't get send

Open dataprolet opened this issue 1 year ago • 2 comments

Using a supported version?

  • [X] I have searched searched open and closed issues for duplicates.
  • [X] I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

Overall summary

While using Signal-Desktop at some point the application is not sending messages anymore or rather takes extremely long (multiple minutes) for sending a message. Receiving messages works fine though. As random as the issue occurs it also solves itself.

EDIT: This is neither related so suspend/resume as in #7041 and #6103 nor to leaving the system running for a long time as in #6577.

Steps to reproduce

It's hard to reproduce because it seems to be random when the issue occurs. At one point I can send messages just fine and the next message doesn't get send.

Expected result

Well, messages should be sent immediately.

Actual result

Messages take multiple minutes to get send.

Screenshots

No response

Signal version

7.33.0

Operating system

Arch Linux

Version of Signal on your phone

7.23.1

Link to debug log

No response

dataprolet avatar Nov 16 '24 10:11 dataprolet

Sorry this is happening for you, but more debug info is needed to help us track this down.

The next time this happens, can you please generate a debug log (Menu -> View -> Debug Log) and find the stuck message's timestamp (hover over the message, click triple dot menu -> Info -> copy Sent timestamp) then share these 2 things? Alternatively you can also send a message with these items to Signal Support [email protected]. Thanks!

ayumi-signal avatar Nov 18 '24 17:11 ayumi-signal

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] avatar Feb 16 '25 18:02 stale[bot]

Here's the debug log, the message is 1741108043416:

debuglog.txt

dataprolet avatar Mar 04 '25 17:03 dataprolet

@dataprolet your logs suggest that we were unable to connect a functioning websocket to our server... is there anything unusual about your network or anything that may have changed that coincides with those messages not being sent?

trevor-signal avatar Mar 05 '25 17:03 trevor-signal

No, not that I'm aware of. I'm using Pi-hole in my local network but besides that nothing unusual. Is there anything that I can do to further debug the issue?

dataprolet avatar Mar 06 '25 11:03 dataprolet

No, not that I'm aware of. I'm using Pi-hole in my local network but besides that nothing unusual. Is there anything that I can do to further debug the issue?

It would be interesting to see if the problem persists with Pi-hole disabled (though I understand if you'd rather not do that).

trevor-signal avatar Mar 06 '25 22:03 trevor-signal

I disabled Pi-hole for my Desktop-PC and I'm having the issue still.

dataprolet avatar Mar 17 '25 12:03 dataprolet

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] avatar Jun 15 '25 19:06 stale[bot]

This issue still persists and I need further assistance debugging it.

dataprolet avatar Jun 16 '25 09:06 dataprolet

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] avatar Sep 14 '25 19:09 stale[bot]

This issue has been closed due to inactivity.

stale[bot] avatar Sep 21 '25 22:09 stale[bot]

I think I fixed it by lowering my MTU because of issues regarding DS-Lite.

dataprolet avatar Sep 24 '25 09:09 dataprolet