> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usekolaos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

Use the error shown in KolaOS to identify the next action. Organization admins manage membership, infrastructure and provider setup; workstation owners manage their own sessions.

## Workstation access

| Message or state | Next action |
| - | - |
| `Only the workstation's owner can open it.` | Select your own workstation. Admin access does not permit opening another member's IDE. |
| `Only the workstation's owner can connect to it over SSH.` | Connect to your own workstation with its registered SSH key. |
| `Only the workstation's owner can start or stop it.` | Ask the owner to start or stop it. |
| `Only admins can resize a workstation. Ask an admin.` | Ask an organization admin to review the resources and plan limit. |
| `Only admins can delete a workstation. Ask an admin.` | Ask an organization admin. Save needed work before deletion. |
| No workstation in the workspace | Ask an admin to check your developer role, membership and provisioning request. Admins cannot join workspaces. |
| `Admins don't join workspaces. Change their role to developer first.` | Add a developer account. An admin cannot add themselves, and the organization must keep an active admin. |
| `QUEUED` | Check the displayed capacity, infrastructure or plan error with an admin. |
| `FAILED` | Read the reported error, fix its cause and choose Start when directed. |
| `BOOTSTRAPPING` | Wait for configuration to finish. After a 30 minute timeout, the failed state tells you to try Start again. |
| `node_full` | The node has no room to start the workstation. Ask an admin to free or add capacity. |

## SSH and editors

| Message or symptom | Next action |
| - | - |
| `Permission denied (publickey)` | Run `kola ssh setup`, wait about 15 seconds and reconnect. |
| `No ED25519 host key is known for ...` | Wait a few seconds after workstation startup, then reconnect. |
| An editor does not list a new workstation | Run `kola ssh setup` again. |
| An editor lists the wrong organization's workstations | Run `kola login --org <organization-id>`, then `kola ssh setup`. |
| VS Code times out while starting a workstation | Reconnect after startup, or raise `remote.SSH.connectTimeout`. |

## AI tools

**No provider** means an admin needs to connect a provider that serves the tool's models. **Model not served** means the selected default model is unavailable from the connected providers. **Provider not working** means the provider's latest connection test failed.

Ask an admin to open **Organization**, then **AI providers**, and fix or test the connection. An admin should also check the organization cap under **Usage and budget** when model requests are blocked.

## Infrastructure setup

For **AWS setup stalled**, check the CloudFormation access stack in the intended account and resume from **Infrastructure**. For a server installer failure, check the reported operating system, virtualization, disk or connection requirement before retrying with a valid join command.

See [infrastructure](https://docs.usekolaos.com/administration/infrastructure.md) for requirements and recovery, or [repositories](https://docs.usekolaos.com/administration/repositories.md) if GitHub access is missing.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.