This chat module is based on the XMPP protocol, also known as Jabber.It is therefore possible to connect to the chats using [XMPP client software](https://en.wikipedia.org/wiki/XMPP#Clients).This can for example be useful to facilitate moderation operations.
For the user documentation associated with these features, please refer to the [user documentation page](/peertube-plugin-livechat/documentation/user/xmpp_clients/).
Enabling these features requires configuration changes on the server, and on the DNS records.It is not possible to configure this only from the Peertube interface, and it requires some basic system some basic system admin skills.
To enable this feature, you will need to set up your server and DNS records, so that XMPP clients can find and access the [Prosody server](https://prosody.im) that this plugin uses internally.
Start by going to the livechat plugin settings of your instance, then enable the setting "Enable connection to room using external XMPP accounts".By checking this setting, new settings appear below.
First of all, the "Prosody server to server port" field.This one defaults to 5269, which is the standard port for this service.You can however change to another port, if this is already in use on your server.
Next, the field "Server to server network interfaces" field allows you to specify which network interfaces the server should listen on.The default value "*, ::" indicates to listen on all IP addresses.You can change these values, if you wish to listen on only certain IP addresses.The syntax is explained next to the setting.
For the "Certificate folder" setting, you can leave it empty.In this case, the plugin will automatically generate self-signed certificates.Some XMPP servers may refuse to connect, depending on their configuration.In this case, you can indicate here a path on the server, in which you must place certificates to be used by the module.It is up to you to generate and renew them.See bellow for more information.
If you are using Docker for your Peertube, you need to modify the `docker-compose.yml` file to open port 5269 of the `peertube` container, so that the outer world can connect to it.
You need to add [DNS records](https://prosody.im/doc/dns) allowing remote servers to find "room.your_instance.tld" and "external.your_instance.tld" components.
