The app can't find my key file no such file or directory - Docker, Ubuntu, Certbot certificates

[Gandalf-Le-Dev]

Here is the error message and my docker command:

$ sudo docker run \
        -p 0.0.0.0:8080:8080 \
        -v /etc/letsencrypt/live/blog.mathisrocher.com:/etc/letsencrypt \
        -v /home/ubuntu/trilium/trilium-data:/home/node/trilium-data \
        zadam/trilium:0.63-latest
No USER_UID specified, leaving 1000
No USER_GID specified, leaving 1000
DB size: 2207 KB
{
  "appVersion": "0.63.5",
  "dbVersion": 228,
  "nodeVersion": "v18.18.2",
  "syncVersion": 32,
  "buildDate": "2024-03-28T07:11:39+01:00",
  "buildRevision": "399458b52f250b22be22d980a78de0b3390d7521",
  "dataDirectory": "/home/node/trilium-data",
  "clipperProtocolVersion": "1.0",
  "utcDateTime": "2024-04-06T22:37:22.511Z"
}
CPU model: AMD EPYC-Milan Processor, logical cores: 2 freq: 2645 Mhz
Trusted reverse proxy: loopback
node:internal/fs/utils:350
    throw err;
    ^

Error: ENOENT: no such file or directory, open '/etc/letsencrypt/privkey.pem'
    at Object.openSync (node:fs:603:3)
    at Object.readFileSync (node:fs:471:35)
    at startHttpServer (/usr/src/app/src/www.js:102:21)
    at startTrilium (/usr/src/app/src/www.js:67:24)
    at Object.<anonymous> (/usr/src/app/src/www.js:40:1)
    at Module._compile (node:internal/modules/cjs/loader:1256:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
    at Module.load (node:internal/modules/cjs/loader:1119:32)
    at Module._load (node:internal/modules/cjs/loader:960:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:86:12) {
  errno: -2,
  syscall: 'open',
  code: 'ENOENT',
  path: '/etc/letsencrypt/privkey.pem'
}

Node.js v18.18.2

I have mounted the volume correctly, here is my trilium config:

[Network]
# host setting is relevant only for web deployments - set the host on which the server will listen
# host=0.0.0.0
# port setting is relevant only for web deployments, desktop builds run on a fixed port (changeable with TRILIUM_PORT environment variable)
port=8080
# true for TLS/SSL/HTTPS (secure), false for HTTP (insecure).
https=true
# path to certificate (run "bash bin/generate-cert.sh" to generate self-signed certificate). Relevant only if https=true
certPath=/etc/letsencrypt/fullchain.pem
keyPath=/etc/letsencrypt/privkey.pem

# setting to give trust to reverse proxies, a comma-separated list of trusted rev. proxy IPs can be specified (CIDR notation is permitted),
# alternatively 'true' will make use of the leftmost IP in X-Forwarded-For, ultimately an integer can be used to tell about the number of hops between
# Trilium (which is hop 0) and the first trusted rev. proxy. 
# once set, expressjs will use the X-Forwarded-For header set by the rev. proxy to determinate the real IPs of clients.
# expressjs shortcuts are supported: loopback(127.0.0.1/8, ::1/128), linklocal(169.254.0.0/16, fe80::/10), uniquelocal(10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, fc00::/7)
trustedReverseProxy=loopback

Should i use nginx to do the TLS instead ?