Skip to content

First steps after install

Your backend is running and you can sign in. This guide takes you from an empty admin panel to the first device with a working VPN connection — the whole loop, once: create a customer, add a client, watch it connect.

Prerequisites

Steps

1. Create your first customer

Every client belongs to a customer — even if you only manage one organization, create it as a customer.

  1. Go to Admin → Customers → Add.
  2. Enter a name and a short client prefix (used in generated client names).
  3. Save. The defaults are fine for everything else — you can refine them any time later.

Pro If this customer should get the integrated WireGuard® server, set that up now — see Integrated WireGuard® server — or leave the server mode on External to upload configs manually like Community.

2. Install a client on your test device

Follow the matching guide: Windows · Linux · macOS · Mobile. Stop when the device shows up in the admin panel (mobile devices paired by QR skip straight to done).

3. Activate the client

  1. On the Overview page, click the Pending counter.
  2. Open the new client, assign it to your customer, and click Activate.

The device completes the activation on its own within a few minutes.

4. Give it a VPN profile

  • Community / external server mode: open the client's Details page and upload a WireGuard® .conf file for it. The client receives it on its next check-in.
  • Pro with integrated server Pro: nothing to do — the peer and profile were created automatically when you activated the client.

5. Connect

On the device, open the tray/menu/app and click Connect.

Verify it works

  1. The client's icon shows a green check — the tunnel is up and verified end-to-end.
  2. In the admin panel, the client's Details page shows it online and connected, and the connection appears in its history.

That's the full loop. From here, the Working with Valenius section explains every admin page in the same practical style — a good next read is Releases & auto-update, so your clients start updating themselves.

Common problems

The client never appears as pending. See the "Common problems" section of the matching client install guide — it's almost always a wrong or unreachable server address on the device.

The uploaded config never arrives on the device. The client fetches it on its next check-in — allow a few minutes. The client must be online (green) in the admin panel; if it isn't, revisit its install guide.

Connect works but there's no green check. The tunnel is up but couldn't be verified yet — this can lag a little behind the connect. If it persists, the profile's endpoint may be unreachable from the device's network (firewall blocking the WireGuard® UDP port is the usual cause).