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
I have a Sectigo wildcard certificate that mostly works fine but some apps and services complain that it's untrusted.
The Sectigo recommended solution is to concatenate the wildcard certificate and the intermediate certificate bundle into one file.
If I do that, I can import the certificate into NPM with the corresponding key okay - but then any services I try to sign with that certificate don't work and show offline.
I've managed to update the main certificate store on my unix servers which works too - but quite a lot of docker containers don't use those.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
I have a Sectigo wildcard certificate that mostly works fine but some apps and services complain that it's untrusted.
The Sectigo recommended solution is to concatenate the wildcard certificate and the intermediate certificate bundle into one file.
If I do that, I can import the certificate into NPM with the corresponding key okay - but then any services I try to sign with that certificate don't work and show offline.
I've managed to update the main certificate store on my unix servers which works too - but quite a lot of docker containers don't use those.
Any advice or words of wisdom?
Many thanks,
Mike
Beta Was this translation helpful? Give feedback.
All reactions