CONNECT EJABBERD INSTALL
CONNECT EJABBERD PASSWORD

On '::' will mean listening for IPv4 traffic as well as IPv6 traffic. Note that on some operating systems and/or OS configurations, listening When the IP address is not specified, it will listen on Depending on the type of the IP address, IPv4 or IPv6 It is possible to specify a genericĪddress ('0.0.0.0' for IPv4 or '::' for IPv6), so ejabberd will listen The IP address can be represented as a string. To create and listen on a unix domain socket /path/to/socket. It can be a Jabber/XMPP standard port or any other valid port number.Īlternatively, set the option to a string in form 'unix:/path/to/socket' The port defines which port number to listen for incoming connections: Options for the TCP socket and for the listening module. Port, optionally also the IP address and/or a transport Protocols ejabberd will listen and what services will be run on them.Įach element of the list is an associative array with the following The listen option defines for which ports, addresses and network If you are using an old ejabberd release, please refer to the corresponding archived version of this page in the Archive. okie mismatches - that's the current rabbit I'm chasing down the hole.This section describes the most recent ejabberd version. There are hints from possibly related issues from ejabberd support that point to. node nodename ejabberd node name: 09:18:31.948 ** Connection attempt from disallowed node ** My steps on a clean installation of Fedora 21: In my case, it's doing *anything* with ejabberdctl - not just registering.

CONNECT EJABBERD PASSWORD

ejabberdctl register admin localhost password Version-Release number of selected component (if applicable):ģ. 14:57:42.557 ejabberd community is started in the node 14:57:42.557 Application ejabberd started on node 14:59:18.926 ** Connection attempt from disallowed node ** 14:57:30.188 Application lager started on node 14:57:30.257 Application sasl started on node 14:57:30.286 Application crypto started on node 14:57:30.354 Application asn1 started on node 14:57:30.354 Application public_key started on node 14:57:30.421 Application ssl started on node 14:57:30.450 Application p1_yaml started on node 14:57:30.482 Application p1_tls started on node 14:57:30.492 Application p1_xml started on node 14:57:30.498 Application p1_stringprep started on node 14:57:30.508 Application p1_zlib started on node 14:57:30.515 Application p1_cache_tab started on node 14:57:31.015 Application mnesia started on node 14:57:33.259 FQDN used to check DIGEST-MD5 SASL authentication: node nodename ejabberd node name: I see this in the log /var/log/ejabberd/ejabberd.log: spool dir Database spool dir: /var/lib/ejabberd

logs dir Directory for logs: /var/log/ejabberd ctl-config file Config ejabberdctl: /etc/ejabberd/ejabberdctl.cfg config file Config ejabberd: /etc/ejabberd/ejabberd.yml config-dir dir Config ejabberd: /etc/ejabberd Optional parameters when starting an ejabberd node: Live Start an ejabberd node in live (interactive) mode Start Start an ejabberd node in server modeĭebug Attach an interactive Erlang shell to a running ejabberd node # ejabberdctl register admin localhost passwordįailed RPC connection to the node nodedown

CONNECT EJABBERD INSTALL

After a clean install of ejabberd in Fedora 21, I cannot use the ejabberdctl utility to register users, etc.

Connect ejabberd