-
-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package search: unable to get local issuer certificate #958
Comments
Thanks for reporting this issue. I'd highly recommend taking a look at the proxy PPM setup to see if you can apply it to your setup. As that's commonly what's required on a enterprise network setup like that. |
I did already. ProxyI played with various proxy server settings, which doen't make sense here - since there is no proxy in between. The proxy script sould™ return DIRECT because for the URL of pulsar packages no proxy is in that script. SSLI can disable Searching for packages that I would like to install is unaffected by all these settings. |
Can I somehow find out what is going on here? Are there logs? |
Sorry for lag, I've been trying to do some investigation on our end. But here's some further details that might be helpful in troubleshooting. When you install a package, the request is being made directly to GitHub to download the source code of the package. So it seems that GitHub is able to work with your corporate proxy settings. Meanwhile when you search for packages that's only hitting the PPR (Pulsar Package Repository) which is hosted in GCP, which doesn't seem to like the corporate proxy settings. As for logging, yeah the request itself is made by the CLI utility PPM, not the actual Pulsar application, that's why DevTools doesn't show anything useful. By running PPM in the command line you may be able to get more errors detailing what's going wrong. Otherwise if we could coordinate like privately messaging on Discord, or if you could let me be aware of a unique search that you could make, such as your username, I could then try to check the logs on our end to see if I can find out any more. |
I think that the certificate error is not a problem in general with the URL of the PPR because ...
in the cmd (Windows) I can search using When I start Pulsar from that SummaryI think Pulsar is getting certificates through Why does the search which is started from Pulsar UI - through |
Thanks in advance for your bug report!
What happened?
The package search in pulsar cannot find packages because of missing certificates.
Error is:
unable to get local issuer certificate
I am in a corporate network and there are special (self-signed?) certificates.
Downloading and installing packages works by passing
NODE_EXTRA_CA_CERTS
as environmental variable to pulsar (more on this here.While this solves the package downloading issue it does not solve the searching issue - should it?
Pulsar version
1.114.2024031604
Which OS does this happen on?
🪟 Windows
OS details
Version 10
Which CPU architecture are you running this on?
x86_64/AMD64
What steps are needed to reproduce this?
Doesn't make sense, since I don't know how the corporate network was created in detail.
Additional Information:
First install ever for me, user installation
The text was updated successfully, but these errors were encountered: