You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 14, 2023. It is now read-only.
Cheers. I just finished setting up an LXC container with NPM and certbun, and noticed that NPM uses only the full certificate chain, which certbun doesn't produce.
Producing the chain is not difficult, but there are some pitfalls:
User must know the order in which the certificates are concatenated.
The pem file for domain cert. does not end with a newline, requiring a manual fixup.
Additionally, if the server requires full chain certificate to function, then the concatenation steps must be somehow squeezed into/before the "server restart" command.
Not sure how many people use certbun with NPM (as NPM already has a bundled Let's Encrypt generation/refresh tool), but I would have appreciated if certbun config had an optional setting like fullchainCertLocation where certbun would output the concatenated certificate chain. (Anyone not wishing to have the certificated could set it to /dev/null as I'm currently doing with public key).
In the meantime, I'm using the following commandToReloadWebserver to deal with NPM:
Cheers. I just finished setting up an LXC container with NPM and certbun, and noticed that NPM uses only the full certificate chain, which certbun doesn't produce.
Producing the chain is not difficult, but there are some pitfalls:
Additionally, if the server requires full chain certificate to function, then the concatenation steps must be somehow squeezed into/before the "server restart" command.
Not sure how many people use certbun with NPM (as NPM already has a bundled Let's Encrypt generation/refresh tool), but I would have appreciated if certbun config had an optional setting like
fullchainCertLocation
where certbun would output the concatenated certificate chain. (Anyone not wishing to have the certificated could set it to/dev/null
as I'm currently doing with public key).In the meantime, I'm using the following
commandToReloadWebserver
to deal with NPM:The text was updated successfully, but these errors were encountered: