vast-ai · jjziets · Jun 4, 2026 · Jun 15, 2026 · Jun 17, 2026 · Jun 17, 2026
diff --git a/docs.json b/docs.json
@@ -159,7 +159,7 @@
             "group": "Teams",
             "icon": "users",
             "pages": [
-              "guides/teams/overview",
+              "guides/teams/teams-overview",
               "guides/teams/managing-teams",
               "guides/teams/teams-roles",
               "guides/teams/legacy-teams"
@@ -588,26 +588,68 @@
         "tab": "Host",
         "groups": [
           {
-            "group": "Concepts",
-            "icon": "lightbulb",
+            "group": "Before You Host",
+            "icon": "compass",
             "pages": [
               "host/hosting-overview",
-              "host/understanding-verification",
-              "host/earning"
+              "host/supported-hardware",
+              "host/persona-decision-guide",
+              "host/earning",
+              "host/guide-to-taxes"
+            ]
+          },
+          {
+            "group": "Set Up",
+            "icon": "wrench",
+            "pages": [
+              "host/quickstart",
+              "host/account-hosting-agreement",
+              "host/hardware-prep",
+              "host/storage-setup",
+              "host/network-ports",
+              "host/installing-host-software",
+              "host/headless-install",
+              "host/vms"
             ]
           },
           {
-            "group": "Guides",
-            "icon": "warehouse",
+            "group": "Verify & List",
+            "icon": "badge-check",
             "pages": [
               "host/optimization-guide",
               "host/verification-stages",
+              "host/understanding-verification",
               "host/how-to-self-test",
               "host/market-metrics",
+              "host/self-test-reference",
+              "host/pricing-your-listing",
+              "host/not-in-search"
+            ]
+          },
+          {
+            "group": "Operate",
+            "icon": "gauge",
+            "pages": [
+              "host/first-24-hours",
+              "host/reliability-uptime",
+              "host/maintenance-windows",
+              "host/removing-recreating-machines",
+              "host/fleet-operations",
+              "host/common-errors-diagnostics",
+              "host/machine-errors",
               "host/datacenter-status",
               "host/payment",
-              "host/guide-to-taxes",
-              "host/vms"
+              "host/workload-policy"
+            ]
+          },
+          {
+            "group": "Reference",
+            "icon": "book-open",
+            "pages": [
+              "host/common-host-questions",
+              "host/glossary",
+              "host/hosting-agreement",
+              "host/community"
             ]
           },
           {
@@ -808,7 +850,7 @@
     "links": [
       {
         "label": "FAQ",
-        "href": "/guides/reference/faq"
+        "href": "https://docs.vast.ai/guides/reference/faq"
       },
       {
         "label": "Discord",

diff --git a/host/account-hosting-agreement.mdx b/host/account-hosting-agreement.mdx
@@ -0,0 +1,50 @@
+---
+title: "Account & Hosting Agreement"
+sidebarTitle: "Account & Agreement"
+description: "Host account conversion and agreement flow."
+"canonical": "/host/account-hosting-agreement"
+personas:
+  - pro-operator
+  - headless-operator
+  - business-owner
+  - hobbyist
+---
+
+<div className="persona-chips"><span className="persona-chip">All host personas</span></div>
+
+Use this page when a host account, hosting agreement, or Machines tab is not behaving as expected.
+
+<a id="separate-host-account" />
+## Do I need a separate host account?
+
+Yes. Use a dedicated account for hosting. Do not use the same account for both client rentals and host operations, because that setup is unsupported and can cause account and machine-management issues.
+
+## How to accept the hosting agreement
+
+Once your host account is created, open the [host setup page](https://cloud.vast.ai/host/setup/). There is a link in the first paragraph to the hosting agreement. Read through the agreement. Once you accept, your account is converted to a hosting account, and a Machines link appears in the navigation. Your account can now list machines that are running the daemon software.
+
+The setup page is the canonical place for the current agreement link and generated install command. Do not rely on copied buttons, screenshots, or old setup instructions.
+
+<a id="host-features-tab" />
+## What must happen before I can see host features or the Machines tab?
+
+Your account must be enabled for hosting and the hosting agreement must be accepted. After the account is converted to a host account, the Machines navigation and other host features should become available.
+
+If the account still behaves like a client account, confirm that you are signed into the intended host account and that the agreement flow completed.
+
+<a id="agreement-stuck" />
+## What if I accepted the agreement but still see a client account?
+
+Confirm that you are signed into the correct dedicated host account, then refresh or sign out and back in. If the Machines tab is still missing, treat it as an account-state issue rather than a Linux install issue. Contact Vast support with the host account email and screenshots or error messages from the setup flow.
+
+## Stale or deprecated setup links
+
+Copy the install command only from the official setup page while signed into the host account. Commands from old notes, screenshots, third-party guides, or another account can contain expired or account-specific material. See [Installing Host Software](/host/installing-host-software#install-command).
+
+## Related pages
+
+| Topic | Read next |
+| --- | --- |
+| First-time setup path | [Hosting Quickstart](/host/quickstart) |
+| Installing the host software | [Installing Host Software](/host/installing-host-software) |
+| Agreement reference | [Hosting Agreement](/host/hosting-agreement) |
diff --git a/host/common-errors-diagnostics.mdx b/host/common-errors-diagnostics.mdx
@@ -0,0 +1,207 @@
+---
+title: "Host Diagnostics"
+sidebarTitle: "Diagnostics"
+description: "Host log collection and diagnostic evidence paths."
+"canonical": "/host/common-errors-diagnostics"
+personas:
+  - pro-operator
+  - headless-operator
+---
+
+<div className="persona-chips"><span className="persona-chip">Pro Operator</span><span className="persona-chip">Headless / DC</span></div>
+
+Use this page to collect logs and host-side evidence. For exact Machines-page error strings and what they usually mean, start with [Machine Error Reference](/host/machine-errors).
+
+## Where To Start
+
+| Situation | Start here |
+| --- | --- |
+| Machines page shows a red error, `vericode=8`, or a host-facing runtime message | [Machine Error Reference](/host/machine-errors) |
+| Self-test failed and you need a support bundle | [Logs and support bundles](#logs) |
+| You need host daemon, service, GPU, kernel, storage, or port evidence | Use the diagnostic commands on this page |
+| Port reachability is the main issue | [Network & Ports](/host/network-ports) |
+| Renter reported a machine issue | [Workload Policy: Renter Reports And Host Logs](/host/workload-policy#renter-reports-and-host-logs) |
+
+<a id="logs" />
+## Logs And Support Bundles
+
+Installer logs are written to `vast_host_install.log` in the directory where you launched the installer, not under `/var/lib/vastai_kaalia`.
+
+```bash
+cat vast_host_install.log
+```
+
+If the installer created a compressed log archive:
+
+```bash
+tar -xzvf vastai_install_logs.tar.gz
+cat vast_host_install.log
+```
+
+The host daemon log is:
+
+```bash
+sudo tail -n 100 /var/lib/vastai_kaalia/kaalia.log
+```
+
+For self-test failures, the CLI can create a diagnostic bundle. The normal command is:
+
+```bash
+vastai self-test machine <machine_id>
+```
+
+Failure bundles are saved by default under:
+
+```text
+/tmp/vast_selftest_<machine_id>_<timestamp>.tar.gz
+```
+
+You can override the output directory:
+
+```bash
+vastai self-test machine <machine_id> \
+  --support-bundle-dir /path/to/output
+```
+
+Bundles can include:
+
+- `self-test-output.log`
+- `self-test-result.json`
+- `manifest.json`
+- `collection-errors.json`
+- `instance/show-instance.json`
+- `instance/container.log`
+- `instance/daemon.log`
+
+<a id="host-service-snapshot" />
+## Host Service Snapshot
+
+For a quick SSH check, collect service state, recent service logs, daemon logs, and the configured host port range:
+
+```bash
+systemctl is-active vastai.service vast_metrics.service docker nvidia-persistenced.service
+sudo journalctl -u vastai.service -n 80 --no-pager
+sudo journalctl -u vast_metrics.service -n 80 --no-pager
+sudo tail -n 100 /var/lib/vastai_kaalia/kaalia.log
+sudo cat /var/lib/vastai_kaalia/host_port_range
+```
+
+Services should be `active`, logs should not show restart loops or repeated fatal errors, and the configured port range should match the forwarded ports.
+
+<a id="gpu-kernel-logs" />
+<a id="gpu-pcie-issue" />
+<a id="nvidia-smi-fails" />
+<a id="nvml-mismatch" />
+<a id="gpu-falls-off-bus" />
+<a id="bad-bandwidthtest2" />
+<a id="failed-cdi" />
+## GPU And Kernel Diagnostics
+
+Use these commands to collect GPU, PCIe, AER, Xid, driver, and Docker GPU-injection evidence after an exact error has pointed you toward GPU or runtime health. For error meanings and first-response guidance, use [Machine Error Reference](/host/machine-errors).
+
+- **NVRM**: NVIDIA kernel driver messages.
+- **Xid**: NVIDIA GPU fault, reset, or error codes.
+- **PCIe**: the bus/link between the GPU, motherboard, and CPU.
+- **AER**: PCIe Advanced Error Reporting messages. Repeated AER messages can point to risers, slots, power, BIOS lane settings, cabling, motherboard, or GPU hardware issues.
+
+Check the current boot:
+
+```bash
+sudo journalctl -k -b --no-pager | grep -Ei 'NVRM|Xid|AER|PCIe|fallen|GPU has fallen'
+sudo dmesg -T | grep -Ei 'NVRM|Xid|AER|PCIe|fallen|GPU has fallen'
+```
+
+Search kernel and syslog history for AER/PCIe evidence:
+
+```bash
+sudo journalctl -k -b --no-pager | grep -Ei 'AER|PCIe Bus Error|pcieport|NVRM|Xid'
+sudo journalctl -k -b -1 --no-pager | grep -Ei 'AER|PCIe Bus Error|pcieport|NVRM|Xid'
+sudo dmesg -T | grep -Ei 'AER|PCIe Bus Error|pcieport|NVRM|Xid'
+sudo grep -Ei 'AER|PCIe Bus Error|pcieport|NVRM|Xid' /var/log/syslog /var/log/syslog.1 /var/log/kern.log /var/log/kern.log.1 2>/dev/null
+sudo zgrep -Ei 'AER|PCIe Bus Error|pcieport|NVRM|Xid' /var/log/syslog.*.gz /var/log/kern.log.*.gz 2>/dev/null
+```
+
+While reproducing under load, watch live kernel messages in another SSH session:
+
+```bash
+sudo journalctl -kf | grep --line-buffered -Ei 'AER|PCIe Bus Error|pcieport|NVRM|Xid'
+```
+
+Confirm host GPU visibility and Docker GPU injection:
+
+```bash
+nvidia-smi -L
+sudo docker run --rm --gpus all nvidia/cuda:12.2.0-base-ubuntu22.04 nvidia-smi -L
+```
+
+If the machine is idle and not rented, you can also run a short load test with a GPU burn image you trust:
+
+```bash
+sudo docker run --rm --gpus all oguzpastirmaci/gpu-burn 60
+```
+
+Correlate timestamps with self-test runs, rentals, `gpu-burn`, or other load tests. Repeated messages during load are much more concerning than a small number of corrected messages during boot.
+
+<a id="red-error" />
+<a id="port-issue" />
+<a id="docker-cache" />
+## Machine Error Lookup
+
+Use the Machine Error Reference for exact message meanings, likely causes, and next checks:
+
+| Message or symptom | Canonical reference |
+| --- | --- |
+| Red machine error, unhealthy, or de-verified machine | [Generic red machine error](/host/machine-errors#generic-red-machine-error) |
+| `Port issue` or `Port Networking Issues` | [Port Networking Issues](/host/machine-errors#port-networking-issues) |
+| TCP works but UDP fails | [TCP works but UDP fails](/host/machine-errors#tcp-works-but-udp-fails) |
+| `GPU PCIE issue`, AER, PCIe, Xid 79, or fallen off bus | [GPU PCIe Issue](/host/machine-errors#gpu-pcie-issue) |
+| `failed to inject CDI devices` or `unresolvable CDI devices` | [CDI Device Injection](/host/machine-errors#cdi-device-injection) |
+| `bad bandwidthtest2` | [`bad bandwidthtest2`](/host/machine-errors#bad-bandwidthtest2) |
+| `nvidia-smi` fails, NVML mismatch, or GPU disappears | [GPU Missing Or Unhealthy](/host/machine-errors#gpu-missing-or-unhealthy) |
+| Full client storage, `no space left on device`, or missing expected disk space | [Full Client Storage](/host/machine-errors#full-client-storage) |
+
+## Storage And Port Evidence
+
+For storage or port reports, collect the host-side facts before changing machine state:
+
+```bash
+sudo cat /var/lib/vastai_kaalia/host_port_range
+df -h /var/lib/docker
+sudo docker system df
+findmnt /var/lib/docker -no SOURCE,FSTYPE,OPTIONS
+```
+
+For networking cases, also capture the configured router, firewall, datacenter ACL, or provider forwarding state. For the full network checklist, see [Network & Ports](/host/network-ports). For storage meanings and cleanup guidance, see [Machine Error Reference: Full Client Storage](/host/machine-errors#full-client-storage).
+
+<a id="collect-logs" />
+## Before Asking For Help
+
+Include:
+
+- Account context and exact command.
+- The affected machine record in the console, relevant offer/contract context if support asks, and whether the account is the host account.
+- Exact timestamps with timezone.
+- Exact error strings, screenshots, or CLI output.
+- What changed recently: reboot, driver, kernel, Docker, BIOS, storage, router, or ISP.
+- Host OS, GPU model/count, NVIDIA driver version, and Docker storage mount output.
+- Tested external IP and port for networking issues.
+- Self-test support bundle when available.
+- Installer log, daemon log, and relevant kernel log excerpts.
+
+Review bundles before sharing them. Share sensitive machine/account details only in the appropriate support channel.
+
+<a id="escalate-support" />
+## Escalate To Vast Support
+
+Escalate account conversion, hosting agreement, payout, API permission, backend machine record, ghost machine, suspected backend bug, or platform-state mismatch issues.
+
+Local Ubuntu, Docker, GPU driver, hardware, power, thermals, and consumer networking are primarily host responsibilities. Vast hosting requires direct public inbound TCP/UDP reachability; CGNAT or double NAT without a real public forwarding path is not a supported hosting network setup.
+
+## Related Pages
+
+| Topic | Read next |
+| --- | --- |
+| Install failures | [Installing Host Software](/host/installing-host-software#install-failures) |
+| Machine error strings | [Machine Error Reference](/host/machine-errors) |
+| Self-test errors | [Self-Test Reference](/host/self-test-reference) |
+| Connectivity | [Network & Ports](/host/network-ports) |