Anope IRC Services
Anope Support => 2.0.x/1.9.x Support => Topic started by: Teddy on August 05, 2021, 06:08:56 PM
-
Hi all,
i used Anope 2.0.9, the link is correct, services are linked but steel not reuning.
They all joined the chanel #service but when you try a command ... it don't work so you can't register a nickname or a chanel, not using operserv too ... anybody seen this issue before ?
Could you help me please ?
-
can you let us know how did you check that anope is running?
also:
did you oper up on ircd side? did you see the server notices about the link?
can you do a /whois nickserv ? if so, can you /msg nickserv help register ?
you could also check and ircd's and anope'slog for more details.
-
Hi Lord235,
Thanks a lot for your answer.
i'm oper and can see services linked. All services joined #services channel.
When i /whois NickServ :
* [NickServ] (services@services.nightmare.fr): Nickname Registration Service
* [NickServ] is using modes +o
* [NickServ] is connecting from *@services.nightmare.fr
* [NickServ] @#services
* [NickServ] services.nightmare.fr :Services du réseau irc.nightmare.fr
* [NickServ] is an IRC Operator
* [NickServ] Fin de la liste WHOIS
But when i do a /msg NickServ help register for exemple here is the message from nickserv
>NickServ< help register
-NickServ- Unknown command help register. "/msg NickServ HELP" for help.
Thanks for your help
-
and what does "/msg NickServ HELP" say?
also: are you using a kinda default config, or you modified it like not all ppl can access to services?
-
ah never mind.. you modified it, it's clear..
using modes: +o
missing network service swhois.
standard should look like this:
NickServ is services@services.*.*.eu * nickname registration service
NickServ is using modes +ioqS
NickServ is connecting from *@services.*.*.eu
NickServ on ?@#*
NickServ using *.irc.*.eu services for irc.*.*.eu
NickServ is an IRC Operator
NickServ is a Network Service
nickserv End of /WHOIS list.
you missing user modes and so i don't know what else you could have changed.
-
Hi Lord235,
I removed the +o mode and now the /whois NickServ is the same than yours
* [NickServ] (services@services.XXX.fr): Nickname Registration Service
* [NickServ] is using modes +ioqS
* [NickServ] is connecting from *@services.XXX.fr
* [NickServ] !@#services
* [NickServ] services.XXX.fr :Services du réseau irc.XXX.fr
* [NickServ] is an IRC Operator
* [NickServ] is a Network Service
* [NickServ] Fin de la liste WHOIS.
But the problem is the same, any command tried, always the same message "Unknow command" for any service of Anope, it's really strange
-
can you pastebin and share the link of your nickserv.conf ?
-
Hi Lord235,
My nickserv.conf : https://pastebin.com/HnNjnekq
Best regards
-
hehe. i expected problems here, but can't see any. :(
can you please do a
/msg OperServ modinfo ns_register
?
for that you need to be opered up via anope too. (having services root rights)
----
i have never run into such problem so i'm trying to debug.. :\
-
Hi Lord235,
Here is the message from /msg OperServ modinfo ns_register
>OperServ< modinfo ns_register
-OperServ- Password authentication required for that command.
Thanks for your help
-
yea. well. i told you that you need services root for that. :)
anyway.. without more info i have no clue about this prob. :\
lets see if someone else have any idea or run into this prob.
-
-OperServ- Password authentication required for that command.
This means you're not identified to services though or an OperServ password is set, don't remember exactly, but I believe that's the former.
The below only applies if you're using UnrealIRCd (I don't know the other IRCds syntax).
For what I can see, services seems to be U-Lined properly, but I'd double check if you have something like:
ulines {
services.domain.tld;
}
This is kinda puzzling me because the /nickserv help register should have still outputted the help on how to register a nickname.
Do you also have the following on your unrealircd.conf:
include "aliases/anope.conf";
-
Also check this setting:
https://github.com/anope/anope/blob/2.0/data/chanserv.example.conf#L127-L132