MUC service not announced in disco items/info #413
Closed
opened 2022-05-31 09:27:22 +00:00 by raucao
·
1 comment
No Branch/Tag Specified
Labels
Clear labels
monitoring
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
security
ui/ux
wontfix
service
discourse
Kosmos Community Forums
Infrastructure metrics, alerts, notifications, etc.
service
accounts
Kosmos Accounts
service
drone-ci
Kosmos Drone CI
service
email
mail.kosmos.org
service
garage
S3-compatible object storage
service
gitea
Kosmos Gitea
service
ipfs
Kosmos IPFS
service
lightning
Lightning address, lndhub, etc.
service
mastodon
kosmos.social
service
nostr
Relays, Blossom server, etc.
service
postgres
Database cluster
service
remotestorage
Portable data storage for the Web
service
wiki
Kosmos Wiki
service
xmpp
Kosmos Chat
Something is not working
Graphic/visual design
Config, builds, CI, deployment, etc.
Documentation
This issue or pull request already exists
Improving existing functionality
New functionality
Dive in, and start contributing
Something to consider
Not a bug
Small contribution
Medium contribution
Large contribution
Currently not actionable
Manual IT ops activities
Looking for an answer
release
major
release
minor
release
patch
All your base are belong to us
User interface, process design, etc.
This won't be fixed
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Current operational issues
Solved
No Assignees
Notifications
Due Date
No due date set.
Depends on
#334 Upgrade ejabberd to 22.05
kosmos/chef
Reference: kosmos/chef#413
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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_fileandappend_host_configand 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