I need your inputs on Ejabberd 20.01, the upgrade seems good, when the rpm 18.06 will be stopped before the upgrade to 20.01 you can read some obsolete directive in
ejabberd.log but once the new template is expanded, the 20.01 version is running
I can reach some salons
I can use the web_admin (remember to use firstname.lastname@example.org login)
no warns in logs
I test a new directive to do not cache authentication, I hope that it could fix the password cache @Neustradamus
yum install http://packages.nethserver.org/nethserver/7.7.1908/autobuild/x86_64/Packages/nethserver-ejabberd-1.5.2-1.7.pr30.g321370f.ns7.noarch.rpm --enablerepo=nethserver-testing
Well now guys it is up to you
Have you added my PRs/remarks or not yet?
Could you point me the url
time to test now…the upgrade is good, we added a cache false for authentication and mod_http_upload, test the UI to enable it
yum install http://packages.nethserver.org/nethserver/7.7.1908/autobuild/x86_64/Packages/nethserver-ejabberd-1.5.2-1.15.pr30.ga1953b1.ns7.noarch.rpm --enablerepo=nethserver-testing
thank in advance
@stephdl what are the use cases of the software ejabberd.
am trying to understand.
Communication. More info can be found on: https://en.wikipedia.org/wiki/Ejabberd
Installation went well with:
yum install http://packages.nethserver.org/nethserver/7.7.1908/testing/x86_64/Packages/nethserver-ejabberd-1.5.2-1.16.g2692f3c.ns7.noarch.rpm --enablerepo=nethserver-testing
After ejabberd 18.x was installed via - Software center -
I was able to send a picture with Conversations on Android:
but not with OMEMO encryption:
I am not sure we have implemented OMEMO (encryption)
OK, maybe the client. I will continue in the next days…
Thank you for your work !
OMEMO works on another of my Server… Thanks for your Work!
can this solution be used as a STURN, TUN and signalling server for nextcloud talk.
if i have this installed, do i need cortun