search

erming / shout

Deprecated. See fork @ https://github.com/thelounge
MIT License
3.63k stars 273 forks source link

Reconnect to a server. #654

Open gravypod opened 8 years ago

gravypod commented 8 years ago

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.

Rosiak commented 8 years ago

:+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.

fletom commented 8 years ago

+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.

MaxLeiter commented 8 years ago

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

fletom commented 8 years ago

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

scottHargus commented 8 years ago

+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.

MaxLeiter commented 7 years ago

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

fnkr commented 7 years ago

@MaxLeiter Thank you for the notification. :heart:

@gravypod This issue can be closed then, right?

dgw commented 7 years ago

@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. 😉

fnkr commented 7 years ago

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