Cannot install Shadcn-ui because of self-signed certificate during the installation

[YassouSr]

I cannot install the package because of error shown below, although I have disabled the company proxy and used my 4G to download the package.

I have tried to change the configuration of pnpm like I have used to do with npm but the problem persists.

D:\my-project>pnpm config set strict-ssl false

D:\my-project>pnpm dlx shadcn init
✔ Preflight checks.
✔ Verifying framework. Found Vite.
✔ Validating Tailwind CSS config. Found v4.
✔ Validating import alias.


Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

request to https://ui.shadcn.com/r/styles/index.json failed, reason: self-signed certificate in certificate chain

How to solve this problem ?.

[PxPerfectMike]

Hi YassouSr,

The error you're encountering is related to a self-signed certificate in the certificate chain when trying to access https://ui.shadcn.com during the shadcn-ui installation. This is a known issue that has been reported by other users as well when trying to install shadcn-ui components.

You've already tried setting pnpm config set strict-ssl false, but as noted in a similar issue with pnpm, sometimes the strict-ssl and cafile settings are ignored in pnpm, which explains why your attempt didn't work.

Here are a few solutions you can try:

1. Set the NODE_TLS_REJECT_UNAUTHORIZED environment variable temporarily:

   For Windows (in Command Prompt):

   set NODE_TLS_REJECT_UNAUTHORIZED=0
   pnpm dlx shadcn init
   

   For Windows (in PowerShell):

   $env:NODE_TLS_REJECT_UNAUTHORIZED=0
   pnpm dlx shadcn init
   

   For Linux/macOS:

   NODE_TLS_REJECT_UNAUTHORIZED=0 pnpm dlx shadcn init
   

2. If you're behind a corporate proxy/firewall:

   If you're behind a corporate proxy that uses certificate inspection (like Netskope), you may need to export the certificate from your browser and set the NODE_EXTRA_CA_CERTS environment variable:

   $env:NODE_EXTRA_CA_CERTS="path\to\your\exported\certificate.pem"
   pnpm dlx shadcn init
   

3. Try using npm instead of pnpm for just the initialization:

   Some users have reported that using npm works when pnpm fails:

   NODE_TLS_REJECT_UNAUTHORIZED=0 npx shadcn@latest init
   

Note: Setting NODE_TLS_REJECT_UNAUTHORIZED=0 disables SSL certificate verification, which should only be used temporarily for development purposes. It's not recommended for production environments as it can expose you to man-in-the-middle attacks.