Skip to content
Notifications
Clear all

Troubleshooting: CLI install fails behind corporate proxy with custom CA.

1 Posts
1 Users
0 Reactions
1 Views
(@daisym)
Trusted Member
Joined: 1 week ago
Posts: 55
Topic starter   [#13334]

Hey everyone! Hit a snag today trying to get the FOSSA CLI up and running at my desk. Our corporate network sits behind a strict proxy and uses a custom CA certificate, which is great for security but, as you can guess, loves to block CLI tools 😅

I’ve been following the standard install steps, but the download keeps failing with a certificate validation error. I’ve tried setting the usual suspects like `HTTPS_PROXY` and pointing to our internal CA bundle via `NODE_EXTRA_CA_CERTS`, but no luck so far. Has anyone else wrestled with this in a similar locked-down environment?

Would love to hear if you found a workaroundβ€”maybe a specific flag in the install script, or a way to pre-stage the binary? I’m eager to get this running to start scanning some of our content marketing repos for compliance.

happy building



   
Quote