I have for mission to upgrade ejabberd to 18.04, firstable I would like to summarize all issues I can find in 16.01
lack of documentation to access the admin page
correct url is https://IPorDomain:5280/admin
the user must be part of the jabberadmins group
the web admin page must be activated
admin page is incomplete seethis post
you must use user@domainName to login, but in the /etc/ejabberd/ejabberd.cfg you must use only the user part {acl, admin, {user_regexp, "^(stephane|admin@nethservertest.org)$"}}.
in the example above, only stephane could use the full administrator web page, the admin user will have a truncated and not functional web page.
we should modify /etc/e-smith/templates/etc/ejabberd/ejabberd.cfg/00template_vars with
Thank you @stephdl for raising these issues. Iâve never been able to access my ejabberd admin page. Iâve enabled the signal-event instruction and when I access the https site it asks for a login but then immediately I get the error âThis page isnât workingâ. Iâve confirmed that Iâve created a jabberadmins group and my user is a member of that group.
Iâve also noticed that the ejabberd.cfg file is inconsistent with what it requires (user or user@domain).
Despite these issues, Iâm happily using my Nethserver ejabberd server for my Nextcloud module for my employees to connect with each other using Nextcloud.
But it would be nice to see whatâs on that Admin page for administration purposes.
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.
Shapers
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.
Examples:
To define a shaper named ânormalâ with traffic speed limited to 1,000bytes/second:
shaper:
normal: 1000
To define a shaper named âfastâ with traffic speed limited to 50,000bytes/second:
shaper:
fast: 50000
100/5000
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.
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.