Derek Coleman & Associates Inc logoDerek Coleman & Associates Inc

Home / Support / WireGuard on Ubuntu 24.04 LTS

WireGuard on Ubuntu 24.04 LTS — Support & Quick Start

WireGuard on Ubuntu 24.04 LTS — WireGuard is a fast, modern VPN protocol with state-of-the-art cryptography and a minimal attack surface. Published by Derek Coleman & Associates Inc on the Azure Marketplace, deployed in your own Azure subscription.

Email support Product page Azure Marketplace listing

At a glance

Application ports51820/udp (VPN)
Admin credential filesudo cat /etc/wireguard/wg0.conf # server config (private key, 10.8.0.1/24); no peers are pre-configured
Sign in asno login — WireGuard authenticates peers by key pair
Service(s)wg-quick@wg0
Configuration/etc/wireguard/wg0.conf (root-only); server public key: sudo wg show wg0 public-key
Logssudo wg show; journalctl -u wg-quick@wg0
VersionWireGuard (Ubuntu 24.04 package 1.0.20210914)
PlatformUbuntu 24.04 LTS

Quick start

  1. Deploy from the Azure Marketplace (Get It Now → Create), choosing your SSH key at the Administration step.
  2. Allow inbound SSH (22) for yourself plus the application port(s): 51820/udp (VPN) — restrict to your own IP where possible. The in-image firewall already allows them; only the Network Security Group (NSG) keeps them closed.
  3. Add a peer with `wg set` and `wg-quick save` (see First login below), then configure the client with the server's public key and endpoint.
  4. Enable forwarding/NAT rules for the subnets you want to reach through the tunnel (sysctl is pre-set in /etc/sysctl.d/99-wireguard.conf).

First login / credentials

This image generates its admin credential on the VM at first boot — nothing is pre-set. SSH into the VM with the username + key you chose at deploy, then print the generated credential:

ssh <your-username>@<VM-IP>
sudo cat /etc/wireguard/wg0.conf  # server config (private key, 10.8.0.1/24); no peers are pre-configured

Sign in as no login — WireGuard authenticates peers by key pair.

  1. No password exists. The server generated its own key pair and interface wg0 (10.8.0.1/24) at first boot; `sudo wg show` prints the public key.
  2. Add a peer on the server: wg genkey | tee /tmp/peer.key | wg pubkey > /tmp/peer.pub; sudo wg set wg0 peer $(cat /tmp/peer.pub) allowed-ips 10.8.0.2/32; sudo wg-quick save wg0.
  3. On the client, create a config with PrivateKey=<peer.key>, Address=10.8.0.2/32, and a [Peer] block with the server public key and Endpoint=<VM-IP>:51820, then bring the tunnel up.

There is no credential file to read — this image generates the server key pair only. Peer configs are created by you (see the steps above); keep /tmp/peer.key off the server once copied.

Still stuck?

Email support@dcassociatesgroup.com (response within 1 business day) or send a message via the contact form. Include the offer name, VM size, region, and any log output — sudo journalctl -u <service> -n 100 usually tells the story.