Problème à l'installation de Peertube

Bonjour,
je ne suis pas sur que je suis au bon endroit pour demandé de l’aide à l’installation. Donc si il y a plus approprié, n’hésitez pas à me rediriger.

J’ai suivi la documentation fournir avec Peertube pour l’installation. Dans l’ensemble, c’est clair. Cependant, je rencontre un problème avec Yarn.
Lors de cette étape :
$ cd ./peertube-latest && sudo -H -u peertube yarn install --production --pure-lockfile
J’ai ce message d’erreur :
yarn: error: no such option: --production

J’ai suivi la doc à la lettre. Un admin Peertube ma conseillé de configurer le fichier production.yaml à partir de l’exemple, ce que j’ai fais en en faisant une copie dans le dossier config de peertube-latest.
Mais je but sur la même erreur.

Ai-je loupé un truc ?

Merci d’avance pour votre aide.
Longue vie au libre!

Tu as mal installé les dépendances (en l’occurrence yarn) https://github.com/Chocobozzz/PeerTube/blob/develop/support/doc/dependencies.md#debian--ubuntu-and-derivatives

Ok, je pensais l’avoir suivi à la lettre. Je vais le refaire.
je suppose que pour Yarn, j’installe les nightly : https://yarnpkg.com/en/docs/nightly
Est-ce qu’il y a un point spécifique auquel faut être attentif ?

Merci du support !
Félicitation pour cette excellent travail ! :slight_smile:

Non il faut installer du stable (surtout si c’est de la prod).

Ok, donc : https://yarnpkg.com/en/docs/install#linux-tab
Yarn est déjà dans les dépôt stable. Cette version suffit-elle ou je dois quand même configurer le dépôt ?

Merci

C’est pas le même yarn dans les dépots debian

Heu … ok.
Faut le savoir o.O
Je regarde cela ce soir. Sachant que j’ai commencé par installé Yarn depuis le dépôt debian, puis désinstaller pour passer au nightly, j’ai surement du ménage à faire.
Merci !

Hello!

J’ai eu le même problème, j’ai trouvé la solution en installant yarn globalement via npm, et non pas via les dépôts de Debian:

sudo npm install -g yarn

Je ne sais pas si la solution est bonne en tout cas ça a marché pour moi!

PS: oups j’ai posté avant de faire ma présentation, ça ne saurait tarder :stuck_out_tongue:

1 « J'aime »

Merci ! Je n’ai plus l’erreur, donc l’installe se lance … :slight_smile:

[2/4] Fetching packages...
info fsevents@1.1.3: The platform "linux" is incompatible with this module.
info "fsevents@1.1.3" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning " > @angular/compiler-cli@5.2.6" has incorrect peer dependency "typescript@>=2.4.2 <2.7".
warning " > @ngx-meta/core@5.0.0" has unmet peer dependency "lodash@>=4.17.4".
[4/4] Building fresh packages...
$ npm rebuild node-sass
Done in 39.49s.
Done in 168.00s.

On croise les doigts!

Bon, et bien problème de certificat.

$ sudo certbot --authenticator standalone --installer nginx --post-hook "systemctl start nginx"
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer nginx

Which names would you like to activate HTTPS for?
-------------------------------------------------------------------------------
1: video.franckboucher.com
-------------------------------------------------------------------------------
Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel): 1
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for video.franckboucher.com
Waiting for verification...
Cleaning up challenges
Running post-hook command: systemctl start nginx
Failed authorization procedure. video.franckboucher.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for video.franckboucher.com

IMPORTANT NOTES:
 - The following errors were reported by the server:

   Domain: video.franckboucher.com
   Type:   connection
   Detail: DNS problem: NXDOMAIN looking up A for
   video.franckboucher.com

   To fix these errors, please make sure that your domain name was
   entered correctly and the DNS A/AAAA record(s) for that domain
   contain(s) the right IP address. Additionally, please check that
   your computer has a publicly routable IP address and that no
   firewalls are preventing the server from communicating with the
   client. If you're using the webroot plugin, you should also verify
   that you are serving files from the webroot path you provided.

A mon niveau, c’est du chinois ^^
Merci de votre aide.

Bon, si je comprends bien, c’est un problème d’alias …

Désolé pour le monologue ^^

Problème Résolu mais problème nginx derrière …

Peut-être que je peux essayer de t’aider, sans te garantir 100% d’efficacité! :slight_smile:

Déjà as-tu résolu ton problème de certificat? Si oui, comment?

Salut, ça sera avec plaisir.
Pour le moment, Nginx refuse de se lancer, il semblerait qu’il ne trouve pas le certif. J’ai du faire une faute de frappe quelques part, mais pour le moment je ne trouve pas.
Enfin, c’est ce que je comprends des logs. Si tu vois autre chose, je suis preneur.
Merci pour le coup de main.

$ sudo journalctl -u nginx
-- Logs begin at Sun 2018-03-25 17:41:22 CEST, end at Wed 2018-03-28 21:29:52 CEST. --
Mar 25 18:09:17 vps528815 systemd[1]: Starting A high performance web server and a reverse proxy server...
Mar 25 18:09:17 vps528815 systemd[1]: nginx.service: Failed to read PID from file /run/nginx.pid: Invalid argument
Mar 25 18:09:17 vps528815 systemd[1]: Started A high performance web server and a reverse proxy server.
Mar 25 18:31:13 vps528815 systemd[1]: Stopping A high performance web server and a reverse proxy server...
Mar 25 18:31:13 vps528815 systemd[1]: Stopped A high performance web server and a reverse proxy server.
Mar 25 18:31:13 vps528815 systemd[1]: Starting A high performance web server and a reverse proxy server...
Mar 25 18:31:13 vps528815 nginx[23866]: nginx: [emerg] a duplicate default server for 0.0.0.0:80 in /etc/nginx/sites-enabled/fb:22
Mar 25 18:31:13 vps528815 nginx[23866]: nginx: configuration file /etc/nginx/nginx.conf test failed
Mar 25 18:31:13 vps528815 systemd[1]: nginx.service: Control process exited, code=exited status=1
Mar 25 18:31:13 vps528815 systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Mar 25 18:31:13 vps528815 systemd[1]: nginx.service: Unit entered failed state.
Mar 25 18:31:13 vps528815 systemd[1]: nginx.service: Failed with result 'exit-code'.
Mar 25 18:33:42 vps528815 systemd[1]: Starting A high performance web server and a reverse proxy server...
Mar 25 18:33:42 vps528815 nginx[23898]: nginx: [emerg] a duplicate default server for 0.0.0.0:80 in /etc/nginx/sites-enabled/fb:22
Mar 25 18:33:42 vps528815 nginx[23898]: nginx: configuration file /etc/nginx/nginx.conf test failed
Mar 25 18:33:42 vps528815 systemd[1]: nginx.service: Control process exited, code=exited status=1
Mar 25 18:33:42 vps528815 systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Mar 25 18:33:42 vps528815 systemd[1]: nginx.service: Unit entered failed state.
Mar 25 18:33:42 vps528815 systemd[1]: nginx.service: Failed with result 'exit-code'.
Mar 25 18:34:13 vps528815 systemd[1]: nginx.service: Unit cannot be reloaded because it is inactive.
Mar 25 18:34:22 vps528815 systemd[1]: Starting A high performance web server and a reverse proxy server...
Mar 25 18:34:22 vps528815 nginx[23931]: nginx: [emerg] a duplicate default server for 0.0.0.0:80 in /etc/nginx/sites-enabled/fb:22
Mar 25 18:34:22 vps528815 nginx[23931]: nginx: configuration file /etc/nginx/nginx.conf test failed
Mar 25 18:34:22 vps528815 systemd[1]: nginx.service: Control process exited, code=exited status=1
Mar 25 18:34:22 vps528815 systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Mar 25 18:34:22 vps528815 systemd[1]: nginx.service: Unit entered failed state.
Mar 25 18:34:22 vps528815 systemd[1]: nginx.service: Failed with result 'exit-code'.
Mar 25 18:42:59 vps528815 systemd[1]: Starting A high performance web server and a reverse proxy server...
Mar 25 18:42:59 vps528815 nginx[23971]: nginx: [emerg] "try_files" directive is not allowed here in /etc/nginx/sites-enabled/fb:52
Mar 25 18:42:59 vps528815 nginx[23971]: nginx: configuration file /etc/nginx/nginx.conf test failed
Mar 25 18:42:59 vps528815 systemd[1]: nginx.service: Control process exited, code=exited status=1
Mar 25 18:42:59 vps528815 systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Mar 25 18:42:59 vps528815 systemd[1]: nginx.service: Unit entered failed state.
Mar 25 18:42:59 vps528815 systemd[1]: nginx.service: Failed with result 'exit-code'.
Mar 25 18:44:04 vps528815 systemd[1]: Starting A high performance web server and a reverse proxy server...
Mar 25 18:44:04 vps528815 nginx[23999]: nginx: [emerg] "try_files" directive is not allowed here in /etc/nginx/sites-enabled/default:51
Mar 25 18:44:04 vps528815 nginx[23999]: nginx: configuration file /etc/nginx/nginx.conf test failed
Mar 25 18:44:04 vps528815 systemd[1]: nginx.service: Control process exited, code=exited status=1
Mar 25 18:44:04 vps528815 systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Mar 25 18:44:04 vps528815 systemd[1]: nginx.service: Unit entered failed state.
Mar 25 18:44:04 vps528815 systemd[1]: nginx.service: Failed with result 'exit-code'.
Mar 25 19:43:51 vps528815 systemd[1]: Starting A high performance web server and a reverse proxy server...
Mar 25 19:43:51 vps528815 nginx[24096]: nginx: [emerg] "try_files" directive is not allowed here in /etc/nginx/sites-enabled/fb:52
Mar 25 19:43:51 vps528815 nginx[24096]: nginx: configuration file /etc/nginx/nginx.conf test failed
Mar 25 19:43:51 vps528815 systemd[1]: nginx.service: Control process exited, code=exited status=1
Mar 25 19:43:51 vps528815 systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Mar 25 19:43:51 vps528815 systemd[1]: nginx.service: Unit entered failed state.
Mar 25 19:43:51 vps528815 systemd[1]: nginx.service: Failed with result 'exit-code'.
Mar 25 19:59:33 vps528815 systemd[1]: Starting A high performance web server and a reverse proxy server...
Mar 25 19:59:33 vps528815 nginx[24143]: nginx: [emerg] a duplicate default server for 0.0.0.0:80 in /etc/nginx/sites-enabled/default:22
Mar 25 19:59:33 vps528815 nginx[24143]: nginx: configuration file /etc/nginx/nginx.conf test failed
Mar 25 19:59:33 vps528815 systemd[1]: nginx.service: Control process exited, code=exited status=1
Mar 25 19:59:33 vps528815 systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Mar 25 19:59:33 vps528815 systemd[1]: nginx.service: Unit entered failed state.
Mar 25 19:59:33 vps528815 systemd[1]: nginx.service: Failed with result 'exit-code'.
Mar 25 20:00:32 vps528815 systemd[1]: Starting A high performance web server and a reverse proxy server...
Mar 25 20:00:32 vps528815 nginx[24172]: nginx: [emerg] a duplicate default server for 0.0.0.0:80 in /etc/nginx/sites-enabled/default:22
Mar 25 20:00:32 vps528815 nginx[24172]: nginx: configuration file /etc/nginx/nginx.conf test failed
Mar 25 20:00:32 vps528815 systemd[1]: nginx.service: Control process exited, code=exited status=1
Mar 25 20:00:32 vps528815 systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Mar 25 20:00:32 vps528815 systemd[1]: nginx.service: Unit entered failed state.
Mar 25 20:00:32 vps528815 systemd[1]: nginx.service: Failed with result 'exit-code'.
Mar 28 18:33:51 vps528815 systemd[1]: Starting A high performance web server and a reverse proxy server...
Mar 28 18:33:51 vps528815 systemd[1]: nginx.service: Failed to read PID from file /run/nginx.pid: Invalid argument
Mar 28 18:33:51 vps528815 systemd[1]: Started A high performance web server and a reverse proxy server.
Mar 28 18:36:23 vps528815 systemd[1]: Reloading A high performance web server and a reverse proxy server.
Mar 28 18:36:23 vps528815 nginx[3107]: nginx: [emerg] BIO_new_file("/etc/letsencrypt/live/video.franckboucher.com/fullchain.pem") failed (SSL: error:02001002:system library:fopen:No such file
or directory:fopen('/etc/letsencrypt/live/video.franckboucher.com/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
Mar 28 18:36:23 vps528815 systemd[1]: nginx.service: Control process exited, code=exited status=1
Mar 28 18:36:23 vps528815 systemd[1]: Reload failed for A high performance web server and a reverse proxy server.
Mar 28 18:38:16 vps528815 systemd[1]: Reloading A high performance web server and a reverse proxy server.
Mar 28 18:38:16 vps528815 nginx[3125]: nginx: [emerg] BIO_new_file("/etc/letsencrypt/live/video.franckboucher.com/fullchain.pem") failed (SSL: error:02001002:system library:fopen:No such file
or directory:fopen('/etc/letsencrypt/live/video.franckboucher.com/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
Mar 28 18:38:16 vps528815 systemd[1]: nginx.service: Control process exited, code=exited status=1
Mar 28 18:38:16 vps528815 systemd[1]: Reload failed for A high performance web server and a reverse proxy server.
Mar 28 18:38:45 vps528815 systemd[1]: Stopping A high performance web server and a reverse proxy server...
Mar 28 18:38:45 vps528815 systemd[1]: Stopped A high performance web server and a reverse proxy server.
Mar 28 18:38:45 vps528815 systemd[1]: nginx.service: Unit entered failed state.
Mar 28 18:38:45 vps528815 systemd[1]: nginx.service: Failed with result 'exit-code'.
Mar 28 18:38:52 vps528815 systemd[1]: nginx.service: Unit cannot be reloaded because it is inactive.
Mar 28 18:39:03 vps528815 systemd[1]: Starting A high performance web server and a reverse proxy server...
Mar 28 18:39:03 vps528815 nginx[3142]: nginx: [emerg] BIO_new_file("/etc/letsencrypt/live/video.franckboucher.com/fullchain.pem") failed (SSL: error:02001002:system library:fopen:No such file
or directory:fopen('/etc/letsencrypt/live/video.franckboucher.com/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
Mar 28 18:39:03 vps528815 nginx[3142]: nginx: configuration file /etc/nginx/nginx.conf test failed
Mar 28 18:39:03 vps528815 systemd[1]: nginx.service: Control process exited, code=exited status=1
Mar 28 18:39:03 vps528815 systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Mar 28 18:39:03 vps528815 systemd[1]: nginx.service: Unit entered failed state.
Mar 28 18:39:03 vps528815 systemd[1]: nginx.service: Failed with result 'exit-code'.
Mar 28 18:41:38 vps528815 systemd[1]: Starting A high performance web server and a reverse proxy server...
Mar 28 18:41:38 vps528815 systemd[1]: nginx.service: Failed to read PID from file /run/nginx.pid: Invalid argument
Mar 28 18:41:38 vps528815 systemd[1]: Started A high performance web server and a reverse proxy server.
Mar 28 18:54:07 vps528815 systemd[1]: Reloading A high performance web server and a reverse proxy server.
Mar 28 18:54:07 vps528815 nginx[3202]: nginx: [emerg] BIO_new_file("/etc/letsencrypt/live/video.franckboucher.com/fullchain.pem") failed (SSL: error:02001002:system library:fopen:No such file
or directory:fopen('/etc/letsencrypt/live/video.franckboucher.com/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
Mar 28 18:54:07 vps528815 systemd[1]: nginx.service: Control process exited, code=exited status=1
Mar 28 18:54:07 vps528815 systemd[1]: Reload failed for A high performance web server and a reverse proxy server.
Mar 28 18:58:21 vps528815 systemd[1]: Stopping A high performance web server and a reverse proxy server...
Mar 28 18:58:21 vps528815 systemd[1]: Stopped A high performance web server and a reverse proxy server.
Mar 28 18:58:21 vps528815 systemd[1]: nginx.service: Unit entered failed state.
Mar 28 18:58:21 vps528815 systemd[1]: nginx.service: Failed with result 'exit-code'.
Mar 28 18:58:25 vps528815 systemd[1]: Starting A high performance web server and a reverse proxy server...
Mar 28 18:58:25 vps528815 nginx[3327]: nginx: [emerg] BIO_new_file("/etc/letsencrypt/live/video.franckboucher.com/fullchain.pem") failed (SSL: error:02001002:system library:fopen:No such file
or directory:fopen('/etc/letsencrypt/live/video.franckboucher.com/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
Mar 28 18:58:25 vps528815 nginx[3327]: nginx: configuration file /etc/nginx/nginx.conf test failed
Mar 28 18:58:25 vps528815 systemd[1]: nginx.service: Control process exited, code=exited status=1
Mar 28 18:58:25 vps528815 systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Mar 28 18:58:25 vps528815 systemd[1]: nginx.service: Unit entered failed state.
Mar 28 18:58:25 vps528815 systemd[1]: nginx.service: Failed with result 'exit-code'.

Le log que tu nous montre indique bien une erreur de configuration de nginx avec nginx: [emerg] a duplicate default server for 0.0.0.0:80 in /etc/nginx/sites-enabled/fb:22. Ça tombe bien, nginx a un outil de test de configuration, sans doute plus locace : nginx -t.

Merci. pas eu beaucoup de temps en ce moment, je m’y remets. Voici ce que j’ai :

$ nginx -t
nginx: [emerg] BIO_new_file("/etc/letsencrypt/live/video.franckboucher.com/fullchain.pem") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/video.franckboucher.com/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
nginx: configuration file /etc/nginx/nginx.conf test failed

J’ai fais sauter le https pour le moment (j’y reviendrai), du coup Nginx fonctionne :slight_smile:

Mais le Daemon peertube boot en boucle O.O :

Apr 01 12:06:56 vps528815 systemd[1]: Started PeerTube daemon.
Apr 01 12:06:56 vps528815 peertube[16766]: > peertube@1.0.0-beta.1 start /var/www/peertube
Apr 01 12:06:56 vps528815 peertube[16766]: > node dist/server
Apr 01 12:06:59 vps528815 peertube[16766]: (node:16777) UnhandledPromiseRejectionWarning: SequelizeConnectionError: password authentication failed for user "peertube"
Apr 01 12:06:59 vps528815 peertube[16766]:     at connection.connect.err (/var/www/peertube/node_modules/sequelize/lib/dialects/postgres/connection-manager.js:128:24)
Apr 01 12:06:59 vps528815 peertube[16766]:     at Connection.connectingErrorHandler (/var/www/peertube/node_modules/pg/lib/client.js:123:14)
Apr 01 12:06:59 vps528815 peertube[16766]:     at emitOne (events.js:116:13)
Apr 01 12:06:59 vps528815 peertube[16766]:     at Connection.emit (events.js:211:7)
Apr 01 12:06:59 vps528815 peertube[16766]:     at Socket.<anonymous> (/var/www/peertube/node_modules/pg/lib/connection.js:117:12)
Apr 01 12:06:59 vps528815 peertube[16766]:     at emitOne (events.js:116:13)
Apr 01 12:06:59 vps528815 peertube[16766]:     at Socket.emit (events.js:211:7)
Apr 01 12:06:59 vps528815 peertube[16766]:     at addChunk (_stream_readable.js:263:12)
Apr 01 12:06:59 vps528815 peertube[16766]:     at readableAddChunk (_stream_readable.js:250:11)
Apr 01 12:06:59 vps528815 peertube[16766]:     at Socket.Readable.push (_stream_readable.js:208:10)
Apr 01 12:06:59 vps528815 peertube[16766]:     at TCP.onread (net.js:607:20)
Apr 01 12:06:59 vps528815 peertube[16766]: (node:16777) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
Apr 01 12:06:59 vps528815 peertube[16766]: (node:16777) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Apr 01 12:06:59 vps528815 systemd[1]: peertube.service: Service hold-off time over, scheduling restart.
Apr 01 12:06:59 vps528815 systemd[1]: Stopped PeerTube daemon.
Apr 01 12:06:59 vps528815 systemd[1]: Started PeerTube daemon.

J’ai ça dans mon dossier /var/www/peertube/ :

~$ ls -la
total 408
drwxr-xr-x  16 peertube peertube   4096 Apr  1 12:10 .
drwxr-xr-x   7 root     root       4096 Mar 26 18:33 ..
-rw-------   1 peertube peertube   4777 Mar 28 21:30 .bash_history
-rw-r--r--   1 peertube peertube    220 May 15  2017 .bash_logout
-rw-r--r--   1 peertube peertube   3526 May 15  2017 .bashrc
drwxr-xr-x   3 peertube peertube   4096 Mar 28 18:17 .cache
drwxr-xr-x   4 root     root       4096 Apr  1 12:05 client
drwxr-xr-x   2 peertube peertube   4096 Apr  1 12:05 config
drwx------   3 peertube peertube   4096 Mar 28 18:19 .config
-rw-r--r--   1 peertube peertube   1394 Apr  1 12:05 CREDITS.md
drwxr-xr-x   5 root     root       4096 Apr  1 12:05 dist
-rw-r--r--   1 peertube peertube   6486 Apr  1 12:05 FAQ.md
-rw-r--r--   1 peertube peertube  34520 Apr  1 12:05 LICENSE
drwxr-xr-x   2 peertube peertube   4096 Mar 26 18:55 .nano
drwxr-xr-x   3 peertube peertube   4096 Mar 28 18:18 .node-gyp
drwxr-xr-x 430 root     root      16384 Apr  1 12:05 node_modules
drwxr-xr-x   4 peertube peertube   4096 Mar 28 18:57 .npm
-rw-r--r--   1 peertube peertube   4171 Apr  1 12:05 package.json
-rw-r--r--   1 peertube peertube   4424 Apr  1 11:38 peertube.save
-rw-r--r--   1 peertube peertube    675 May 15  2017 .profile
-rw-r--r--   1 peertube peertube   4947 Apr  1 12:05 README.md
drwxr-xr-x   7 root     root       4096 Apr  1 12:05 scripts
drwxr-xr-x   3 peertube peertube   4096 Apr  1 12:05 storage
drwxr-xr-x   7 root     root       4096 Apr  1 12:05 support
-rw-r--r--   1 peertube peertube    500 Apr  1 12:05 tsconfig.json
drwxr-xr-x   3 peertube peertube   4096 Mar 26 18:20 versions
-rw-r--r--   1 peertube peertube    165 Mar 26 18:20 .wget-hsts
drwxr-xr-x   3 peertube peertube   4096 Mar 28 18:18 .yarn
-rw-r--r--   1 peertube peertube 230387 Apr  1 12:05 yarn.lock
-rw-r--r--   1 peertube peertube    116 Apr  1 11:54 .yarnrc

Merci pour l’aide.

Vu que j’ai la sensation d’avoir merdé plein de fois et d’avoir un peu tout cassé, je repars de 0 ! Je ré-installe tout.
Merci pour l’aide apporté, je reviens vers vous sur le même fil si j’ai besoin d’aide.
A+

As-tu bien créé l’utilisateur et la base peertube sur PostgreSQL? As-tu bien pris le temps de correctement configurer ton fichier config/production.yaml ? La connexion à la base de données semble mal se passer…

C’est bien de recommencer mais je pense qu’il faudrait surtout comprendre à quel niveau il y a eu un soucis! :slight_smile: