Production cert and key should support filesystem paths

[pi0]

Ref: https://github.com/nuxt/nuxt.js/issues/12827

Running a production server with SSL needs the NITRO_SSL_CERT and NITRO_SSL_KEY to be from filesystem.

As a workaround (UNIX and Mac), we can use:

NITRO_SSL_CERT="`cat path/to/cert.pem`" NITRO_SSL_KEY="`cat path/to/key.pem`" node .output/server/index.mjs

[dataexcess]

Amazing that worked :D thank you for the quick reply

[dataexcess]

Do you have any idea how to write this line in a package.json file? backticks are not allowed...

[pi0]

You can use a server.sh script that starts the server with SSL.

#!/bin/bash
export NITRO_SSL_CERT="`cat path/to/cert.pem`"
export NITRO_SSL_KEY="`cat path/to/key.pem`"
exec node .output/server/index.mjs

"start": "./server.sh"

[dataexcess]

Works like a charm ✨ thank you! And I can set the PORT and HOST var before, perfect. "start": "HOST=localhost PORT=3001 ./server.sh"

[alex-key]

@pi0 Could it be just as simple as this:

import { readFileSync } from "node:fs";
import { resolve } from "pathe";

...

let cert = process.env.NITRO_SSL_CERT;
let key = process.env.NITRO_SSL_KEY;

if (cert && key) {
  cert = readFileSync(resolve(cert), "utf8");
  key = readFileSync(resolve(key), "utf8");
}

[ananthachetan]

Any idea when the fix will be available?

[rudolfbyker]

For me, even when specifying NITRO_SSL_KEY and NITRO_SSL_CERT, it always starts as HTTP rather than HTTPS.