# NoSSHKey

> The Workspace accepts only the SSHKeys named in spec.sshKeys, or every project member's keys when it names none.

Source: https://nodus-platform-site.pages.dev/docs/reference/errors/no-ssh-key/
Build revision: 211ad9f836655b1c3a2668c4693e442471f28614

<!-- Code generated by tools/errgen. DO NOT EDIT. -->

**HTTP status:** 403 · **Retryable:** no

The Workspace accepts only the SSHKeys named in spec.sshKeys, or every project member’s keys when it names none.

## Message

```text
no SSH key of yours may log in to workspace "{name}"
```

## What to do

add a key with `nodus create sshkey --from-file ~/.ssh/id_ed25519.pub`, or ask the owner to list yours in spec.sshKeys

## On the wire

The response is a Kubernetes `Status` with `reason: NoSSHKey` and `code: 403`, plus `fix`, `docs` (this page) and `requestId`. `details.causes` lists the fields involved, when there are any. The CLI prints the fix and the request id; the Python SDK raises `nodus.errors.NoSSHKey`.