Cloud phone setup for beginners

Before you start: prepare both roles and the connection details

The management computer needs the Windows 64-bit client. The runtime node needs Ubuntu 24.04 amd64 and an SSH port reachable from the management computer. Prepare the node IP, SSH port, account, and password.

For a local node, the management computer should be able to reach its LAN address directly. If you require access across networks, prepare a secure network design first rather than exposing weak SSH credentials to the public internet.

• A Windows 64-bit management computer that can run the client.
• An Ubuntu 24.04 amd64 node with enough memory and data-disk space.
• Node IP, SSH port, SSH account, and password.
• A stable network; prefer a LAN path when both devices are local.
• A verified backup of important data before reinstalling an idle computer.

Complete one-click deployment from the client

1. 01

   Download and sign in

   Install the Windows 64-bit client, create an account, and sign in. Server and cloud phone management are handled in the client.

2. 02

   Add the Ubuntu server

   Enter a server name and group, the node IP, SSH port, account, and password. Choose automatic, platform public, or desktop LAN connection according to your network.

3. 03

   Run the connection test first

   Confirm that the client reaches the node and validates SSH. The first connection asks you to confirm the host fingerprint; an unexpected fingerprint change is blocked until you verify why the server changed.

4. 04

   Start one-click deployment

   The client runs a read-only preflight for Ubuntu, network, memory, storage, Docker, ADB, Binder, images, and node service conditions before preparing dependencies, storage, Docker, the runtime environment, and the Agent.

5. 05

   Watch stages and logs

   Keep the client open and review each stage. If preflight identifies an operating-system, space, or network problem, correct that specific condition before trying again.

6. 06

   Verify node health

   Run the health check after deployment and confirm that the node service, Docker, and runtime environment are available. Use the repair option only when the check identifies a supported repair.

7. 07

   Create and start a cloud phone

   Choose the server, group, system image, resources, and network mode. Start the new phone and use the remote entry to verify its display and basic controls.

What to check after creating the first phone

Validate one phone before increasing the count: check startup, remote display, input, network access, restart behavior, and node load. Add phones gradually only after the node remains stable.

The first use of a system image on a node requires download, verification, and preparation. Later phones using the same image on that node prefer the verified local cache.

• The server health check passes.
• The phone starts, stops, and restarts normally.
• Remote display and input work.
• The network mode matches the intended environment.
• The node retains safe memory, storage, and load headroom.

Troubleshoot deployment in this order

Read the failed stage and original log before repeating deployment. An unsupported system, unreachable SSH service, insufficient storage, and an unavailable package source require different fixes.

• Confirm the node is Ubuntu 24.04 amd64, not another Ubuntu release or a Windows desktop.
• Check the IP, SSH port, account, password, and host fingerprint from the management computer.
• Confirm at least 4 GB of node memory and 30 GB free in the node data location.
• Confirm access to required package sources or prepare the supported offline environment bundle.
• If deployment finishes but status is abnormal, run health check before repair or Agent update.