---
id: "cloud.operar-pela-cli"
titulo: "Operate your Cloud"
resumo: "Follow, turn off and turn back on the Cloud: from the app on Windows, macOS and Linux with a screen, and from the CLI on a headless Linux server."
idioma: "en"
tipo: "referencia"
categoria: "cloud"
aplicavelDesde: "0.0.16"
capabilities: ["cloud.cli"]
estadoEditorial: "aprovado"
nivelEvidencia: "artefato-distribuido"
refFonte: "e593bd0591d172fd8fb2c40f2c38f5bb52980eb3"
revisaoFonte: "2026-10-04"
revisor: "mantenedor (autorizou a publicação, 2026-10-04)"
rota: "/docs/en/cloud/operar-pela-cli/"
fonte: "pt-br/cloud/operar-pela-cli.md"
caminhoPublico: "docs/publica/en/cloud/operar-pela-cli.md"
hashFonte: "sha256:e4a9aab2ebd93617db755991e04e0824ac176d18cc6f7a1d664c9a6d3d5b2599"
hashDestaPagina: "sha256:7daa9f69256bbedf63e3e44bd031c8a7ffb05cbc5bc4a3a642ffacd838ce3f94"
traducaoAssistidaPorIA: true
traducaoDesatualizada: false
corpoRetido: false
---
<!-- traducao-assistida-por-ia: idioma=EN fonte=pt-br/cloud/operar-pela-cli.md fonteHash=sha256:e4a9aab2ebd93617db755991e04e0824ac176d18cc6f7a1d664c9a6d3d5b2599 estado=atual -->

How you follow the Cloud depends on where it was turned on.

## On Windows, macOS and Linux with a screen

Everything is in **Settings → Elyra Cloud**, on the **Make this computer your Cloud** card:

| The card shows | What it means |
|---|---|
| **Starting…** | The Cloud is coming up and asking the account for the address. |
| **Up since** HH:MM | The Cloud is up. **Copy** copies the address; **Open** opens it in the browser. |
| **Reconnecting…** | The connection to the address dropped and is coming back on its own. |
| **Off** | The Cloud is not turned on on this computer. |

- **Turn it off**: click **Turn off** and confirm. Anyone connected through the address loses the
  connection.
- **Turn it back on**: click **Turn on** again.
- **Quitting Elyra** also turns the Cloud off. When you open the app again, check the card: if it says
  **Off**, click **Turn on**.

## On a headless Linux server

On the server, Elyra Cloud runs as the user service `elyra-cloud.service`. You follow it with the
`elyra cloud` CLI and with `systemctl`.

### `elyra cloud status`

```
elyra cloud status [--json]
```

Shows whether the server is ready. It exits with an error when it cannot reach it. If the server started on
a different port than the preferred one (6768 was busy), the command reports the real port.

### `elyra cloud stop`

```
elyra cloud stop [--json]
```

Stops Elyra Cloud on this computer. When it runs as a service, the command stops the service; the service
stays enabled and comes back when the machine reboots or when you start it again. When stopping, the
server also releases the address in the account. The command only says "stopped" after confirming the
stop, and exits with an error if it could not:

- `not running`: nothing to stop.
- `could not confirm`: check with `elyra cloud status` and run it again.

### `elyra cloud start`

```
elyra cloud start [--json]
```

Starts the server **in the foreground**, in the terminal (Ctrl+C or `elyra cloud stop` stop it). You usually
do not need it: the service already does this. If Cloud is already running, the command says so and does
not start another one.

### `elyra cloud desinstalar`

```
elyra cloud desinstalar [--sim] [--json]
```

Removes the Cloud installed on this machine. It is covered in [Turn off or uninstall](/docs/en/cloud/desinstalar/).

### The service through `systemctl`

```
systemctl --user status elyra-cloud.service     # state
systemctl --user restart elyra-cloud.service    # restart (generates a new code if not yet activated)
systemctl --user stop elyra-cloud.service       # stop
systemctl --user start elyra-cloud.service      # start
```

### See the log

```
journalctl --user -t elyra-cloud -f
```

Shows what the service writes, live: the activation code, the address and errors.

### The service comes back by itself

- After the **machine reboots**: the service is enabled, and the user's **linger** lets their systemd start
  without a login.
- After **a failure**: systemd tries again every 30 seconds. Errors that are pointless to repeat (such as a
  refused activation) stop the service, and the reason stays in the log.

## Next steps

- [Troubleshooting](/docs/en/cloud/resolver-problemas/)
- [Turn off or uninstall](/docs/en/cloud/desinstalar/)