wireguard_webadmin

Deployment Guide

Mon, 01 Jan 0001 00:00:00 +0000

Prerequisites

A Linux server reachable from where you’ll manage it
Docker and Docker Compose installed
A domain name pointing to your server’s IP
Ports 80 and 443 open for Caddy; your WireGuard UDP port open (default 51820)

Caddy requires a valid DNS name — either internal or public — pointing to your server so it can obtain and renew SSL certificates automatically.

Deploy

mkdir wireguard_webadmin && cd wireguard_webadmin

wget -O docker-compose.yml \
 https://raw.githubusercontent.com/eduardogsilva/wireguard_webadmin/main/docker-compose-caddy.yml

Create a .env file in the same directory. Set SERVER_ADDRESS to your domain:

Get Involved

Mon, 01 Jan 0001 00:00:00 +0000

⭐

Star the repo

The simplest thing you can do. It helps the project get discovered by other sysadmins who are looking for exactly this.

Star on GitHub

🐛

Report bugs

Found something broken? Open an issue on GitHub. No template required — just describe what you saw and how to reproduce it.

Open an issue

🔧

Contribute code

Pull requests are welcome. For anything non-trivial, open an issue first so we can align before you invest time writing code. Good starting points: issues tagged good first issue, bug fixes with a clear reproduction case, and test coverage.

Zero Trust Application Gateway

Mon, 01 Jan 0001 00:00:00 +0000

What is Zero Trust here?

Traditional network security assumes that anything inside your network can be trusted. Zero Trust flips that model: no request is trusted by default, even if it comes from inside the VPN.

In wireguard_webadmin, the Zero Trust application gateway sits in front of your internal services. Every request must authenticate before reaching the app — the service itself never needs to be exposed directly.

How a request flows

1 Client reaches gateway

The public endpoint receives the request instead of the internal service.