Mercurial > prosody-modules
view mod_isolate_host/README.md @ 6352:525655adfd3e
mod_report_affiliations: Fix traceback a non-user is sending a presence
For now we won’t touch their presence instead of emiting this traceback:
error Traceback[s2s]: /usr/lib/prosody/core/rostermanager.lua:275: attempt to concatenate a nil value (local 'username')
stack traceback:
/usr/lib/prosody/core/rostermanager.lua:275: in function 'prosody.core.rostermanager.is_user_subscribed'
...ules/mod_report_affiliations/mod_report_affiliations.lua:116: in field '?'
/usr/lib/prosody/util/events.lua:81: in function </usr/lib/prosody/util/events.lua:77>
(...tail calls...)
/usr/lib/prosody/core/stanza_router.lua:184: in upvalue 'core_post_stanza'
/usr/lib/prosody/modules/mod_presence.lua:244: in function </usr/lib/prosody/modules/mod_presence.lua:231>
(...tail calls...)
/usr/lib/prosody/util/events.lua:81: in function </usr/lib/prosody/util/events.lua:77>
(...tail calls...)
/usr/lib/prosody/core/stanza_router.lua:188: in upvalue 'core_post_stanza'
/usr/lib/prosody/core/stanza_router.lua:128: in upvalue 'core_process_stanza'
/usr/lib/prosody/modules/mod_s2s.lua:818: in upvalue 'func'
/usr/lib/prosody/util/async.lua:149: in function </usr/lib/prosody/util/async.lua:147>
| author | Link Mauve <linkmauve@linkmauve.fr> |
|---|---|
| date | Tue, 30 Dec 2025 13:19:43 +0100 |
| parents | fe081789f7b5 |
| children |
line wrap: on
line source
--- labels: - 'Stage-Beta' summary: Prevent communication between hosts ... Introduction ============ In some environments it is desirable to isolate one or more hosts, and prevent communication with external, or even other internal domains. Loading mod\_isolate\_host on a host will prevent all communication with JIDs outside of the current domain, though it is possible to configure exceptions. **Note:** if you just want to prevent communication with external domains, this is possible without a plugin. See [Prosody: Disabling s2s](http://prosody.im/doc/s2s#disabling) for more information. This module was sponsored by [Exa Networks](http://exa-networks.co.uk/). Configuration ============= To isolate all hosts by default, add the module to your global modules\_enabled: ``` {.lua} modules_enabled = { ... "isolate_host"; ... } ``` Alternatively you can isolate a single host by putting a modules\_enabled line under the VirtualHost directive: ``` {.lua} VirtualHost "example.com" modules_enabled = { "isolate_host" } ``` After enabling the module, you can add further options to add exceptions for the isolation: Option Description -------------------------- ----------------------------------------------------------------------------------------- isolate\_except\_domains A list of domains to allow communication with. isolate\_except\_users A list of user JIDs allowed to bypass the isolation and communicate with other domains. **Note:** Admins of hosts are always allowed to communicate with other domains Compatibility ============= ----- ------- 0.9 Works ----- -------
