Node https agent module

Is it possible to use the nodejs https agent module, providing the .cert and .key files in Vercel functions? I have this code:

1const httpsAgent = new Agent({2  cert: process.env.CERTIFICATE,3  key: process.env.KEY,4  rejectUnauthorized: true,5})67const interApi = axios.create({8  baseURL: process.env.BASE_URL,9  httpsAgent,10})

I use the https agent to make requests to this API. Everything works on localhost, but I have this error on Vercel:

1Error: error:0480006C:PEM routines::no start line2    at node:internal/tls/secure-context:70:133    at Array.forEach (<anonymous>)4    at setCerts (node:internal/tls/secure-context:68:3)5    at configSecureContext (node:internal/tls/secure-context:186:5)6    at Object.createSecureContext (node:_tls_common:116:3)7    at Object.connect (node:_tls_wrap:1763:48)8    at Agent.createConnection (node:https:171:22)9    at Agent.createSocket (node:_http_agent:340:26)10    at Agent.addRequest (node:_http_agent:288:10)11    at new ClientRequest (node:_http_client:334:16)12    at p.request (/var/task/.next/server/app/[slug]/page.js:2579:29132)13    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)14    at async h (/var/task/.next/server/app/[slug]/page.js:61:157225)15    at async p (/var/task/.next/server/app/[slug]/page.js:61:157124)16    at async f (/var/task/.next/server/app/[slug]/page.js:61:158205)17    at async u (/var/task/.next/server/app/[slug]/page.js:61:155563)18    at async /var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:16:41819    at async rR (/var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:15:7978)20    at async r7 (/var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:18:1144)21    at async es (/var/task/node_modules/next/dist/compiled/next-server/server.runtime.prod.js:16:26324) {22  library: 'PEM routines',23  reason: 'no start line',24  code: 'ERR_OSSL_PEM_NO_START_LINE',25  digest: '1423523602'26}

When searching the Web for PEM routines:get_name:no start line or ERR_OSSL_PEM_NO_START_LINE I'm presented with a choice of possible sources and solutions for the problem.

https://stackoverflow.com/questions/63030755/error-error0909006cpem-routinesget-nameno-start-line-node suggests it could be something with file encodings, or some .npmrc configuration that should be deleted (for no given reason).

https://stackoverflow.com/questions/66691292/npm-err-code-err-ossl-pem-no-start-line-and-routinesget-nameno-start-line-whe also goes the rather rough way to delete pieces and reset a Node installation (also without adding reasons why this might help).

auth0/node-jsonwebtoken#642 also has more approaches to why this might fail. A repeating pattern is something around line breaks. Another example simply swapped public and private key (:

Is it possible to use the nodejs https agent module, providing the .cert and .key files in Vercel functions? I have this code:

1const httpsAgent = new Agent({2  cert: process.env.CERTIFICATE,3  key: process.env.KEY,4  rejectUnauthorized: true,5})67const interApi = axios.create({8  baseURL: process.env.BASE_URL,9  httpsAgent,10})

I use the https agent to make requests to this API. Everything works on localhost, but I have this error on Vercel:

1Error: error:0480006C:PEM routines::no start line2    at node:internal/tls/secure-context:70:133    at Array.forEach (<anonymous>)4    at setCerts (node:internal/tls/secure-context:68:3)5    at configSecureContext (node:internal/tls/secure-context:186:5)6    at Object.createSecureContext (node:_tls_common:116:3)7    at Object.connect (node:_tls_wrap:1763:48)8    at Agent.createConnection (node:https:171:22)9    at Agent.createSocket (node:_http_agent:340:26)10    at Agent.addRequest (node:_http_agent:288:10)11    at new ClientRequest (node:_http_client:334:16)12    at p.request (/var/task/.next/server/app/[slug]/page.js:2579:29132)13    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)14    at async h (/var/task/.next/server/app/[slug]/page.js:61:157225)15    at async p (/var/task/.next/server/app/[slug]/page.js:61:157124)16    at async f (/var/task/.next/server/app/[slug]/page.js:61:158205)17    at async u (/var/task/.next/server/app/[slug]/page.js:61:155563)18    at async /var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:16:41819    at async rR (/var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:15:7978)20    at async r7 (/var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:18:1144)21    at async es (/var/task/node_modules/next/dist/compiled/next-server/server.runtime.prod.js:16:26324) {22  library: 'PEM routines',23  reason: 'no start line',24  code: 'ERR_OSSL_PEM_NO_START_LINE',25  digest: '1423523602'26}

When searching the Web for PEM routines:get_name:no start line or ERR_OSSL_PEM_NO_START_LINE I'm presented with a choice of possible sources and solutions for the problem.

auth0/node-jsonwebtoken#642 also has more approaches to why this might fail. A repeating pattern is something around line breaks. Another example simply swapped public and private key (: