Zen

Chaîne source Chaîne source

211/10000 · 211

La chaîne est en lecture seule.

Anglais Actions
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)
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)
record name: _xmpp-server._tcp.external.your_instance.tld. (replace «your_instance.tld» by your instance uri)
Be careful to keep the dot after "your_instance.tld".
Using the `dig` command to check your records, you should get a result similar to this:
$ dig +short _xmpp-server._tcp.room.videos.john-livingston.fr. SRV
0 5 5269 videos.john-livingston.fr.

$ dig +short _xmpp-server._tcp.external.videos.john-livingston.fr. SRV
0 5 5269 videos.john-livingston.fr.
If you are **not using the standard `5269` port**, you must also add a SRV record for `_xmpp-server._tcp.your_instance.tld.` (same as above, just without the `room.` prefix). Of course, you can also add this record if you use the standard port. It will also work.
Using trusted certificates
The self-signed certificates that this plugin uses by default can be rejected by some XMPP servers, for security reasons.
It is possible to use certificates validated by a certification authority. However, this requires advanced system administration knowledge. Indeed, due to the multitude of possible use cases, it is impossible to document all situations here. This documentation will therefore only explain the goal to be reached, and give an example which will only be suitable for a "basic" situation (manual installation of Peertube, using letsencrypt). If you are in another situation (Docker installation, certificates signed by another authority, etc...), you will have to adapt this approach by yourself.
Basic principle
It is up to you to generate valid certificates for domains `your_instance.tld` and `room.your_instance.tld`. You can use any [method supported by Prosody](https://prosody.im/doc/certificates).
You must then place these certificates in a folder that will be accessible to the `peertube` user, and specify this folder in the plugin setting "Certificate folder".
If you want to use the ProsodyCtl utility to import certificates, this utility is available (once Peertube is started) using the following command (adapting the path to your Peertube data folder, and replacing "xxx" with the arguments you wish to pass to prosodyctl): `sudo -u peertube /var/www/peertube/storage/plugins/data/peertube-plugin-livechat/prosodyAppImage/squashfs-root/AppRun prosodyctl xxx`
The plugin will check once a day to see if any files have been modified in this folder, and reload Prosody if necessary.
Method for the simple case
We assume here that your Peertube installation is "classic" (no use of Docker), and that the certificates are generated by letsencrypt, using the certbot tool.
First of all, we'll have to create a certificate for the subdomain `room.your_instance.tld` : this is the uri of the MUC (XMPP chat rooms) component. Even if the connections are made on `your_instance.tld`, we will need a valid certificate for this subdomain.
So start by setting up a DNS entry for `room.your_instance.tld`, which points to your server. You can use a CNAME entry (or an A entry and a AAAA entry).
Next, we'll use nginx (already installed for your Peertube) to generate the certbot certificate. We will create a new site. In the file `/etc/nginx/site-available/room.peertube`, add:
server {
listen 80;
listen [::]:80;
server_name room.your_instance.tld;

location /.well-known/acme-challenge/ {
default_type "text/plain";
root /var/www/certbot;
}
location / { return 301 https://your_instance.tld; }
}

Chargement…

Avatar de l’utilisateur Aucun

Chaîne ajoutée au dépôt

  1. PeerTube LiveChat
  2. Peertube Plugin Livechat Documentation
  3. Anglais
$ dig +short _xmpp-server._tcp.room.videos.john-livingston.fr. SRV
0 5 5269 videos.john-livingston.fr.

$ dig +short _xmpp-server._tcp.external.videos.john-livingston.fr. SRV
0 5 5269 videos.john-livingston.fr.
$ dig +short _xmpp-server._tcp.room.videos.john-livingston.fr. SRV
0 5 5269 videos.john-livingston.fr.

$ dig +short _xmpp-server._tcp.external.videos.john-livingston.fr. SRV
0 5 5269 videos.john-livingston.fr.
Il y a un mois
Parcourir toutes les modifications de chaînes

Points à vérifier

Plusieurs vérifications en échec

Les contrôles suivants sont défaillants :
Traduction inchangée: Français, Allemand

Réinitialiser

Glossaire

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

Informations sur la chaîne

Description de la chaîne source
type: Fenced code block (bash)
Drapeaux
no-wrap, read-only
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 mois
Date de dernière mise à jour
Il y a 5 jours
Âge de la chaîne source
Il y a un mois
Fichier de traduction
support/documentation/po/livechat.en.pot, chaîne 233