-
Notifications
You must be signed in to change notification settings - Fork 195
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
Desktop client doesn't receive messages / port issue #995
Comments
same message sync issue with 1.0.6. Need to restart the app to get new message |
I've seen this issue before but have been unable to reliably reproduce it |
Hello |
Yeah i'm going to try and get someone to look at this, it might get incidentally fixed when we finish the receiving pipeline refactor @msgmaxim , but I've definitely had this trigger after Session is open on desktop for 24-48 hours |
samething with v1.1.1 |
Is this issue NAT related? |
Session-desktop currently does not listen on any TCP or UDP ports, so you shouldn't need to port forward anything. |
I don't receive any messages from other person when using the desktop session which is linked to my phone. edit: edit 2: |
Hello |
We're looking into this issue :) |
Hello Reproduce: |
Same here with v1.3.0 |
Ok Idk how session actually work but If A is closed and B can receive msg this tell me session send msg to a dht or something |
If A sends a message to B then it will always be sent regardless if B was online or not. B however might not receive a message if it was expired on the storage server. This issue above is not related to sending, rather there's a bug which occurs in receiving after having session open for a long time which we haven't been able to reproduce consistently (and thus are still working to find out why it's occurring) |
@Mikunj " having session open for a long time" |
Right sorry i missed your comment describing that. We'll try and look more into this issue |
We've might have found a bug with the receiving, we've patched it up but will keep an eye out in testing if it still times out. If not then you'll get it in the next desktop release :) |
Hello |
Still same issue here. 1.4.0 and 1.4.1 same issue. Sent from A to B on same network. B does not receive new msgs from A When will this be fixed????? |
@Bilb My node does not receive any msg anymore. Lappy doesnt receive any msg from my desktop anymore and didnt get anything from you since "Mais si c'est l'histoire du focus dans les conversations. Ça devrait être résolu prochainement. On a gros refactor de l'App qui est en route" New Edit: Ok got all your msg but I had to restart session :/ New edit again: I receive nothing on lappy again. Restarting in a terminal shell for log |
Ok lappy doesnt receive new msg from desktop
|
heres the desktop output
|
I've finally found the issue. Its my iptables rules. When I set everything to ACCEPT session works fine, every msg are received. Both of my devices are set with these iptables rules and everything works fine, except for session. I wont set my iptables to ACCEPT everything in order for session to work. Im no dev neither a network pro. I took these iptables rules from whonix. What do I need to remove in order for session to work ?
|
See #1415 |
Hi. First, I love the app very user-friendly, good job
Im running the appimage. I've run 1.0.4 and 1.0.5 (same sync issue with both version)
I have 1 client running on main and another client running in virtualbox
I often have to restart the receiver side client in order for the app to sync a new message sent from the other client.
I've noticed that this sync issue occur when im not using the app for a period of time (idle) .
main run mx linux: OS: MX x86_64 Kernel: 4.19.0-6-amd64
vb run linuxlite: OS: Linux Lite 4.8 x86_64 Kernel: 4.15.0-91-generic
Thanks for session.
The text was updated successfully, but these errors were encountered: