Nightly versions bug

I’ve tried installing the latest nightly builds, these are:
peertube-nightly-2021-05-28.tar.xz
peertube-nightly-2021-05-29.tar.xz
peertube-nightly-2021-05-30.tar.xz
peertube-nightly-2021-05-31.tar.xz

And they all give an error when launching Peertube

peertube@media:~/peertube-latest$ sudo journalctl -fu peertube – Logs begin at Mon 2021-05-31 13:27:24 MSK. –
мая 31 13:36:28 media peertube[2864]: npm ERR! A complete log of this run can be found in:
мая 31 13:36:28 media peertube[2864]: npm ERR! /var/www/peertube/.npm/_logs/2021-05-31T10_36_28_694Z-debug.log
мая 31 13:36:28 media systemd[1]: peertube.service: Main process exited, code=exited, status=255/EXCEPTION
мая 31 13:36:28 media systemd[1]: peertube.service: Failed with result ‹ exit-code ›.
мая 31 13:36:28 media systemd[1]: peertube.service: Service RestartSec=100ms expired, scheduling restart.
мая 31 13:36:28 media systemd[1]: peertube.service: Scheduled restart job, restart counter is at 5.
мая 31 13:36:28 media systemd[1]: Stopped PeerTube daemon.
мая 31 13:36:28 media systemd[1]: peertube.service: Start request repeated too quickly.
мая 31 13:36:28 media systemd[1]: peertube.service: Failed with result ‹ exit-code ›.
мая 31 13:36:28 media systemd[1]: Failed to start PeerTube daemon.

peertube@media:~$ cat /var/www/peertube/.npm/_logs/2021-05-31T10_36_28_694Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ ‹ /usr/bin/node ›, ‹ /usr/bin/npm ›, ‹ start › ]
2 info using npm@6.14.12
3 info using node@v12.22.1
4 verbose run-script [ ‹ prestart ›, ‹ start ›, ‹ poststart › ]
5 info lifecycle peertube@3.2.0-nightly-2021-05-31~prestart: peertube@3.2.0-nightly-2021-05-31
6 info lifecycle peertube@3.2.0-nightly-2021-05-31~start: peertube@3.2.0-nightly-2021-05-31
7 verbose lifecycle peertube@3.2.0-nightly-2021-05-31~start: unsafe-perm in lifecycle true
8 verbose lifecycle peertube@3.2.0-nightly-2021-05-31~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/www/peertube/versions/peertube-nightly-2021-05-31/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
9 verbose lifecycle peertube@3.2.0-nightly-2021-05-31~start: CWD: /var/www/peertube/versions/peertube-nightly-2021-05-31
10 silly lifecycle peertube@3.2.0-nightly-2021-05-31~start: Args: [ ‹ -c ›, ‹ node dist/server › ]
11 silly lifecycle peertube@3.2.0-nightly-2021-05-31~start: Returned: code: 255 signal: null
12 info lifecycle peertube@3.2.0-nightly-2021-05-31~start: Failed to exec start script
13 verbose stack Error: peertube@3.2.0-nightly-2021-05-31 start: node dist/server
13 verbose stack Exit status 255
13 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:314:20)
13 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:314:20)
13 verbose stack at maybeClose (internal/child_process.js:1022:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
14 verbose pkgid peertube@3.2.0-nightly-2021-05-31
15 verbose cwd /var/www/peertube/versions/peertube-nightly-2021-05-31
16 verbose Linux 4.19.0-16-amd64
17 verbose argv « /usr/bin/node » « /usr/bin/npm » « start »
18 verbose node v12.22.1
19 verbose npm v6.14.12
20 error code ELIFECYCLE
21 error errno 255
22 error peertube@3.2.0-nightly-2021-05-31 start: node dist/server
22 error Exit status 255
23 error Failed at the peertube@3.2.0-nightly-2021-05-31 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 255, true ]

And here are the previous versions
peertube-nightly-2021-05-27.tar.xz and even earlier - they work great.

I’ve tried NodeJS 12, 14, 15.

Update your systemd template: PeerTube/peertube.service at develop · Chocobozzz/PeerTube · GitHub

Or try to run PeerTube manually to see what happens (using the same env variables than systemd service).

I copied the config file and systemd file again, now everything started up and works fine.
I don’t know exactly where the error was.
Thank you.