OpenClaw WebChat Interaction

Access directly via VNC

Note that on the Jetson Nano motherboard, because OpenClaw runs in Docker, special handling is required when interacting with WebChat. For details, please see Part 2, Accessing from Other Hosts on the Local Network

First, connect to the host's terminal and enter the following command (for non-Docker versions, the gateway may start automatically at boot and does not need to be manually started; for Docker versions, it must be manually started):

xxxxxxxxxx
openclaw gateway

Next, we need to obtain the OpenClaw access token. In another terminal, enter the following command:

xxxxxxxxxx
openclaw dashboard

This command displays the token once, or you can find the ~/.openclaw/openclaw\.json file, where your token will be configured.

We connect to the system where the motherboard is located via VNC, then open a browser and enter the link provided in the dashboard.

Accessing from Other Hosts on the Local Network

OpenClaw version 3.8 on Jetson After deploying OpenClaw within a Docker container on a Nano, accessing the OpenClaw Control UI (web console) via a browser on the local Jetson will result in a 4008 access error. Therefore, you need to access it from a different computer.

If no other computer is available, you can use OpenClaw's TUI tool, which can be used via command line in the terminal. See the TUI usage section below for details.

Note: Please use the latest version of Edge or Chrome browser. Other browsers may encounter a 4008 error.

1. Modify the OpenClaw configuration file to allow other devices on the intranet to access OpenClaw

xxxxxxxxxx
openclaw config

Here, we select according to the following image (use the up and down arrow keys to select, and press Enter to confirm).

Except for the Token, which can be different from the one in the image, everything else must be the same. The key setting here is the "Gateway bind mode" option; we need to set it to "LAN" to allow other devices within our local network to access our OpenClaw instance.

Finally, select "Continue" to confirm, press Enter, and the configuration is complete!

2. Start the Gateway

Once the configuration is complete, let's start the OpenClaw Gateway service. Open a new terminal window and enter the following command:

xxxxxxxxxx
openclaw gateway

3. Retrieve the Access Token

The Token referred to here is the one generated during the configuration process we just completed. If you didn't write it down, you can use the following command:

xxxxxxxxxx
openclaw dashboard

This command will display the token for you. Alternatively, you can locate the ~/.openclaw/openclaw.json file, where your token is stored within the configuration.

4. Establish an SSH Tunnel and Access via PC

On a PC connected to the same local network, configure the connection environment to access the Jetson device. Open the Cmd terminal on your computer (using Windows as an example: press Win+R to launch the Run utility, type cmd, and then press Enter).

Enter the following command into the console:

xxxxxxxxxx
ssh -L 18789:127.0.0.1:18789 jetson@<jetson-ip-address>

Note: You must replace <jetson-ip-address> with the actual IP address of your Jetson board.

After pressing Enter, you will be prompted to enter the password (the default password is yahboom).

If this screen appears, it indicates that you have successfully connected to the Jetson.

Open a web browser on your PC and enter the full address—consisting of the IP and token—into the address bar (this is the address that was output by the openclaw onboard command earlier; e.g., https://127.0.0.1:18789/#token=xxxxxxxxxxxxx). If the interface shown below appears, it confirms that the deployment was successful!