Run
How the private node is reached after install
The public site sells and supports ZeroTrade, while the node itself stays private on the machine you control.
The public domain is the portal for buying, activation, docs, downloads, and updates.
The private node runtime lives on the machine you install: home PC, mini PC, VPS, or Ubuntu server.
The local panel stays bound to 127.0.0.1 by default instead of being exposed publicly.
Host Choice
Use the server host you own, not the public product domain
You can run the node behind a normal domain or a raw IP. The public site should explain the pattern plainly instead of making it look like everyone logs into the product domain itself.
If you already have a hostname for the box, a normal login path is ssh ubuntu@example.com.
If you are keeping it simple, logging in with the raw server IP is normal too: ssh ubuntu@serverIP.
A node subdomain is optional. It can be nice, but it is not required just to run the product.
Plain English
How the private browser panel actually reaches your home PC
The browser panel is not a public website. It lives on the server or PC where ZeroTrade is installed.
From your own computer, use ssh ubuntu@example.com or ssh ubuntu@serverIP to reach the machine that runs the node.
Once the SSH tunnel is open, http://127.0.0.1:8010/panel works in the browser on your home PC because SSH forwards your local port 8010 to the server's local panel port.
Typing http://127.0.0.1:8010/panel into your Windows browser before the SSH tunnel is active will not open the panel on your server. That is expected, not a broken install.
Windows Reality
What to expect on your home desktop before and after the tunnel
The confusing part is simple once it is stated plainly: the panel lives on the server, not inside your Windows browser by magic. The browser URL only becomes useful on your own PC after SSH creates the local bridge.
If your Windows machine has OpenSSH, open PowerShell and run ssh ubuntu@example.com or ssh ubuntu@serverIP, then open the tunnel in another terminal window.
Some operators prefer PuTTY. The idea is still the same: connect to the server over SSH and forward local port 8010 to 127.0.0.1:8010 on the server.
The public website and the private node can live on the same Ubuntu box. The website stays public while the node panel stays private behind SSH.
Access Path
The actual login and tunnel flow from your home PC
Connect to your own node host
Use the hostname or IP you control for the installed machine. The public ZeroTrade site is not the private node host.
ssh ubuntu@example.com or ssh ubuntu@serverIPOpen the terminal control center
Typing zerotrade on the machine shows the node summary, mode, services, and next actions.
zerotradeLet the node tell you the private path
The CLI prints the local panel URL plus the SSH tunnel pattern for your own browser.
zerotrade accessCreate the browser tunnel
Run this from your own computer to bring the private node panel into your browser safely.
ssh -L 8010:127.0.0.1:8010 ubuntu@example.comBrowser Panel
Open the panel on your home PC after the tunnel is active
Once the tunnel is open, load http://127.0.0.1:8010/panel in the browser on your home PC. SSH is forwarding that local browser port to the installed node on the server.
If you try that browser URL before the tunnel exists, it will not reach the panel on your server. That failure is normal and simply means the SSH bridge is not open yet.
Security Posture
Keep the public site and private runtime separate
The portal remains public for commerce and docs. The trading panel stays private on the server unless the operator deliberately chooses another access posture.
Useful Commands
The short command list you actually need after activation
Open the fastest read on node mode, heartbeat, strategy posture, and service health.
Print the local panel address and the SSH tunnel pattern without exposing a public dashboard.
Run the validation pass before making assumptions about readiness or environment drift.
Inspect paper execution, recent orders, and positions after the first draft or fill.
Operator Surfaces
Use the surface that fits what you are trying to do
The fastest first check is still the CLI. It gives mode, heartbeat, service posture, active strategies, and the exact local access path.
The browser surface exists for a calmer local overview once the SSH tunnel is open, not as a publicly exposed trading dashboard.
The public status surface is there for quick checks and mobile awareness, while the private node remains on the host you control.
First Session Checklist