keybase / keybase/keybase-issues
Error: Cannot find a public key for '<username>'
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
It's been a few years since I last encrypted a message via the web interface (https://keybase.io/encrypt), but now I get the error `Error: Cannot find a public key for ''` for most users I've checked, including myself—but can still encrypt messages to them via the desktop app or CLI, and can still decrypt messages sent to me via the web interface.



No JS console or network errors are visible in the browser dev tools.
In case it's helpful, I received the same error when attempting to encrypt messages to hellobot, @malgorithms, and a handful of other randomly selected users, but *did* successfully encrypt a message to @maxtaco (but could not sign it—got the same error if I tried). So it's not *completely* broken! :)
(Note: decryption via the web interface only works for PGP messages: saltpack messages (like the desktop app produces) fail in the web interface with the message `Error: no header found`. Presumably saltpack just isn't supported via the web interface, but the web UI and error message are unclear.)
Contributor guide
No contributing guide indexed for this repository
Research direction
The payload names only the web entry point at keybase.io/encrypt and browser developer tools; start by reproducing encryption and signing there, then compare the behavior with the working desktop app or CLI. Done means the reported accounts can be encrypted to and signed for through the web interface, with a clear response for unsupported saltpack decryption.
Written by the indexing model from the issue text.
Assessment
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100