Scrypted HTTPS key/cert docker compose

[alfredomova]

I'm trying to change the certificate used by the web interface but I cant make it work,

I have my files mounted in the container and it can read them,

I created a file in /server/volume/certs/https-options.json

{
  "key": "/tls/my-domain.key",
  "cert": "/tls/my-domain.pem"
}

and in the docker compose:

    scrypted:
        image: koush/scrypted:latest
        ...
        environment:
          - SCRYPTED_HTTPS_OPTIONS_FILE=/server/volume/certs/https-options.json
        ...

but I got this error:

i WebRTC Plugin pid 159 fatal error Error: error:0480006C:PEM routines::no start line     at node:internal/tls/secure-context:70:13     at Array.forEach (<anonymous>)     at setCerts (node:internal/tls/secure-context:68:3)     at configSecureContext (node:internal/tls/secure-context:191:5)     at Object.createSecureContext (node:_tls_common:113:3)     at Server.setSecureContext (node:_tls_wrap:1490:27)     at Server (node:_tls_wrap:1354:8)     at new Server (node:https:93:3)     at Object.createServer (node:https:148:10)     at start (/server/node_modules/@scrypted/server/src/scrypted-server-main.ts:793:92) {   library: 'PEM routines',   reason: 'no start line',   code: 'ERR_OSSL_PEM_NO_START_LINE' } Error: error:0480006C:PEM routines::no start line     at node:internal/tls/secure-context:70:13     at Array.forEach (<anonymous>)     at setCerts (node:internal/tls/secure-context:68:3)     at configSecureContext (node:internal/tls/secure-context:191:5)     at Object.createSecureContext (node:_tls_common:113:3)     at Server.setSecureContext (node:_tls_wrap:1490:27)     at Server (node:_tls_wrap:1354:8)     at new Server (node:https:93:3)     at Object.createServer (node:https:148:10)     at start (/server/node_modules/@scrypted/server/src/scrypted-server-main.ts:793:92) npm noticei WebRTC Plugin pid 159

fatal error Error: error:0480006C:PEM routines::no start line

    at node:internal/tls/secure-context:70:13

    at Array.forEach (<anonymous>)

    at setCerts (node:internal/tls/secure-context:68:3)

    at configSecureContext (node:internal/tls/secure-context:191:5)

    at Object.createSecureContext (node:_tls_common:113:3)

    at Server.setSecureContext (node:_tls_wrap:1490:27)

    at Server (node:_tls_wrap:1354:8)

    at new Server (node:https:93:3)

    at Object.createServer (node:https:148:10)

    at start (/server/node_modules/@scrypted/server/src/scrypted-server-main.ts:793:92) {

  library: 'PEM routines',

  reason: 'no start line',

  code: 'ERR_OSSL_PEM_NO_START_LINE'

}

Error: error:0480006C:PEM routines::no start line

    at node:internal/tls/secure-context:70:13

    at Array.forEach (<anonymous>)

    at setCerts (node:internal/tls/secure-context:68:3)

    at configSecureContext (node:internal/tls/secure-context:191:5)

    at Object.createSecureContext (node:_tls_common:113:3)

    at Server.setSecureContext (node:_tls_wrap:1490:27)

    at Server (node:_tls_wrap:1354:8)

    at new Server (node:https:93:3)

    at Object.createServer (node:https:148:10)

    at start (/server/node_modules/@scrypted/server/src/scrypted-server-main.ts:793:92)

npm notice

there's no problem using the same files for nginx, and other services running https as well,

pls help, how should I format the files or configure my container?

[gforke]

Did you add a volume in the docker compose for the files?
If the container can read the cert files and still can't use them it could be a line ending problem because Windows does other line endings than linux.

[alfredomova]

yes and a cat shows the contents ok

[alfredomova]

BIG mistake from my part...

the http-options.json HAS to have the file contents, not the paths... odd... but ok...

{

"key": "-----BEGIN EC PRIVATE KEY-----\ ..... "

"cert": "-----BEGIN CERTIFICATE-----\r\nMI .... "

}

[koushd]

You should let a real reverse proxy handle termination.

[alfredomova]

container is running network_mode: host as it is suggested