Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

WireGuard Server-to-Server VPN Between Two Unraid Servers (Only One Side Has Dynamic DNS)

Featured Replies

Hi everyone,

I'm trying to set up a WireGuard server-to-server VPN connection between two Unraid servers so that they can access each other and transfer data (SMB, NFS, rsync, etc.).

My setup is:

  • Server A

    • Has a Dynamic DNS hostname

    • UDP port 51820 is forwarded to the Unraid server

    • Acts as the main server

  • Server B

    • No Dynamic DNS hostname

    • No public static IP

    • Located at a different site

I'm using Unraid's built-in WireGuard VPN Manager and selecting "Server to Server Access" when creating the peer.

My confusion is that Unraid requires an Endpoint field when creating the peer on Server A. Since Server B does not have a public hostname or static IP, I'm not sure what should be entered there.

Questions:

  1. What is the recommended way to configure a site-to-site WireGuard tunnel when only one server has a Dynamic DNS hostname?

  2. Does Server A actually need an endpoint configured for Server B?

  3. Should Server B be configured as the only side that initiates the connection?

  4. Are there any example configurations for this scenario using Unraid's built-in WireGuard manager?

Any guidance or screenshots of a working configuration would be greatly appreciated.

Here are my current Configs:

  • Server A

Interface Name: PeerToPeer
PrivateKey: [InterfaceAPrivate]
PublicKey: [InterfaceAPublic]
Network: 10.100.100.0/24
Local tunnel address: 10.100.100.1
Local endpoint: [myEndpoint]:51282
Peer name: Server B
Peer type of access: Server to server access
Peer private key: [InterfaceBPrivate]
Peer public key: [InterfaceBPublic]
Peer tunnel address: 10.100.100.2
Peer endpoint: [Thats the Question]

  • Server B

    Interface Name: PeerToPeer
    PrivateKey: [InterfaceBPrivate]
    PublicKey: [InterfaceBPublic]
    Network: 10.100.100.0/24
    Local tunnel address: 10.100.100.2
    Local endpoint: [Thats the Question]
    Peer name: Server A
    Peer type of access: Server to server access
    Peer private key: [InterfaceAPrivate]
    Peer public key: [InterfaceAPublic]
    Peer tunnel address: 10.100.100.1
    Peer endpoint: [myEndpoint]:51282

Thanks!

Edited by sphairon

Solved by sphairon

  • Author
  • Solution

I found the Issue in my port forwarding.

Peer endpoint for Server A is just localhost (127.0.0.1).

Local Endpoint for Server B is empty

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.