keybase / keybase/client

TLS Handshake error in Keybase from within corporate intranet

Open
#9,207 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

Hi, I'm trying to proof-of-concept Keybase as a useful tool at work but cannot get it working within our network. It works fine on my non-work machines, and works fine on my work machine when using an outside network.

I've already asked the network infrastructure to whitelist api.keybase.io. Now that that is done, I can install and open keybase and sign in, but most functionality fails.

Most/all ui features show this error:

Error: API network error: doRetry failed, attempts: 6, timeout 11.390625s, last err: Get https://api.keybase.io/_/api/1.0/sesscheck.json: remote error: tls: handshake failure at l.t (file:///C:/Users/Dev/AppData/Local/Keybase/Gui/resources/app/desktop/dist/index.bundle.js:1:249154) at l (file:///C:/Users/Dev/AppData/Local/Keybase/Gui/resources/app/desktop/dist/index.bundle.js:1:249758) at s (file:///C:/Users/Dev/AppData/Local/Keybase/Gui/resources/app/desktop/dist/index.bundle.js:1:249449) at t.convertToError (file:///C:/Users/Dev/AppData/Local/Keybase/Gui/resources/app/desktop/dist/index.bundle.js:1:249636) at _rpcClient.invoke.e (file:///C:/Users/Dev/AppData/Local/Keybase/Gui/resources/app/desktop/dist/index.bundle.js:1:236528) at file:///C:/Users/Dev/AppData/Local/Keybase/Gui/resources/app/desktop/dist/index.bundle.js:11:249324 at e.t.Deferrals.e._call (file:///C:/Users/Dev/AppData/Local/Keybase/Gui/resources/app/desktop/dist/index.bundle.js:6:233825) at file:///C:/Users/Dev/AppData/Local/Keybase/Gui/resources/app/desktop/dist/index.bundle.js:6:233976 at s (file:///C:/Users/Dev/AppData/Local/Keybase/Gui/resources/app/desktop/dist/index.bundle.js:6:233605) at e.t.Deferrals.e._fulfill...

From keybase commandline I get a similar TLS error with a possibly useful error code of 1601:

C:\Users\Dev\AppData\Local\Keybase>keybase id chris

I will do a keybase log send and add the id. This may well be an issue on our side, but I need some guidance as to what to ask the network team to change, my network is otherwise usable and functional.

Keybase GUI Version: 1.0.33-20171003151350+ea019b3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the recorded keybase id chris failure and the requested keybase log send report, then compare the failed https://api.keybase.io requests with the working outside-network case. Review the bundled index.bundle.js only as needed to correlate the GUI error. Done means determining whether the failure is in the client or corporate network and documenting the network change or client fix required.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.