Docs
Connecting to your agent
Everything you need after your machine finishes provisioning. It usually takes about two minutes from payment to a working address.
Quick start
- Open your server page in the console and copy the Machine URL.
- Reveal and copy the login token on the same page.
- Open the URL in a browser and paste the token when the agent asks for it.
- Optional: add an SSH public key on the server page for shell access.
1 · Your machine address
Every machine gets its own HTTPS address on gridrocket.cloud, with a certificate issued automatically. You'll find it on the server page in your console as Machine URL. Open it in any browser — no VPN, no port forwarding.
2 · Your login token
The agent is protected by a gateway token that we generate and inject into the machine at launch. It is shown on the server page under PasClaw login token — reveal it, copy it, and paste it into the agent's login prompt the first time you connect.
The token is unique per machine and is regenerated every time you relaunch. Treat it like a password: anyone who has it can drive your agent.
3 · SSH access
You get root on the box. Use the root password on the server page, or paste an SSH public key into the SSH public key field — it is installed into ~/.ssh/authorized_keys on the next launch.
ssh root@<your-machine>.gridrocket.cloud
4 · Health, reboots and rebuilds
We probe your machine's address on a schedule and show recent uptime plus the last check on the server page. If the agent stops answering, you can Reboot machine for a clean restart, or Destroy machine and launch a fresh one — the server itself stays yours for the rest of the paid period.
Destroying a machine is irreversible: anything written to the machine's disk is gone. We ask you to type the confirmation word before doing it.
5 · Billing and the end of a period
You rent the server by the month. Cancel any time from the server page — it keeps running until the end of the paid period, then we tear the machine down and release the address. There is no long-term contract and no usage billing.
6 · Troubleshooting
The address doesn't answer
Provisioning may still be finishing — check the provisioning log on the server page. If the status is running and it still doesn't answer, use Reboot machine; if that doesn't help, destroy it and launch a fresh one.
The token is rejected
The token is regenerated on every relaunch, so an old copy will fail. Reveal and copy it again from the server page, and make sure no trailing space came along with it.
The browser warns about the certificate
The certificate is requested right after the machine boots and can take a minute to be issued. Wait a moment and reload — do not click through the warning.
SSH is refused
Use the root password shown on the server page, or paste an SSH public key into the SSH public key field — keys are installed on the next launch, not retroactively on a running machine.
The machine disappeared
Machines are torn down at the end of a cancelled billing period, and destroying a machine is irreversible. Launch a new one from the server page if the period is still active.
Still stuck?
Send us the server ID from your console and what you're seeing. We answer within one business day.
Contact support