> For the complete documentation index, see [llms.txt](https://legacy.docs.synteq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacy.docs.synteq.com/gpu-vds/common-issues/unable-to-boot-the-vm-from-the-panel.md).

# Unable to boot the VM from the panel

What should you do in case your GPU VDS isn't booting

#### 1. Open a ticket <a href="#id-1.-open-a-ticket" id="id-1.-open-a-ticket"></a>

Start by going to our [client area](https://get.crunchbits.com/), and then on the left navigation bar, please select `Support` \[1] > `Open Ticket` \[2]

<figure><img src="https://2938941940-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F44w2dpnVMZwQFQvJQvmV%2Fuploads%2FEMFbWz0i9LoGjVHBWIKz%2Fimage.png?alt=media&amp;token=fbf6af33-2a8b-462c-a5e3-8d9915dd2881" alt=""><figcaption></figcaption></figure>

#### 2. Fill out the body of the ticket <a href="#id-2.-fill-out-the-body-of-the-ticket" id="id-2.-fill-out-the-body-of-the-ticket"></a>

Then, select the `Technical Support` department

<figure><img src="https://2938941940-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F44w2dpnVMZwQFQvJQvmV%2Fuploads%2FrcQBDVsL8ctiEoBpBLSA%2Fimage.png?alt=media&amp;token=aa7e28e1-f085-4482-9f78-a94496526bc1" alt=""><figcaption></figcaption></figure>

Afterward, please select the appropriate server in the `Realted Service` field, and fill out the `Subject`, and the `Message` part as per the table below:

<table data-header-hidden><thead><tr><th width="120.83984375"></th><th></th></tr></thead><tbody><tr><td>Subject [1]</td><td><pre><code>GPU VDS not booting
</code></pre></td></tr><tr><td>Message [2]</td><td><pre data-overflow="wrap"><code>Hello,​

My GPU VDS IPv4: \[xxx.xxx.xxx.xxx] isn't booting. Please take a look at it.

Thank you! </code></pre></td></tr></tbody></table>

{% hint style="info" %}
Make sure to replace the `xxx.xxx.xxx.xxx` variable with your VDS IPv4 address.
{% endhint %}

<figure><img src="https://2938941940-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F44w2dpnVMZwQFQvJQvmV%2Fuploads%2FREVWrIBYrNYfjxmpG2Dk%2FCleanShot%202025-10-31%20at%2017.07.29%402x.png?alt=media&amp;token=f4a3f03a-f4b4-431a-9c9a-4367bd4edbdd" alt=""><figcaption></figcaption></figure>

### 3. Submit the ticket

Then, please click the `Submit` button at the bottom, and wait until one of our team members to take a look at your GPU VDS.&#x20;

<figure><img src="https://2938941940-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F44w2dpnVMZwQFQvJQvmV%2Fuploads%2Ftqxj9LzA9TfhbodNpYsO%2FCleanShot%202025-10-31%20at%2017.10.18%402x.png?alt=media&amp;token=f00a790b-811f-48bc-b688-fc071caa8afc" alt=""><figcaption></figcaption></figure>

Afterward, wait for one of our team members to get back to you!&#x20;


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://legacy.docs.synteq.com/gpu-vds/common-issues/unable-to-boot-the-vm-from-the-panel.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.