MUC service not announced in disco items/info #413
Labels
No Label
service
accounts
service
discourse
service
drone-ci
service
email
service
garage
service
gitea
service
ipfs
service
mastodon
service
postgres
service
remotestorage
service
wiki
service
xmpp
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
release
major
release
minor
release
patch
security
ui/ux
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Depends on
#334 Upgrade ejabberd to 22.05
kosmos/chef
Reference: kosmos/chef#413
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I found out that the reason that the XMPP compliance test suite is currently reporting we don't support MUC, despite our daily use of it, is that the MUC items are missing from the service discovery info.
This also means that if you don't already have that service info cached, people cannot e.g. create private chat rooms, because there is no MUC domain/service that the client can find with normal discovery (as reported by @maxsan).
I think the reason is that the MUC config is included in a separate modules block via
include_config_file
andappend_host_config
and there seems to be a subtle bug in how ejabberd then assembles the service info from the config.Edit:
We should first upgrade to 22.05 to see if that was already fixed, and if not, then report the bug upstream.Still happening with the latest release version.Reported here: https://github.com/processone/ejabberd/issues/3836