Générateur de configuration simple basé sur le Web pour WireGuard
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Yannick Meunier 703c6d5154 màj 2 weeks ago
api màj 2 weeks ago
auth màj 2 weeks ago
cmd/wg-gen-web màj 2 weeks ago
core màj 2 weeks ago
model màj 2 weeks ago
storage màj 2 weeks ago
template màj 2 weeks ago
ui màj 2 weeks ago
util wg-gen-web 3 weeks ago
version màj 2 weeks ago
.env wg-gen-web 3 weeks ago
.gitignore wg-gen-web 3 weeks ago
Dockerfile wg-gen-web 3 weeks ago
LICENSE-WTFPL wg-gen-web 3 weeks ago
LISEZMOI.md màj 2 weeks ago
README.md wg-gen-web 3 weeks ago
go.mod wg-gen-web 3 weeks ago
wg-gen-web_cover.png wg-gen-web 3 weeks ago
wg-gen-web_screenshot.png wg-gen-web 3 weeks ago


Wg Gen Web

Simple Web based configuration generator for WireGuard

Simple Web based configuration generator for WireGuard.

pipeline status Go Report Card Gitlab pipeline status (self-hosted) Discord Build multi-arch Docker Images via buildx GitHub last commit Docker Pulls GitHub go.mod Go version GitHub code size in bytes

Why another one ?

All WireGuard UI implementations are trying to manage the service by applying configurations and creating network rules. This implementation only generates configuration and its up to you to create network rules and apply configuration to WireGuard. For example by monitoring generated directory with inotifywait.

The goal is to run Wg Gen Web in a container and WireGuard on host system.


  • Self-hosted and web based
  • Automatically select IP from the netowrk pool assigned to client
  • QR-Code for convenient mobile client configuration
  • Sent email to client with QR-code and client config
  • Enable / Disable client
  • Generation of wg0.conf after any modification
  • Dockerized
  • Pretty cool look




The easiest way to run Wg Gen Web is using the container image

docker run --rm -it -v /tmp/wireguard:/data -p 8080:8080 -e "WG_CONF_DIR=/data" vx3r/wg-gen-web:latest

Docker compose snippet

version: '3.6'
    image: vx3r/wg-gen-web:latest
    container_name: wg-gen-web
    restart: unless-stopped
      - 8080:8080
      - WG_CONF_DIR=/data
      - WG_INTERFACE_NAME=wg0.conf
      - SMTP_HOST=smtp.gmail.com
      - SMTP_PORT=587
      - SMTP_USERNAME=account@gmail.com
      - SMTP_PASSWORD="*************"
      - SMTP_FROM=Wg Gen Web <account@gmail.com>
      - /etc/wireguard:/data

Please note that mapping /etc/wireguard to /data inside the docker, will erase your host's current configuration. If needed, please make sure to backup your files from /etc/wireguard.

A workaround would be to change the WG_INTERFACE_NAME to something different, as it will create a new interface (wg-auto.conf for example), note that if you do so, you will have to adapt your daemon accordingly.

Directly without docker

Fill free to download latest artifacts from my GitLab server:

Put everything in one directory, create .env file with all configurations and run the backend.

Automatically apply changes to WireGuard

Using systemd

Using systemd.path monitor for directory changes see systemd doc

# /etc/systemd/system/wg-gen-web.path
Description=Watch /etc/wireguard for changes



This .path will activate unit file with the same name

# /etc/systemd/system/wg-gen-web.service
Description=Restart WireGuard

ExecStart=/usr/bin/systemctl restart wg-quick@wg0.service


Which will restart WireGuard service

Using inotifywait

For any other init system, create a daemon running this script

while inotifywait -e modify -e create /etc/wireguard; do
  wg-quick down wg0
  wg-quick up wg0

How to use with existing WireGuard configuration

After first run Wg Gen Web will create server.json in data directory with all server informations.

Feel free to modify this file in order to use your existing keys

What is out of scope

  • Generation or application of any iptables or nftables rules
  • Application of configuration to WireGuard by Wg Gen Web itself


  • Multi-user support behind Authelia (suggestions / thoughts are welcome)
  • Send configs by email to client

Need Help

  • Join us on Discord
  • Create an issue



From the top level directory run

$ go run main.go


Inside another terminal session navigate into the ui folder

$ cd ui

Install required dependencies

$ npm install

Set the base url for the api

$ export VUE_APP_API_BASE_URL=http://localhost:8080/api/v1.0

Start the development server. It will rebuild and reload the site once you make a change to the source code.

$ npm run serve

Now you can access the site from a webbrowser with the url http://localhost:8081.

Application stack