Skip to content
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

No longer seems to recognise rapidly when your connection returns #1702

Closed
matrixbot opened this issue Jun 28, 2016 · 8 comments
Closed

No longer seems to recognise rapidly when your connection returns #1702

matrixbot opened this issue Jun 28, 2016 · 8 comments

Comments

@matrixbot
Copy link

Created by @ matthew:matrix.org.

For instance: my connection flakes out; a sending message goes red and i get told that it'll get sent when the connection returns. My connection returns, but it's not sent. I manually resent it from the contextual menu, and it successfully sends. The warning still tells me that the connection hasn't returned, and i have to stare at the warning for another 10-30s until it decides the connection's back.

@ara4n
Copy link
Member

ara4n commented Jul 31, 2016

I saw this many times tonight when restarting synapse & synchotron. The act of successfully sending or re-sending a message doesn't tell vector that the connection is back.

@lukebarnard1 lukebarnard1 changed the title Vector no longer seems to recognise rapidly when your connection returns Riot no longer seems to recognise rapidly when your connection returns Mar 30, 2017
@lampholder lampholder modified the milestones: RW003 - candidates, RW004 - candidates Apr 21, 2017
@MurzNN
Copy link
Contributor

MurzNN commented Jul 14, 2017

Got the same problems - after short disconnects - Riot stay disconnected long time. Maybe as workaround - add "Force reconnect" button to offline message in interface?

@aaronraimist
Copy link
Collaborator

Is anyone still experiencing this? It works for me. Riot reconnects very quickly.

@jryans jryans added P2 and removed P1 labels Apr 29, 2021
@jryans jryans changed the title Riot no longer seems to recognise rapidly when your connection returns No longer seems to recognise rapidly when your connection returns Apr 29, 2021
@kittykat
Copy link
Contributor

Re-sends instantly over here so closing issue

@krux02
Copy link

krux02 commented Nov 2, 2022

I have this issue today. I don't know what the problem is. But it just won't reconnect or try to reconnect. Yesterday I still had a connection. Doday I don't get any. I don't get any feedback on what the actual problem is (no visual error message) and I don't have a reconnect button. It seems like the program just refuses to connect even though it could.

@kittykat
Copy link
Contributor

kittykat commented Nov 2, 2022

I have this issue today. I don't know what the problem is. But it just won't reconnect or try to reconnect. Yesterday I still had a connection. Doday I don't get any. I don't get any feedback on what the actual problem is (no visual error message) and I don't have a reconnect button. It seems like the program just refuses to connect even though it could.

There's an update to matrix.org happening right now. You're probably experiencing the downtime from that if your account is registered on matrix.org

@AppTester7
Copy link

I get this issue on at least one of my PC's when i have the same account logged on on both PCs on element

"Connectivity to the server has been lost"

I was recommended to goto a non-matrix server due to speed constraints on matrix.org servers alledgedley being the culprit with delays
so i registered with a new account on envs.net

It makes no differance

I have to manually log out and log back in again - everytime on one of my PC's

If i only have 1 PC up and running with element then i dont get this error

@AppTester7
Copy link

I get this issue on at least one of my PC's when i have the same account logged on on both PCs on element
"Connectivity to the server has been lost"

I was recommended to goto a non-matrix server due to speed constraints on matrix.org servers so i registered a new acconut on envs.net
It makes no differance at all
I have to manually log out and log back in again - everytime on one of the PC's
If i only have 1 PC up and running with element then i dont get this error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants