-
|
This may be because I'm behind a proxy, but the proxy environment variables have been exported correctly on my shell. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
This is almost certainly a corporate proxy/firewall issue. Try these fixes in order:
NODE_TLS_REJECT_UNAUTHORIZED=0 pnpm dlx shadcn init
export NODE_EXTRA_CA_CERTS=/path/to/your/corporate-ca.pem
pnpm dlx shadcn init
pnpm config set proxy http://your-proxy:port
pnpm config set https-proxy http://your-proxy:port
pnpm dlx shadcn init
curl -x http://your-proxy:port 'https://ui.shadcn.com/init?base=radix&style=nova&baseColor=neutral&theme=neutral&iconLibrary=lucide&font=geist&rtl=false' -o init.jsonThen check what error curl gives — that'll tell you exactly what the proxy is blocking. @kalcodes What does |
Beta Was this translation helpful? Give feedback.
Thanks for you support!
After additional searching, I found out, I need to enable node's native proxy support with
export NODE_USE_ENV_PROXY=1environment variable. Since the proxy variablesHTTP[S]_PROXYare already available all that's left to do was enable node's native support.This works
$ export NODE_USE_ENV_PROXY=1 $ pnpm dlx shadcn init