Ejabberd 18.06 bug or issue

hello @stephdl ,
vllt it is still useful that one could set the max transmission size and speed.

Do you still need certain values ​​for encryption or xpe for file transfer and audio transfer?

well it is really beta stage now, I’m studying ejabberd right now :frowning:

But but ejabberd 18.04 works on my server …youpy

1 Like

I did not find information in the documentation on your proposals, could you please point me the correct way to the documentation chapters

I have the following information:


Shaper Rules
An entry allowing to declaring shaper to use for matching user/hosts. The syntax is:

shaper_rules: { ShaperRuleName: { - Number|ShaperName: ACLRule|ACLDefinition } }

Semantic is similar to that described in Access Rights section, only difference is that instead using - allow or - deny, name of shaper or number should be used.


- 10:
- user: "peter@example.com"
- 100: admin
- 5
- fast: admin
- slow: anonymous_users
- normal
log_days: 30

Shapers enable you to limit connection traffic. The syntax is:

shaper: { ShaperName: Rate }: where Rate stands for the maximum allowed incoming rate in bytes per second. When a connection exceeds this limit, ejabberd stops reading from the socket until the average rate is again below the allowed maximum.


To define a shaper named ‘normal’ with traffic speed limited to 1,000bytes/second:

normal: 1000
To define a shaper named ‘fast’ with traffic speed limited to 50,000bytes/second:

fast: 50000

Meintest du: Ich habe folgende Infos: Diese Konfiguration ist auch in der jetzigen Konfiguration schon enthalten.

This configuration is already included in the current configuration.


Is related to Speed up Jabber file transfer feature request made by @sharpec

yep I added some props to adjust them if needed, for the GUI we could think of it


But hello!

looks good :wink:

What are you saying with “Groupsname are displayed”?

Do you need settings for file transfer, voice messages and pictures?

I’m looking forward to it when not all users (including the system users and devices are displayed in the contact list)

Can not Hardly Wait :wink:

best regards

feature from @giacomo, in fact users are sorted by group name (from ldap)

do you point to documentation ?




the two modules you pointed are not enabled by default (yet), probably not for the older installation. Facing to the number of modules (that could break other installation), probably you should use a custom template to enable the modules you want and ask after to put it as default once stabilized.

1 Like

Hello @stephdl!

I hope I do not stress you so much :wink:

Can you support you?
Alpha or beta test?

A bottle of delicious wine?

best regards


what client do you use please :slight_smile:
thank for your support, I will soon have an alpha, but please, please do not test on real server.

For example I am not sure if persistent room will survive, something to test for example

1 Like

On the smartphone, conversation
and on the computers I PidGin and my wife Gajim

1 Like

yum install nethserver-ejabberd --enablerepo=nethserver-testing

you should have ejabberd workable, please do not test directly on your server.

If all is workable for you, then I would be pleased that you test the upgrade from 16.01 with some persistent rooms and users.

1 Like

Tested on a vm on on a production machine (AD only) for now.
No problems so far.

Come on @gerald_FS @greavette it’s now time to give help to our mighty Stéphane!

1 Like