# Adding a location and getting a Gateway token

## Adding a location in Defguard Core

{% hint style="warning" %}
Please remember that **one gateway corresponds to one VPN location.**

You can also deploy multiple gateways for one location for High Availability.
{% endhint %}

Go to the address you set on `DEFGUARD_URL` with your browser and sign in using the credentials you set up during Core deployment.

Go to the *VPN Overview* module from the main menu and click the *Edit Locations settings*.

<figure><img src="/files/GVRrU1cGqDGjRXoFLeQe" alt=""><figcaption><p>Adding a new location</p></figcaption></figure>

Then click the *Add new location tab*.

<figure><img src="/files/UcOPsdzopQ5Nxv7HXmg3" alt="Adding a new location"><figcaption><p>Adding a new location</p></figcaption></figure>

Depending on what is more convenient for you, choose configuration from Wireguard file or do it manually.

<figure><img src="/files/o7BxhbRHQYG5OFnp7ctB" alt=""><figcaption><p>Location wizard</p></figcaption></figure>

<figure><img src="/files/xIUoiRyZ5bwOieiIA4Lk" alt=""><figcaption><p>Location configuration</p></figcaption></figure>

After saving configuration for location you should be redirect to Location overview page, where at the top right corner is `Edit Locations Settings` button, click on it.

<figure><img src="/files/N1e8bxxHY2jY9Rw6Fg1L" alt=""><figcaption><p>Manual configuration</p></figcaption></figure>

In `Gateway server setup` copy two variables: `DEFGUARD_TOKEN` and `DEFGUARD_GRPC_URL`

<figure><img src="/files/FgxB23PoFItwymQj1Nf2" alt=""><figcaption><p>Gateway server setup</p></figcaption></figure>

Also, if core has a custom SSL CA to secure gRPC communication, [you need the CA certificate (more here).](/1.6/deployment-strategies/grpc-ssl-communication.md#custom-ssl-ca-and-certificates)

## Deploy the Gateway service

Proceed with deploying your Gateway service using the selected [deployment strategy](/1.6/deployment-strategies/setting-up-your-instance.md#choose-your-deployment-strategy):

* [package based](/1.6/deployment-strategies/standalone-package-based-installation.md#gateway-1)
* [Docker Compose](/1.6/deployment-strategies/docker-compose.md#deploying-gateway-service)
* [Kubernetes](/1.6/deployment-strategies/kubernetes.md#vpn-gateway-service)
* [Terraform](/1.6/deployment-strategies/terraform.md#gateway-module)
* [AMIs and AWS CloudFormation](/1.6/deployment-strategies/amis-and-aws-cloudformation.md#gateway-instance)

You can also check our guides on running Gateway on [OPNsense firewall](/1.6/deployment-strategies/running-gateway-on-opnsense-firewall.md) or [MikroTik router](/1.6/deployment-strategies/running-gateway-on-mikrotik-routers.md).

If everything went well, Defguard Gateway should be connected to Defguard Core and you can start [adding new devices to your network](/1.6/features/network-devices.md#adding-a-new-network-device).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.defguard.net/1.6/deployment-strategies/gateway.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.