> For the complete documentation index, see [llms.txt](https://docs.scrt.network/secret-network-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scrt.network/secret-network-documentation/secretvm-confidential-virtual-machines/verifying-a-secretvm/secretvm-verify-sdk/troubleshooting.md).

# Troubleshooting

<details>

<summary><code>tls_cert_fetched: FAIL — Hostname/IP does not match certificate's altnames</code></summary>

SecretVM TLS certs are issued for a hostname, not the bare IP. Verify by hostname (e.g. `my-vm.vm.scrtlabs.com`), not the IP literal.

</details>

<details>

<summary><code>workload_binding_verified: FAIL</code></summary>

The VM is genuine, but the `docker-compose.yaml` you passed (or that the VM serves) does not match the launch measurement. Either you have the wrong compose file or the VM is not running what it advertises.

</details>

<details>

<summary><code>workload_binding_verified: FAIL — not_authentic</code></summary>

The MRTD/RTMR (TDX) or family\_id/image\_id (SEV-SNP) is not in the SecretVM registry. If you're on an older SDK release the auto-refresh will pull the latest registry from GitHub on the next miss; otherwise, upgrade with `npm i -g secretvm-verify@latest` or `pip install -U secretvm-verify`.

</details>

<details>

<summary><code>gpu_quote_verified: FAIL — NRAS timeout</code></summary>

NRAS occasionally rate-limits. Retry; if persistent, NRAS may be experiencing an incident.

</details>

<details>

<summary><code>AMD KDS 429 / unreachable</code></summary>

The default cache rescues you in this case. If you've enabled `--strict`, KDS unavailability surfaces as a verification failure on purpose — switch off strict mode or wait for KDS to recover.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.scrt.network/secret-network-documentation/secretvm-confidential-virtual-machines/verifying-a-secretvm/secretvm-verify-sdk/troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.