mguinness/yarpwebauthn repository overview

Visit the source repo at https://github.com/mguinness/YarpWebAuthn⁠ for more information.

See the above repo on how to configure the proxy and registering security keys using customsettings.json.

Use the free Duck DNS⁠ as a dynamic DNS service providing you with a custom subdomain.

A docker volume⁠ is required for app settings and certificates from Let's Encrypt⁠.

The path for the certificates will be at config/live/example.duckdns.org once they are generated.

The following docker images will be used:

• maksimstojkovic/duckdns⁠ - periodically updates Duck DNS with current IP address
• maksimstojkovic/letsencrypt⁠ - generates free SSL certificates for your custom domain
• mguinness/yarpwebauthn⁠ - securely proxies your website(s) using YARP⁠ and WebAuthn⁠
• j796160836/simple-test-http⁠ - a simple test website run as http://demo/ inside docker compose

See below for an example docker compose⁠ configuration file. Replace with your custom subdomain and API token from Duck DNS where needed.

volumes:
  proxy-config:
services:
  ddns:
    image: docker.io/maksimstojkovic/duckdns:latest
    container_name: ddns
    environment:
      - DUCKDNS_DOMAIN=example.duckdns.org
      - DUCKDNS_TOKEN=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
      - DUCKDNS_DELAY=60
    restart: unless-stopped
  certs:
    image: docker.io/maksimstojkovic/letsencrypt:latest
    container_name: certs
    environment:
      - DUCKDNS_DOMAIN=example.duckdns.org
      - DUCKDNS_TOKEN=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
      - LETSENCRYPT_WILDCARD=true
    volumes:
      - proxy-config:/etc/letsencrypt
    restart: unless-stopped
  proxy:
    image: docker.io/mguinness/yarpwebauthn:latest
    container_name: proxy
    ports:
      - 8443:8443
    volumes:
      - proxy-config:/app/config
    restart: unless-stopped
  demo:
    image: docker.io/j796160836/simple-test-http:latest
    container_name: demo

Once running, the proxy will be available on TCP port 8443. Typically you would configure your home router to setup a port forward⁠ rule accepting TCP port 443 and forwarding to TCP port 8433 on the machine running the proxy. Then your website should be publicly (and securely) accessible at https://www.example.duckdns.org/⁠ (substituting example with the custom domain name that you selected).