Unexplained nick changes

[Skook]

Hi Everyone.
Last night I compiled one of these UnrealIRCD servers with the Anope services. Everything went well, with both ircd and services running great.
I was able to login with AIRCD client, create and register a nick with nickserv.
I'm only having one problem, even after identifying, Nickserv eventually starts changing my nick to "guestxxxx".
It's impossible for my nick to already be in use, I'm the only one on it, it's just a private project. It even changes my nick after /oper to IRC OP status. I'm kind of stumped on this one. Went through both unreal and services conf files and can't find anything relevant.
Edit: Just to clarify, this is on a Debian server. I'm also not new to this kind of thing. I used to have a ircd running back in 1990's with bahamut and the old ircservices (by Church).

Here's the events that happen after I login; (passwords redacted)

[16:07:55] * There are 1 users and 7 invisible on 2 servers
[16:07:55] * 7 operator(s) online
[16:07:55] * I have 1 clients and 1 servers
[16:07:55] * Current local users 1, max 2
[16:07:55] * Current global users 8, max 9
[16:07:56] * Skook sets mode: +iwxz

[16:06:39] -NickServ- This nickname is registered and protected. If it is your
[16:06:39] -NickServ- nick, type /msg NickServ IDENTIFY password. Otherwise,
[16:06:39] -NickServ- please choose a different nick.
[16:06:39] -NickServ- If you do not change within 1 minute, I will change your nick.

[16:08:15] -> *NickServ* IDENTIFY *********
[16:06:59] -NickServ- Password accepted - you are now recognized.
[16:08:16] * You are now logged in as Skook.
[16:06:59] * NickServ sets mode: +r

[16:08:35] -> *NickServ* SET KEEPMODES ON
[16:07:19] -NickServ- Keep modes for Skook is now on.
[16:09:14] * Skook sets mode: +ost

[16:09:14] -> Oper Skook ********
[16:09:14] * +bcdfkoqsBOS Server notice mask
[16:09:14] * You are now an IRC Operator

[16:07:57] * Now talking in: #opers
[16:07:57] * Skook joins #opers

[16:09:14] * #opers has modes: +nt
[16:09:14] * #opers created on Fri Jul 04 16:07:57 2025

[16:23:23] -NickServ- Your nickname is now being changed to Guest31613
[16:23:23] * Skook_ is now known as Guest31613
[16:25:01] * Disconnected..
[16:25:08] * Rejoined #opers
[16:23:52] * Now talking in: #opers
[16:23:52] * Guest31613 joins #opers
[16:25:09] * #opers has modes: +nt
[16:25:09] * #opers created on Fri Jul 04 16:07:57 2025

[rafaelgrether]

Hi,

I suggest you to check your services log to get more details. Time on your log is a bit strange.
I think you disconnected and reconnected automatically. In reconnection you will need to identify yourself again, otherwise your nickname will change (unless you use SASL).

~ devnull

[Skook]

Ya, sorry, that "strange time" entries was a "copy and paste" mistake, that I made when posting this. Sorry, didn't notice it until you mentioned it, haha.
My nick gets an actual "kick" when it changes it and then reconnects. But in some testing, if I log in, BUT do not join a channel, nothing happens, but as soon as I join a channel, the nick gets changed. (then disconnects).

[PeGaSuS]

I assume that you have this line to match Anope here.

I'f your services are called services.example.com they must match in both ends.

You also need your ulines block to contain the services server name, like:

Code: Select all

ulines {
    services.example.com;
}

[Skook]

I found a fix for it with extensive googling. All I had to do was type /nickserv set keepmodes on and the problem seems to have gone away, haha
I have no idea why that is a solution, but it worked for someone else with same problem.
Thanks for your input guys. I appreciate it.

[PeGaSuS]

KEEPMODES doesn't really have anything to do with identification, etc. It only serves to keep non-default modes active between sessions.

I suggest you to really have a look at the configs, thoroughly, to find out possible flaws/misconfigurations.

If anything, feel fre to post your configs (redact any sensitive data) so someone can take a look at them, since two pairs of eyes are better than one.