> For the complete documentation index, see [llms.txt](https://hokas.gitbook.io/hokas-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hokas.gitbook.io/hokas-docs/hokas/how-do-i-renew-a-server.md).

# How do I renew a server?

**Free plan:**

1. Open the **Uptime / Renew** card on the server page.
2. Choose one of the two duration options. Durations vary by plan. If no custom duration is set, the options are 12 or 24 hours.
3. Complete the short link flow that opens. When you return, the duration is added to your server.
4. You can use each duration option **once** per renewal window. The default window is 24 hours. If an option is locked, the card shows when it becomes available.

**Paid plan:**

1. A renewal invoice is created automatically **7 days before** expiry and sent by email.
2. If the invoice remains unpaid, a reminder is sent **3 days before** expiry.
3. Pay the invoice from the **Invoices** page or through the email link.
4. Payment extends the same subscription and server. If the server has stopped, it restarts. You do not need a new server or new stock.
5. Note: Renewal invoices are not created for plans lasting 7 days or fewer.


---

# 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://hokas.gitbook.io/hokas-docs/hokas/how-do-i-renew-a-server.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.