Problèmes avec production.yaml 502 Bad Gateway nginx/1.17.10 (Ubuntu)

Peertube ne semble pas démarrer, obtenant une mauvaise erreur de passerelle
voici les détails
serveur 2 cœurs 2,6 GHz
7,5 Go de RAM DDR3
90 gb hdd
ubuntu 20 lts
J’ai déjà lu cet autre (je pense) article similaire:

J’ai réussi à corriger quelques réflexions après avoir lu mais je n’ai pas pu les résoudre toutes
au cas où vous vous demanderiez, j’ai lu le guide d’installation officiel
et aussi cette menace

et ce tutoriel

chaque commande a été exécutée en tant que root

ENGLISH

Peertube doesn´t seem to start, getting bad gateway error
here is the details
server: 2 cores 2.6 ghz
7.5 gb ram ddr3
90 gb hdd
ubuntu 20 lts

I already read this other (I think) similar post:
Problèmes avec production.yaml 502 Bad Gateway nginx/1.17.10 (Ubuntu)
[Résolu] Redondance PeerTubes sur Yunohost
Systemd indispensable?

I mannaged to fix a few thinks after reading but couldn´t solve them all
in case you wondered I read the official install guide
and also this threat
【Updated】The whole commands to install Peertube for Production · Issue #33 · Chocobozzz/PeerTube · GitHub

and this tutorial
https://www.youtube.com/watch?v=GKiIdk0-JSM

every command was executed as root


//////////////////////////////////////////////////


config/production.yaml

listen:
  hostname: 'localhost'
  port: 9000
# Correspond to your reverse proxy server_name/listen configuration
webserver:
  https: true
  hostname: 'motmot.cf'
  port: 443
rates_limit:
  api:
    # 50 attempts in 10 seconds
    window: 10 seconds
    max: 50
  login:
    # 15 attempts in 5 min
    window: 5 minutes
    max: 15
  signup:
    # 2 attempts in 5 min (only succeeded attempts are taken into account)
    window: 5 minutes
    max: 2
  ask_send_email:
    # 3 attempts in 5 min
    window: 5 minutes
    max: 3
# Proxies to trust to get real client IP
# If you run PeerTube just behind a local proxy (nginx), keep 'loopback'
# If you run PeerTube behind a remote proxy, add the proxy IP address (or subnet)
trust_proxy:
  - 'loopback'

# Your database name will be "peertube"+database.suffix
database:
  hostname: 'localhost'
  port: 5432
  suffix: '_prod'
  username: 'peertube'
  password: 'peertube'
  pool:
    max: 5
# Redis server for short time storage
# You can also specify a 'socket' path to a unix socket but first need to
# comment out hostname and port
redis:
  hostname: 'localhost'
  port: 6379
  auth: null
  db: 0
# SMTP server to send emails
smtp:
  hostname: null
  port: 465 # If you use StartTLS: 587
  username: null
  password: null
  tls: true # If you use StartTLS: false
  disable_starttls: false
  ca_file: null # Used for self signed certificates
  from_address: 'admin@example.com'
email:
  body:
    signature: "MotmotPeer"
  subject:
    prefix: "[MotmotPeer]"
# From the project root directory
storage:
  tmp: '/var/www/peertube/storage/tmp/' # Use to download data (imports etc), store uploaded files before proces>
  avatars: '/var/www/peertube/storage/avatars/'
  videos: '/var/www/peertube/storage/videos/'
  streaming_playlists: '/var/www/peertube/storage/streaming-playlists/'
  redundancy: '/var/www/peertube/storage/redundancy/'
  logs: '/var/www/peertube/storage/logs/'
  previews: '/var/www/peertube/storage/previews/'
  thumbnails: '/var/www/peertube/storage/thumbnails/'
  torrents: '/var/www/peertube/storage/torrents/'
  captions: '/var/www/peertube/storage/captions/'
  cache: '/var/www/peertube/storage/cache/'
  plugins: '/var/www/peertube/storage/plugins/'
log:
  level: 'info' # debug/info/warning/error
  rotation:
    enabled : true # Enabled by default, if disabled make sure that 'storage.logs' is pointing to a folder handl>
    maxFileSize: 12MB
    maxFiles: 20
  anonymizeIP: true
search:
  # Add ability to fetch remote videos/actors by their URI, that may not be federated with your instance
  # If enabled, the associated group will be able to "escape" from the instance follows
  # That means they will be able to follow channels, watch videos, list videos of non followed instances
  remote_uri:
    users: true
    anonymous: false
trending:
  videos:
    interval_days: 7 # Compute trending videos for the last x days
# Cache remote videos on your server, to help other instances to broadcast the video
# You can define multiple caches using different sizes/strategies
# Once you have defined your strategies, choose which instances you want to cache in admin -> manage follows -> >
redundancy:
  videos:
    check_interval: '1 hour' # How often you want to check new videos to cache
    strategies: # Just uncomment strategies you want
          -
               size: '10GB'
#        # Minimum time the video must remain in the cache. Only accept values > 10 hours (to not overload remot>
               min_lifetime: '48 hours'
               strategy: 'most-views' # Cache videos that have the most views
#      -
#        size: '10GB'
#        # Minimum time the video must remain in the cache. Only accept values > 10 hours (to not overload remot>
#        min_lifetime: '48 hours'
#        strategy: 'trending' # Cache trending videos
#      -
#        size: '10GB'
#        # Minimum time the video must remain in the cache. Only accept values > 10 hours (to not overload remot>
#        min_lifetime: '48 hours'
#        strategy: 'recently-added' # Cache recently added videos
#        min_views: 10 # Having at least x views

csp:
  enabled: false
  report_only: true # CSP directives are still being tested, so disable the report only mode at your own risk!
  report_uri:
tracker:
  # If you disable the tracker, you disable the P2P aspect of PeerTube
  enabled: true
  # Only handle requests on your videos.
  # If you set this to false it means you have a public tracker.
  # Then, it is possible that clients overload your instance with external torrents
  private: true
  # Reject peers that do a lot of announces (could improve privacy of TCP/UDP peers)
  reject_too_many_announces: false
history:
  videos:
    # If you want to limit users videos history
    # -1 means there is no limitations
    # Other values could be '6 months' or '30 days' etc (PeerTube will periodically delete old entries from data>
    max_age: -1
views:
  videos:
    # PeerTube creates a database entry every hour for each video to track views over a period of time
    # This is used in particular by the Trending page
    # PeerTube could remove old remote video views if you want to reduce your database size (video view counter >
    # -1 means no cleanup
    # Other values could be '6 months' or '30 days' etc (PeerTube will periodically delete old entries from data>
    remote:
      max_age: -1

plugins:
  # The website PeerTube will ask for available PeerTube plugins and themes
  # This is an unmoderated plugin index, so only install plugins/themes you trust
  index:
    enabled: true
    check_latest_versions_interval: '12 hours' # How often you want to check new plugins/themes versions
    url: 'https://packages.joinpeertube.org'
###############################################################################
#
# From this point, all the following keys can be overridden by the web interface
# (local-production.json file). If you need to change some values, prefer to
# use the web interface because the configuration will be automatically
# reloaded without any need to restart PeerTube.
#
# /!\ If you already have a local-production.json file, the modification of the
# following keys will have no effect /!\.
#
###############################################################################
cache:
  previews:
    size: 500 # Max number of previews you want to cache
  captions:
    size: 500 # Max number of video captions/subtitles you want to cache
admin:
  # Used to generate the root user at first startup
  # And to receive emails from the contact form
  email: 'admin@example.com'
contact_form:
  enabled: false
signup:
  enabled: false
  limit: 10 # When the limit is reached, registrations are disabled. -1 == unlimited
  requires_email_verification: false
  filters:
    cidr: # You can specify CIDR ranges to whitelist (empty = no filtering) or blacklist
      whitelist: []
      blacklist: []
user:
  # Default value of maximum video BYTES the user can upload (does not take into account transcoded files).
  # -1 == unlimited
  video_quota: -1
  video_quota_daily: -1
# If enabled, the video will be transcoded to mp4 (x264) with "faststart" flag
# In addition, if some resolutions are enabled the mp4 video file will be transcoded to these new resolutions.
# Please, do not disable transcoding since many uploaded videos will not work
transcoding:
  enabled: true
  # Allow your users to upload .mkv, .mov, .avi, .flv videos
  allow_additional_extensions: true
  # If a user uploads an audio file, PeerTube will create a video by merging the preview file and the audio file
  allow_audio_files: true
  threads: 1
  resolutions: # Only created if the original video has a higher resolution, uses more storage!
    0p: false # audio-only (creates mp4 without video stream, always created when enabled)

///////////////////////////////////////////////


sudo systemctl restart peertube && sudo journalctl -fu peertube

May 14 04:01:53 motmot systemd[1]: peertube.service: Main process exited, code=exited, status=1/FAILURE
May 14 04:01:53 motmot systemd[1]: peertube.service: Failed with result 'exit-code'.
May 14 04:01:53 motmot systemd[1]: peertube.service: Scheduled restart job, restart counter is at 4.
May 14 04:01:53 motmot systemd[1]: Stopped PeerTube daemon.
May 14 04:01:53 motmot systemd[1]: Started PeerTube daemon.
May 14 04:01:53 motmot peertube[4056]: > peertube@2.1.1 start /var/www/peertube/versions/peertube-v2.1.1
May 14 04:01:53 motmot peertube[4056]: > node dist/server
May 14 04:01:53 motmot peertube[4068]: internal/modules/cjs/loader.js:638
May 14 04:01:53 motmot peertube[4068]:     throw err;
May 14 04:01:53 motmot peertube[4068]:     ^
May 14 04:01:53 motmot peertube[4068]: Error: Cannot find module '/var/www/peertube/versions/peertube-v2.1.1/dist
/server'
May 14 04:01:53 motmot peertube[4068]:     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:63
6:15)
May 14 04:01:53 motmot peertube[4068]:     at Function.Module._load (internal/modules/cjs/loader.js:562:25)
May 14 04:01:53 motmot peertube[4068]:     at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
May 14 04:01:53 motmot peertube[4068]:     at startup (internal/bootstrap/node.js:283:19)
May 14 04:01:53 motmot peertube[4068]:     at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
May 14 04:01:53 motmot peertube[4056]: npm ERR! code ELIFECYCLE
May 14 04:01:53 motmot peertube[4056]: npm ERR! errno 1
May 14 04:01:53 motmot peertube[4056]: npm ERR! peertube@2.1.1 start: `node dist/server`
May 14 04:01:53 motmot peertube[4056]: npm ERR! Exit status 1
May 14 04:01:53 motmot peertube[4056]: npm ERR!
May 14 04:01:53 motmot peertube[4056]: npm ERR! Failed at the peertube@2.1.1 start script.
May 14 04:01:53 motmot peertube[4056]: npm ERR! This is probably not a problem with npm. There is likely addition
al logging output above.
May 14 04:01:53 motmot peertube[4056]: npm ERR! A complete log of this run can be found in:
May 14 04:01:53 motmot peertube[4056]: npm ERR!     /var/www/peertube/.npm/_logs/2020-05-14T04_01_53_790Z-debug.l
og
May 14 04:01:53 motmot systemd[1]: peertube.service: Main process exited, code=exited, status=1/FAILURE
May 14 04:01:53 motmot systemd[1]: peertube.service: Failed with result 'exit-code'.
May 14 04:01:53 motmot systemd[1]: peertube.service: Scheduled restart job, restart counter is at 5.
May 14 04:01:53 motmot systemd[1]: Stopped PeerTube daemon.
May 14 04:01:53 motmot systemd[1]: peertube.service: Start request repeated too quickly.
May 14 04:01:53 motmot systemd[1]: peertube.service: Failed with result 'exit-code'.
May 14 04:01:53 motmot systemd[1]: peertube.service: Scheduled restart job, restart counter is at 5.
May 14 04:01:53 motmot systemd[1]: Stopped PeerTube daemon.
May 14 04:01:53 motmot systemd[1]: peertube.service: Start request repeated too quickly.
May 14 04:01:53 motmot systemd[1]: peertube.service: Failed with result 'exit-code'.
May 14 04:01:53 motmot systemd[1]: Failed to start PeerTube daemon.

/////////////////////////////////////


Je suis vraiment désespéré à ce stade après des heures à essayer différentes configurations
toute aide serait très appréciée

N’hésitez pas à me demander toute autre sortie de n’importe quelle commande

Merci d’avance

ENGLISH

I´m really desperate at this point after hours trying different configurations
any help would be highly appresiated

Pls feel free to ask me any other output of any command

Thanks in advance

Bonjour,

Il semble qu’il y ait eu un soucis à l’installation. Je dirais de tout recommencer depuis le début en suivant ce guide : https://docs.joinpeertube.org/#/install-any-os

Bonjour,

Je vous remercie
Je vais réinstaller ubuntu
et recommencer à zéro je reviendrai sur cette page en cas de problème

Merci beaucoup pour cet excellent logiciel

vous êtes géniaux

Bonjour

de retour pour de l’aide
Après avoir réinstallé Ubuntu
(compris que le numéro précédent était un commentaire déplacé
/var/www/peertube/config/production.yaml line 341, column 5 )

Je reçois cette nouvelle erreur

sudo systemctl start peertube && journalctl -f -u peertube
  
     output: 

-- Logs begin at Fri 2020-05-15 06:00:41 UTC. --
May 15 08:45:38 motmot systemd[1]: peertube.service: Main process exited, code=exited, status=1/FAILURE
May 15 08:45:38 motmot systemd[1]: peertube.service: Failed with result 'exit-code'.
May 15 08:45:38 motmot systemd[1]: peertube.service: Scheduled restart job, restart counter is at 5.
May 15 08:45:38 motmot systemd[1]: Stopped PeerTube daemon.
May 15 08:45:38 motmot systemd[1]: peertube.service: Start request repeated too quickly.
May 15 08:45:38 motmot systemd[1]: peertube.service: Failed with result 'exit-code'.
May 15 08:45:38 motmot systemd[1]: Failed to start PeerTube daemon.
May 15 08:59:37 motmot systemd[1]: Started PeerTube daemon.
May 15 08:59:37 motmot peertube[17656]: > peertube@2.1.1 start /var/www/peertube/versions/peertube-v2.1.1
May 15 08:59:37 motmot peertube[17656]: > node dist/server

Je vois toujours l’erreur 502 Bad Gateway
mais autre que le seul
erreur dans les journaux de la console
est celui que j’ai montré ci-dessus

toute suggestion sur où est l’erreur
ou un autre journal pour vérifier?