> For the complete documentation index, see [llms.txt](https://docs.pritunl.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pritunl.com/kb/vpn/link/multiple-pritunl-servers.md).

# Multiple Pritunl Servers

Configure pritunl-link with multiple Pritunl servers

Starting with pritunl-link v1.0.2296.34 multiple hostnames can be provided in the link URI. When multiple hostnames are provided the link client will simultaneously send update requests to all the hosts and use the first response from an online host. Although links will currently remain online even if the Pritunl server cannot be reached due to the caching functionality this update provides additional reliability to keep links online even during significant outages.

To use this feature add additional hostsname to the URI separated by commas. This URI can then be added to Pritunl Link. To update an existing URI edit the configuration file in `/etc/pritunl_link.json` the configuration file will be automatically reloaded and this change will be applied immediately.

```
pritunl://ID:SECRET@pritunl0.domain.com,pritunl1.domain.com
```


---

# 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.pritunl.com/kb/vpn/link/multiple-pritunl-servers.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.