Anope IRC Services

Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1] 2 3 ... 10
 1 
 on: Yesterday at 11:38:24 PM 
Started by Abner - Last post by Abner
That message is sent when you have registration set to require admin confirmation. It cannot be changed from within the config; only within the code itself and that is not a supported method.

Ok thanks mate.

 2 
 on: Yesterday at 11:37:54 PM 
Started by Abner - Last post by Abner
Guys,

When I into at any channel, #Ajuda as a example, I receive:

Now talking on #Ajuda
* myirc.network sets mode +n on #Ajuda
* myirc.network sets mode +t on #Ajuda

I registered this channel and I receive:

* ChanServ sets mode +r on #Ajuda

john registered his nick and received this:

* john sets mode: +r

When john try to access the #ajuda, he receive:

* You were kicked from #Ajuda by ChanServ (You are not permitted to be on this channel.)

#Ajuda +nrt

If I ( channel founder ) leave the #Ajuda and enter again, I have this:

* Now talking on #ajuda
* myirc.network sets mode +n on #ajuda
* myirc.network sets mode +t on #ajuda
* services.myirc.network removes channel operator status from "abner"
* *** Notice -- TS for #ajuda changed from 1508277878 to 1508277137
* ChanServ sets ban on *!*@abner-ip
* ChanServ sets mode +r on #ajuda
* ChanServ sets mode +n on #ajuda
* ChanServ sets mode +t on #ajuda

When I clear the modes using:

/msg operserv mode #Ajuda CLEAR ALL

I have:

ChanServ removes ban on *!*@john-ip
* ChanServ sets mode -n on #Ajuda
* ChanServ sets mode -r on #Ajuda
* ChanServ sets mode -t on #Ajuda

When john try again into in #Ajuda, I have:

* john (~john@john-ip) has joined
* ChanServ has kicked john from #Ajuda (You are not permitted to be on this channel.)
* ChanServ sets ban on *!*@john-ip
* ChanServ sets mode +r on #Ajuda
* ChanServ sets mode +n on #Ajuda
* ChanServ sets mode +t on #Ajuda

Chanserv disobey the CLEAR command. Every channel that i register I have this "problem", my confs:

ircd.conf

/*
 * service {}: specifies a server which may act as a network service
 *
 * NOTE: it is very important that every server on the network
 *       has the same service {} block.
 */
service {
        /* name: the actual name of the service. Wildcards are not allowed. */
        name = "services.myirc.network";

        /* The 'name' directives can be stacked. */
        name = "stats.example.net";
};

chanserv.conf

/*
         * Modes that are required to be set and only set on all registered channels.
         * These modes can not be locked or unlocked. The registered channel mode is
         * automatically always required, if such a mode exists.
         */
        require = "r"

nickserv.conf

 /*
         * If set, Services will set the channel modes a user has access to upon identifying, assuming
         * they are not already set.
         *
         * This directive is optional.
         */
        modeonid = yes

        /*
         * If set, Services will set these user modes on any user who identifies.
         *
         * This directive is optional.
         */
        modesonid = "+r"

Thank you for any help.

 3 
 on: Yesterday at 03:46:47 AM 
Started by Abner - Last post by Abner
It means you don't have a vHost set with HostServ yet. Please check out the Wiki - HostServ and perhaps read through some other sections to get familiar with the basic feature-set and commands.

I followed your comment, When I use

/msg HostServ SET Abner abner@myvhost.network

I have:

<HostServ> Your IRCd does not support vIdent's, if this is incorrect, please report this as a possible bug.

But When I get the BotServ List I have the nick and the mask:

<BotServ> Bot list:
<BotServ> Nick      Mask
<BotServ> BotServ   services@myvhost.network
<BotServ> ChanServ  services@myvhost.network
<BotServ> Global    services@myvhost.network
<BotServ> HostServ  services@myvhost.network
<BotServ> MemoServ  services@myvhost.network
<BotServ> NickServ  services@myvhost.network
<BotServ> OperServ  services@myvhost.network
<BotServ> 7 bots available.

The mask isn't the vident´s?

 4 
 on: October 15, 2017, 11:42:56 PM 
Started by GTAXL :) - Last post by genius3000
With some advice from Adam I cleaned up the code and made a couple improvements over the first commit to my GitHub repo. The module is now published on the Modules site at https://modules.anope.org/index.php?page=view&id=281.

 5 
 on: October 15, 2017, 10:27:06 PM 
Started by Abner - Last post by genius3000
Another question, where I can change this message "All new accounts must be validated by an administrator. Please wait for your registration to be confirmed." ?

That message is sent when you have registration set to require admin confirmation. It cannot be changed from within the config; only within the code itself and that is not a supported method.

 6 
 on: October 15, 2017, 10:24:41 PM 
Started by Abner - Last post by genius3000
It means you don't have a vHost set with HostServ yet. Please check out the Wiki - HostServ and perhaps read through some other sections to get familiar with the basic feature-set and commands.

 7 
 on: October 15, 2017, 10:11:00 PM 
Started by Abner - Last post by Abner
Mates,

I identify at NickServ, OperServ and as "oper", but when I go to Vhost in my nick using /msg hostserv on, I have this error:

<HostServ> Please contact an Operator to get a vHost assigned to this nick.

What does mean?I´m the Operator.

Thank You

 8 
 on: October 15, 2017, 05:53:47 PM 
Started by Abner - Last post by Abner
Another question, where I can change this message "All new accounts must be validated by an administrator. Please wait for your registration to be confirmed." ?

 9 
 on: October 15, 2017, 05:42:19 PM 
Started by Abner - Last post by Abner
Seeing your later post, I assume you figured out that you need a Services Oper block with the correct permissions to be able to see the full Nick list and to sort it to, say only UNCONFIRMED. As a normal user (to Services), 'NickServ LIST *' will only show registered nicks that don't have PRIVATE set on.

Thank You mate.

 10 
 on: October 15, 2017, 05:31:04 PM 
Started by Abner - Last post by Abner
Have a look at this reply from another thread. Once you fix the issue, you will need to restart Services as you don't currently have a Services Oper block to use the RELOAD command.

Jesus, thank you so much.

Pages: [1] 2 3 ... 10