> 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/client/wireguard.md).

# WireGuard Client

Configure WireGuard client

For clients to use [**WireGuard**](https://www.wireguard.com/) it must first be enabled and configured on the server. Once the server has [**WireGuard**](https://www.wireguard.com/) configured an *OpenVPN* and *WireGuard* button will be shown in the client to allow selecting a protocol when connecting. The server must allow the client to access the HTTPS port to allow [**WireGuard**](https://www.wireguard.com/) connections to be authenticated.

After  [**WireGuard**](https://www.wireguard.com/) is enabled on the server the client configuration must be updated. If the server has a subscription the configuration sync feature will automatically update the configuration on the connection. Otherwise the profile will need to be reimported into the client.

### Linux Client

[**WireGuard**](https://www.wireguard.com/install/) must be separately installed on the client. Below is instructions for Fedora.

```shell
sudo dnf install wireguard-tools
```

The client will determine if WireGuard is installed by checking for the exec `wg` and `wg-quick` in the `$PATH`.

### Windows Client

The Windows client comes bundled with [**WireGuard**](https://www.wireguard.com/install/) and requires no changes on the client.

### macOS Client

The macOS client comes bundled with [**WireGuard**](https://www.wireguard.com/install/) and requires no changes on the client.


---

# 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/client/wireguard.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.