keybase / keybase/keybase-issues
Proxy set up with Keybase-Installer
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I'm currently attempting to install keybase on a windows system, however i'm behind a proxy. I have set up my proxy in npm, but cannot run the installer now. I was able to download the installer, so I know I have a good connection, so is there a way to set up a proxy for the command 'keybase-installer'? Here' s the output I get:
C:\Users\[Username]>keybase-installer
info: Made temporary directory: C:\Users\[Username]\AppData\Local\Temp\keybase_ins
tall_[...]
warn: No code-signing key (code@keybase.io) in GPG keychain
info: Fetching URL https://dist.keybase.io/sig/files/1/keyset.json
info: cleaning up tmpdir C:\Users\[Username]\AppData\Local\Temp\keybase_install_[...]
error: connect ECONNREFUSED
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Windows keybase-installer command behind a proxy and inspect how its npm proxy configuration affects the request to https://dist.keybase.io/sig/files/1/keyset.json. Done means the installer can fetch that URL and continue without ECONNREFUSED.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100