Zen

Traduction

Anglais type: Plain text
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.
0/4180 · 418

Connectez-vous pour enregistrer vos traductions.

Anglais Persan Actions
Now you can add this account to gateways and bridge specific live-chat channels.
 
This documentation use an anonymous account to connect the bridge to the chat. But since the livechat v10.1.0, there is a new way to generate long term authentication token, that allows to connect using your account. This is used for [OBS docks](/peertube-plugin-livechat/documentation/user/obs). Using this feature for other purposes is not documented and not officially supported yet. If you want to use it anyway, you can request a token by calling then `/plugins/livechat/router/api/auth/tokens` endpoint. To get needed headers and request body, just check what happens when you generate a new token for OBS docks.
 
Allow connections using XMPP clients
 
XMPP clients
 
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.
 
Login to your Peertube account
 
This feature is not yet available, and will come in a future version of the plugin.
 
Connection using an external XMPP account
 
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.
 
Plugin settings
 
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.
 
Firewall
 
You must open the configured port (5269 by default) on your firewall.
 
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.
 
DNS
 
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.
 
The easiest way to do this is to add SRV records for the "room" and "external" [subdomain](https://prosody.im/doc/dns#subdomains):
 
record name: _xmpp-server._tcp.room.your_instance.tld. (replace «your_instance.tld» by your instance uri)
 
TTL: 3600
 
class: IN
 
SRV: 0
 
priority: 0
 
weight: 5
 
port: 5269 (adapt if your changed the default port)
 
target: your_instance.tld. (replace by your instance uri)
 
record name: _xmpp-server._tcp.external.your_instance.tld. (replace «your_instance.tld» by your instance uri)
 

Chargement…

Avatar de l’utilisateur Aucun

Chaîne mise à jour dans le dépôt
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.
 
Il y a un an
Parcourir toutes les modifications de chaînes

Glossaire

Anglais Persan
Aucune chaîne correspondante n’a été trouvée dans le glossaire.

Informations sur la chaîne

Description de la chaîne source
type: Plain text
Emplacement de la chaîne source
support/documentation/content/en/documentation/admin/advanced/xmpp_clients.md
Âge de la chaîne
Il y a un an
Date de dernière mise à jour
Il y a un mois
Âge de la chaîne source
Il y a un an
Fichier de traduction
support/documentation/po/livechat.fa.po, chaîne 218