# This section provides configuration examples in case # so you do not necessarily need this section. # ejabberd by default uses the internal Mnesia database, # To use both anonymous and internal authentication: # allow_multiple_connections: true | false # anonymous_protocol: sasl_anon | login_anon | both # ldap_filter: "(objectClass=shadowAccount)" # Encryption of connection to LDAP servers: # Remember to setup a database in the next section. # extauth_program: "/path/to/authentication/script" # Make sure the script is executable by ejabberd. # Define the FQDN if ejabberd doesn't detect it: # Store the plain passwords ("plain") or hashed for SCRAM ("scram"): # auth_method: Method used to authenticate the users. # Set the ciphers which can be used for s2s connections. # s2s_certfile: Specify a certificate file. # Allowed values are: false optional required required_trusted # s2s_use_starttls: Enable STARTTLS + Dialback for S2S connections. # domain_certfile: Specify a different certificate for each served hostname. # TODO: Bind to localhost, then put this behind a TLS reverse proxy (read, "Nginx") # To handle XML-RPC requests that provide admin credentials: # ejabberd_stun: Handles STUN Binding requests # All my clients support TLSv1.2, so just turn everything else off. # use this instead of the "starttls" option: # To enforce TLS encryption for client connections, # certificate, specify the full path to the # If TLS is compiled in and you installed a SSL # Don't use stream compression and tls compression # listen: The ports ejabberd will listen on, which service each is handled # to allow communication with an XMPP server called im. # For example, if this ejabberd serves and you want # route_subdomains: Delegate subdomains to other XMPP servers. # You can define one or several, for example: # consumes a lot of memory, send live notifications to these XMPP # watchdog_admins: Only useful for developers: if an ejabberd process # of messages when system is overloaded, you can set a limit. # allowed from error_logger, which is a good idea if you want to avoid a flood # overload protection: If you want to limit the number of messages per second # $M5D6 rotate on every 5th day of the month at 6:00 hr # $M1D0 rotate on the first day of every month at midnight # $W5D16 rotate every week on Friday at 16:00 hr # $W0D23 rotate every week on Sunday at 23:00 hr # Date syntax is taken from the syntax newsyslog uses in nf. # To disable rotation set the size to 0 and the date to "" Setting size to X rotate log when it reaches X bytes. # does not disable rotation, it instead rotates the file and keeps no previous # 0: No ejabberd log at all (not recommended) whether the PID file is even important.# loglevel: Verbosity of log files generated by ejabberd. I'm also unsure how ejabberdctl is trying to communicate with ejabberd. Is this just the missing PID file that's the problem? I can't find a reference to a PID config in the ejabberd.cfg file, so I'm not sure if it's really expected to write something in that location or not. node nodename ejabberd node name: ejabberd at localhost spool dir Database spool dir: /var/spool/ejabberd logs dir Directory for logs: /var/log/ejabberd ctl-config file Config ejabberdctl: /usr/local/etc/ejabberd/ejabberdctl.cfg config file Config ejabberd: /usr/local/etc/ejabberd/ejabberd.cfg config-dir dir Config ejabberd: /usr/local/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 > sudo ejabberdctl register matt įailed RPC connection to the node ejabberd at localhost: nodedown However, the control client isn't able to talk to ejabberd. ĭespite this the daemon seems to have started fine. The only oddity I found is that ejabberdctl.cfg refers to /var/run/ejabberd/ejabberd.pid for the ejabberd PID file, but that directory wasn't created. I did a quick scan through them to look for any obvious changes that needed to be made for local configuration and started up the daemon. Just to get it running, I've put the sample configs in place as running configs. Next message: Ranking Number 1 on Google is the goal of every website owner.Previous message: FreeBSD Port: textproc/libvisio.Ejabberd port: default config not workingĮjabberd port: default config not working Matthew Pounsett matt at
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |