jitsi-meet prosody modules not available
See original GitHub issueAre the jitsi-meet prosody modules available in the container?
I tried loading the mod_muc_size without any success. I’ve added mod_muc_size
as a XMPP_MODULES and as a XMPP_MUC_MODULES in the .env file, but when I access the prosody container it’s nowhere to be found.
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (8 by maintainers)
Top Results From Across the Web
New prosody module not working - Jitsi Community Forum
I have created a new prosody module file named mod_muc_ashq.lua in this directory /usr/share/jitsi-meet/prosody-plugins.
Read more >Issue mod_admin_web prosody module - Google Groups
We do a clean install van jitsi meet with prosody. After that we enable the admin_web module. We create an admin user for...
Read more >How To Implement Your Own Prosody Plugin for Jitsi
Prosody has a plugins directory which contains all the optional modules that it uses. Plugins are only usable if they are enabled. There...
Read more >How to add log in Jitsi prosody plugin lua files - Stack Overflow
also, are these Lua files run from the Prosody server? is there any connection in Jicofo for added prosody modules in jitsi meet?...
Read more >Enable authentication - Jitsi self hosting - GitLab
The proposed Jitsi implementation requires authentication for the host, but not for ... Since Prosody server is accessible independently from Jisti-meet, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah this is common problem. The easiest way to disable this behavior is to remove the /config volume in the docker-compose.yml.
@saghul I’m using port 5280 for my prosody plugin and it’s working fine. Bosh also just uses an endpoint called
/http-bind
. The port is just the default http port of prosody.@RCoanda If you want to be able to access the endpoint via the browser you have to add it to the nginx proxy config in the web container.