1/8/2024 0 Comments Ejabberd data access layer![]() ![]() ![]() okie mismatches - that's the current rabbit I'm chasing down the hole. 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 ** environmentejabberdhttps true ejabberdstarttls true ejabberds2sssl true ejabberdprotocoloptionstlsv1 false ejabberdloglevel 4 ejabberdmuccreateadminonly ejabberdregisteradminonly ejabberdmodadminextra true ejabberdmodmucadmin false ejabberdregistertrustednetworkonly ejabberdskipmodulesupdate false ejabberdauthmethod internal ejabberdadmins ejabberdusers erlang. My steps on a clean installation of Fedora 21: In my case, it's doing *anything* with ejabberdctl - not just registering. ejabberdctl register admin localhost password paperless end-of-line h.264 data-access searchable exponentiation vcl screen-resolution ejabberd-saas mobile-devices distributed-system mac-app-store tcp-ip. 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 After a clean install of ejabberd in Fedora 21, I cannot use the ejabberdctl utility to register users, etc. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |