Paweł Chmielowski
Paweł Chmielowski
I think you may be using wrong url, as i think this error is sent if we can't determine what command should be executed from url/payload.
Hello, How did you install this extra module? It indeed require couple extra modules that aren't distributed with ejabberd.
I added https://github.com/processone/p1_acme/commit/cd292d02ca12ff9cdcad17732c4b02c289288958 in p1_acme library that i think will help with that error.
Do 'aaa' and 'bbb' resolve on both nodes correctly? And is network setup in such way that they both can access themselves?
Yes, that probably why this failed. My guess would be ports used for communications aren't accessible between nodes. Or could be issue with cookie used for authentication (to check that...
Can you see what `mnesia:info().` returns?
Could you try joining node from debug shell instead of ejabberdctl, just execute `ejabberd_admin:join_cluster().` (just update node name as needed). This should allow this operation to not have timeout that...
I added 72bc9b6c7f6afce7aa671a47eee343cc25b0abcb that should allow such certificate be accepted by ejabberd.
Can you see if executing `/Users/void/.asdf/installs/elixir/1.17.0/.mix/elixir/1-17/rebar3 plugin upgrade` allows you to compile after that successfully?
Ah, sorry it should be `/Users/void/.asdf/installs/elixir/1.17.0/.mix/elixir/1-17/rebar3 plugins upgrade --all` You may also try upgrading rebar with `mix local.rebar`. I am able to compile this module using r27/elixitr1.17.0.