We are pleased to announce ejabberd 20.07.
In addition to the usual fixes, this version adds support for Unix domain socket (aka IPC socket) which can be used to replace IP socket for any listener. As it’s more efficient than a network socket, this is the recommended endpoint to use if you have a proxy in front of ejabberd that is running locally on the same node.
It also allows to get rid of the 64k ports limit. You just have to set the option port: "unix:/path/to/file" of your listener to use a Unix domain socket instead of an IP one.
See Changelog below for a list of the other changes in this release.
Features, improvements and fixes in ejabberd 20.07
- Add support for using Unix domain sockets in listeners.
- Make this version compatible with erlang R23
- Make room permissions checks more strict for subscribers
- Fix problem with muc rooms crashing when using muc logger
with some locales - Limit stat calls that logger module issues
- Don’t throw errors when using user_regexp acl rule and
having non-matching host - Fix problem with leaving old data when updating shared rosters
- Fix edge case that caused failure of resuming old sessions with
stream management. - Fix crash when room that was started with loging enabled was later
changed to logging disabled - Increase default shaper limits (this should help with delays for
clients that are using jingle) - Fix couple compatibility problems which prevented working on
erlang R19 - Fix sending presence unavailable when session terminates for
clients that only send directed presences (helps with sometimes
not leaving muc rooms on disconnect). - Prevent supervisor errors for sockets that were closed before
they were passed to handler modules - Make stun module work better with ipv6 addresses
ejabberd 20.07 download & feedback
As usual, the release is tagged in the Git source code repository on Github.
The source package and binary installers are available at ejabberd XMPP & MQTT server download page.
We’ve discovered some issues with the Windows installer that we are still working on, so its publication is delayed.
If you suspect that you’ve found a bug, please search or fill a bug report on Github.
