![]() ![]() With the loglevel set to 4 all I got in the /var/log/ejabberd/ejabberd.log is: 11:46:08.796 Application lager started on node 11:46:08.801 Application crypto started on node 11:46:08.808 Application sasl started on node 11:46:08.813 Application asn1 started on node 11:46:08.813 Application public_key started on node 11:46:08.818 Application ssl started on node 11:46:08.822 Application p1_yaml started on node 11:46:08.831 Application p1_tls started on node 11:46:08.837 Application p1_xml started on node 11:46:08.842 Application p1_stringprep started on node 11:46:08.846 Application p1_zlib started on node 11:46:08.850 Application p1_cache_tab started on node 11:46:10.447 Application mnesia started on node 11:46:11.226 Application inets started on node 11:46:11.698 Application p1_mysql started on node 11:46:11.745 Application p1_iconv started on node 11:46:11. 'TLS_CIPHERS': "ECDH:DH:!CAMELLIA128:!3DES:!MD5:!RC4:!aNULL:!NULL:!EXPORT:!LOW:!MEDIUM"Ĭertfile: "/etc/ejabberd/cert/"Īllow_private_messages_from_visitors: anyoneĪccess_max_user_messages: max_user_offline_messages Here is my /etc/ejabberd/ejabberd.yml: hosts:Ĭaptcha_cmd: "/usr/lib/x86_64-linux-gnu/ejabberd/priv/bin/captcha.sh" 'myhost') in the installer, and then try to log into the admin console using 'localhost', it will fail, since whatever password you entered is for 'admin' at 'myserver', not 'localhost'. User activity is not logged even when loglevel is set to 5 (debug). to make sslh forward http requests to nginx, and non-http requests to ejabberd. logged messages can be viewed through ejabberd web admin interface. Maybe you set custom ACLs in the configuration file, or using the web browser, or in older ejabberd2, and now the web admin is unable to show them correctly. ![]() Since upgrade from ejabberd from the Stable the logging to /var/log/ejabberd/ejabberd.log seems broken. This will tell the Nginx to listen to port 443, and then pass the TCP. modlogdb - module for ejabberd for logging user messages to db ( mnesia, mysql. As such, when using ejabberd installer, you do not need to install Erlang separately. It includes a stripped down version of Erlang. run binary installer will deploy and configure a full featured ejabberd server and does not require any extra dependencies. I have ejabberd 15.09 from the Testing repository running on the Debian 8.2 "Jessie" ( Stable) server. Administration Account Configuring ejabberd Linux RUN Installer The. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |