Skip to content

chain certificate of collection #11

@lubepi

Description

@lubepi

Is there a reason why collection.cert is used instead of collection.chain? That way the intermediate certificate is missing and requests with curl, for example, throw an error. I have now changed

const context = node_tls_1.default.createSecureContext({
    key: collection.key,
    cert: collection.cert,
});

to

const context = node_tls_1.default.createSecureContext({
    key: collection.key,
    cert: collection.chain.join(''),
});

in webServer.js on my system to solve that problem.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions