Proget: The SSL connection could not be established for NPM Feed

kc_2466

Proget 2024.36 (build 5) - Free edition

I've created 3 NPM feeds:
first one connects to npsjs.org in order to cache packages
seconds one has no connectors, and is for local packages
third one aggregates the other two

If you view the feed page for the aggregate feed - you see error messages for both the connectors:

The ProGet server has a valid SSL certificate - Although, if it's relevant, it is issued by our own internal Certificate Authority.

There are no message showing in the Diagnostic Centre.

stevedennis

Hi @kc_2466 ,

This error means that the ProoGet server itself cannot make a secure / SSL connection to the URLs you've configured.

We know that npmjs.org has a valid certificate, so this means that "something" on the server or in your network is interfering with outbound traffic. This is typically a content filter, proxy, or something to that effect.

You would get the same results of if you were to curl those URLs while logged in to the ProGet server, running under the same user that ProGet is running as.

Thanks,
Steve

kc_2466

It's not the feed that connects directly to npmjs.org that has these errors, it's the feed that aggregates the other two - so it's almost as if it's having a problem with it's own feeds?

ProGet is running under docker, and I don't think your docker container has curl - so that makes it tricky.

stevedennis

Hi @kc_2466,

I see - so they are "self-connectors", and ProGet is effectively connecting to itself. In that case, then the ProGet server is not "trusting" your in-house certificates.

You'll need tot add a self-signed CA to Docker configuration. See the self-signed-ca option:
https://docs.inedo.com/docs/installation/linux/docker-guide

Cheers,
Steve

kc_2466

Yes - they are "self-connectors". We've now bought an externally signed certificate, as it seemed like the simpler option (the in house cert option was causing other issues too). However that hasn't resolved the issue with the self-connectors.

However, I've just edited those connectors manually to use http rather than https, and that has resolved the issue. But It's not really an ideal solution.

So it looks like from inside the docker container it's still not "trusting" the externally signed certificate.