shout icon indicating copy to clipboard operation
shout copied to clipboard

Reconnect to a server.

Open gravypod opened this issue 9 years ago • 9 comments

I seem to get an error where I see "Connection error." every time I try and send a message.

The only way to fix this is by restarting shout.

Is there a way to reconnect to a server or a way to fix this bug?

Thanks for your time.

gravypod avatar Feb 26 '16 03:02 gravypod

:+1: Given the fact that freenode is pretty unreliable... It would be nice to see that your disconnected instead of finding out hours later by trying to send a message.

Or perhaps be able to try to reconnect for some time.

Rosiak avatar Feb 28 '16 01:02 Rosiak

+1, this has been happening to me. Shouldn't it just automatically reconnect? Reloading the page, signing out/back in didn't fix the issue, I had to reload the server process.

fletom avatar Feb 29 '16 22:02 fletom

It probably won't be merged to master for a while, but you can always pull this and run Shout from source: https://github.com/erming/shout/pull/541

MaxLeiter avatar Mar 01 '16 02:03 MaxLeiter

How come that can't get pushed out as a release? @erming ?

fletom avatar Mar 11 '16 18:03 fletom

+1, this issue would appear to be a "block" severity level since the one of the main features is to be able to have shout-irc running and constantly connected.

scottHargus avatar Mar 15 '16 13:03 scottHargus

As a note, reconnection support was added to Lounge in 2.0

MaxLeiter avatar Oct 03 '16 05:10 MaxLeiter

@MaxLeiter Thank you for the notification. :heart:

@gravypod This issue can be closed then, right?

fnkr avatar Oct 03 '16 08:10 fnkr

@fnkr Well, technically, it's not fixed in Shout, but in a fork. So it would be fair to leave the issue open unless @erming wants to officially stop development on Shout and state that all unresolved issues will forever remain so. 😉

dgw avatar Oct 03 '16 09:10 dgw

@dgw Oops, my bad. I tought we were talking in thelounge/lounge.

fnkr avatar Oct 03 '16 11:10 fnkr