Bug #3577
closed(for servers I have saved in Server List) it connects ok on startup (i.e. it automatically sends IDENTIFY), but it asks to manually IDENTIFY on reconnect.
0%
Description
Using 2.9 beta 2017/7/11 x64 on win10.
I've noticed this issue on a server I have saved in Server List,
i.e. it connects ok on startup (i.e. it automatically sends IDENTIFY), but it asks to manually IDENTIFY on reconnect.
I can manually connect to it via
/server -l 4 irc.crackwatch.me:+6697 my_password -jn #general
Here are screenshots from the Server list:
On the 2nd screenshot, for the "Login method", I had "Default". I also tried switching to "NickServ (/NickServ + Password)" but the issue still occurs,
On AdiIRC startup it connects ok.
But, afterwards, i.e. during the session, if for some reason it gets disconnected, it "fails" to reconnect, (the: Options|Server|"Reconnect on server disconnect" is enabled )
because I get:
Nick _ isn't registered.
You need a registered nick to join that channel.
and after 1-2 minutes I also get:
This nickname is registered and protected. If it is your nick,
type "/msg NickServ IDENTIFY password".
Otherwise, please choose a different nick.
So, I have to manually send the following in order to connect:
/msg NickServ IDENTIFY my_password
I suppose I could use something like the following in the 'Commands' tab("Run these commands on connect"):
on *:CONNECT:{
if (CrackWAtch isin $server) {
/msg NickServ IDENTIFY my_password
}
}
but is this really necessary?
I mean, since the password is already saved, could AdiIRC automatically submit the saved password on reconnect? (that is my suggestion).
Updated by Per Amundsen over 7 years ago
- Category set to Interface
- Status changed from New to Assigned
- Assignee set to Per Amundsen
Updated by Per Amundsen over 7 years ago
It's okay, was no need to delete :P but thanks for making a new issue with such details.
The thing I said before is still true in this case, when reconnecting and nick is in use, adiirc will use a alternative nick, and that nick can't be authed of course.
Solution would be to either use SASL when available or possibly could detect when regain nick is able to recover main nick and then send the auth.
Updated by Kostas K over 7 years ago
Per Amundsen wrote:
In theory adiirc could send nickserv auth whenever your nick changes to the original nick again, it's something I am gonna look into
Thank you.
Per Amundsen wrote:
The thing I said before is still true in this case, when reconnecting and nick is in use, adiirc will use a alternative nick, and that nick can't be authed of course.
Solution would be to either use SASL when available or possibly could detect when regain nick is able to recover main nick and then send the auth.
Could you please explain why it has to switch to an alternative nick?
I mean:
suppose I'm initially connected as nick_1.
It gets disconnected so I get this:
[12:59:58] * Disconnected..
[12:59:58] * Retry #1 in 5 seconds
[13:00:03] * Looking up irc.crackwatch.me..
[13:00:03] * Connecting to irc.crackwatch.me(99.231.211.104) port +6697..
[13:00:24] * Unable to connect to server: irc.crackwatch.me
[13:00:24] * Disconnected..
[13:00:24] * Retry #2 in 5 seconds
[13:00:29] * Looking up irc.crackwatch.me..
[13:00:29] * Connecting to irc.crackwatch.me(2607:fea8:4e5f:fde7:224:81ff:fec1:6306) port +6697..
[13:00:31] -irc.crackwatch.me- *** Looking up your hostname...
[13:00:31] -irc.crackwatch.me- *** Couldn't resolve your hostname; using your IP address instead
[13:00:31] * nick_1 Nickname is already in use.
...
[13:00:34] -NickServ- Nick nick_2 isn't registered.
[13:00:34] * #general You need a registered nick to join that channel.
[13:00:34] * No one in your notify list is on IRC
[13:01:10] * Your nick is now nick_1
[13:01:10] -NickServ- This nickname is registered and protected. If it is your
[13:01:10] -NickServ- nick, type /msg NickServ IDENTIFY password. Otherwise,
[13:01:10] -NickServ- please choose a different nick.
Why does it have to switch to the 1st alternative nick and then switch back to the original one. whenever it disconnects from the server?
Updated by Per Amundsen over 7 years ago
The reason is, when you timeout or connection drops, it takes a while for the irc server to register you are gone and kick/ping timeout the previous nick. Typically a minute or so.
Updated by Kostas K over 7 years ago
Per Amundsen wrote:
The reason is, when you timeout or connection drops, it takes a while for the irc server to register you are gone and kick/ping timeout the previous nick. Typically a minute or so.
Thanks for explaining and for always being willing to help :)
Updated by Per Amundsen over 6 years ago
- Status changed from Assigned to Invalid
Looks like we figured this one out, closing :)