Setting up site-to-site on UniFi USG

Note: If you are unsure whether site-to-site is the best solution for you, please take a look at our Remote Access article first. What is more, if your device/service supports SHA256 and DH group 14, it is recommended to use these settings instead.


Configuring the tunnel at the UniFi - USG Management Interface

1. Open the UniFi - USG management interface

2. In the left panel, select Networks, then select Create New Network:


3. Select Site to Site VPN > Manual IPsec and fill in with the following information:

  • Enable this Site-to-Site VPN
  • Remote Subnets: Enter the NordLayer dedicated server subnet (by default it is
  • Peer IP: Enter the public IP of your NordLayer dedicated server
  • Local WAN IP: Enter the public IP of the UniFi SCG
  • Pre-shared key: Enter the Shared Key you have generated (we will also need this value)


 4. In the Advanced Options fill in the following information:

  • Key Exchange Version: IKEv2
  • Encryption: AES-256
  • Hash: SHA256
  • DH Group: 14
  • PFS: Enable
  • Dynamic Routing: Disable



Configuring a firewall and static routing

It is necessary to add static routes from the NordLayer subnet ( to the local network and from the local network to the NordLayer subnet ( to the local network through the VPN tunnel gateway. Also, it is necessary to create firewall rules to allow this traffic.

1. Go to Routing & Firewall > Static Routes > Create New Route

  • Choose a name.
  • Enable the route.
  • Enter the NordLayer subnet (by default it is in Destination Network.


  • Make sure to choose the interface you created in the previous section

2. Create a firewall rule that allows traffic from the NordLayer subnet to the LAN Network



Ending note:

In order to finalize the site-to-site setup on our end, we will need these values:

  • Pre-shared key - you can generate it or we can provide it
  • Encryption  details (AES, SHA and DH group) - AES256, SHA256 and DH group 14 are recommended (also must support IKEv2)
  • Remote gateway/router public IP (must be reachable while connected to the dedicated server)
  • Remote subnet and mask (the subnet is used in your local network)

Lastly, it is important to know what device or cloud network is being used (Ubiquiti, Fortigate, AWS, Google Cloud, etc.)

You can provide all of these values to us securely via

In case you are experiencing different results, make sure that you have you carefully gone through all the steps. Having said that, in case the issue persists please feel free to contact our 24/7 customer support team.

Return to top