Hello,
I have changed my servers hostname and then again... and now it is back to what it started with.
I have found since then, Jabber will not bind to LDAP services see video?:
I took a screen shot of the servers /var/log/ejabberd/ejabberd.log flie at very moment that I tried to login with pidgin (see attached)
The video which just goes on and on shows reattempts are rejected:
https://www.youtube.com/watch?v=Q04hiVcKY2gCredentials are correct. They have been triple verified.
Finally, after exhausting all other avenues I unchecked Domain / File Sharing from the Zentyal Modules and completed purged and reintsalled all Jabber modules with:
apt-get remove --purge zentyal-jabber
apt-get remove --purge ejabberd
apt-get autoremove --purge
Turned off Module Domain Controller and File Sharing
Saved everything
Rebooted the server
When I logged in with Pidgin and did ask me to approve the Secure Certificate which I said yes to. However the moment I select 'Accept' it Pidgin returns error : "Lost connection with the server: Input/output error" with option to reconnect (but it will not connect)
Jabber was working with LDAP prior to the hostname changes. Now it will not work at all.
I do not know for sure if the LDAP errors are related to my Jabber problem of not connecting but I am suspecting it is.
Also, I have found the file:
https://github.com/processone/ejabberd/blob/master/src/eldap.erl which contains the code that spawns the error ie; report_bind_failure(S#eldap.host, S#eldap.port, Reason),
If anyone out there has run into this, I would be grateful for the solution. Otherwise I will have to try radical maneuvers all the way up to a format reinstall.
FOLLOW UP: Am experiencing the very same problem showing up in the nextcloud.log file of bind failure and 49.
So it's not a jabber thing, it's an ldap thing.
What sayeth the group.
Sincerely,
Jay
CompuMatter
www.compumatter.com