I've been using the lounge for some time now and ran into some reconnection issues. I've been told that this is the place to open an issue for that case, because reconnection is handled by this irc-framework. so here it is.
example:
I'm re-connecting to the irc network after my connection has been lost or dropped (connection reset by peer case again).
So my old connection is still alive on the irc-server and it needs a few more minutes until it ping-timeouts. until then, the irc-server doesn't allow me to connect with the same ip-address, because it allows only one connection per ip-address.
when I try to connect, this is what happens:
[020] * Please wait while we process your connection.
mynick: Nickname is already in use.
Closing Link: mynick[unknown@ip.host.com] (Too many host connections (local)) (irc)
Disconnected from the network, and will not reconnect. Use /connect to reconnect again.
At this point The Lounge does not try to reconnect anymore. it stays offline indefinitely.
But it should try reconnecting! After a few minutes the old connection drops out and I would be able to reconnect.
The initial irc connection/registration did not fail, I'm connected to the irc-network for a moment, but due to the old connecton I get kicked out.
This is important to distinguish: my irc-client somehow only tries to reconnect if the initial connection attempt did not work. in this case however, it actually did work for a moment, but the irc-server decides to close the connection which in the end has the same effect as a connection failure.
So I'll stay offline forever until someday I manually login to the lounge and type /connect. Needless to say that I expected to be able to read the irc/chan history when I came back, but TL wasn't connected, so there is nothing to read.
summa summarum: The lounge / the irc-framework needs to try reconnecting at an interval of like one to five minutes when the error is "too many host connections (*)"
I've been using the lounge for some time now and ran into some reconnection issues. I've been told that this is the place to open an issue for that case, because reconnection is handled by this irc-framework. so here it is.
example:
I'm re-connecting to the irc network after my connection has been lost or dropped (connection reset by peer case again).
So my old connection is still alive on the irc-server and it needs a few more minutes until it ping-timeouts. until then, the irc-server doesn't allow me to connect with the same ip-address, because it allows only one connection per ip-address.
when I try to connect, this is what happens:
At this point The Lounge does not try to reconnect anymore. it stays offline indefinitely.
But it should try reconnecting! After a few minutes the old connection drops out and I would be able to reconnect.
The initial irc connection/registration did not fail, I'm connected to the irc-network for a moment, but due to the old connecton I get kicked out.
This is important to distinguish: my irc-client somehow only tries to reconnect if the initial connection attempt did not work. in this case however, it actually did work for a moment, but the irc-server decides to close the connection which in the end has the same effect as a connection failure.
So I'll stay offline forever until someday I manually login to the lounge and type /connect. Needless to say that I expected to be able to read the irc/chan history when I came back, but TL wasn't connected, so there is nothing to read.
summa summarum: The lounge / the irc-framework needs to try reconnecting at an interval of like one to five minutes when the error is "too many host connections (*)"