> For the complete documentation index, see [llms.txt](https://docs.antivpn.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.antivpn.io/getting-started/installation.md).

# Installation

Follow this step-by-step guide to install the AntiVPN.io plugin for Velocity and BungeeCord.

**Installation Steps**

1. **Download the Plugin:** Begin by downloading the plugin from [here](https://www.spigotmc.org/resources/111768/). Place the downloaded file into your server's plugins folder.
2. **Restart Your Server:** Restart your server to generate the plugin folder. You'll find it named either "serverantivpn" or "ServerAntiVPN."

You need to get the secret token from [dash.antivpn.io](https://antivpn.io). Here is a short video on how to get it.

{% embed url="<https://s.antivpn.io/tutorials/msedge_oWzkm6byZY.mp4>" %}
How to get the AntiVPN secret
{% endembed %}

Then, you can continue and use the following command at the console of your Proxy/Spigot server.

<pre class="language-log"><code class="lang-log"><a data-footnote-ref href="#user-content-fn-1">antivpn</a> <a data-footnote-ref href="#user-content-fn-2">&#x3C;your copied key here></a>
</code></pre>

Then, you're ready to use the AntiVPN in your server :)

[^1]: This is a command, and only works in the console of the Proxy/Spigot server.

[^2]: Here, you paste the code copied from the video below.


---

# 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://docs.antivpn.io/getting-started/installation.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.