Failed running on Mac with M1 chip using DO droplet

PLAY [Wireguard server setup]*********************************************

TASK [Gathering Facts] ****************************************************
ok: [xxx.xx.xx.xx]

TASK [apt update] *********************************************************
ok: [xxx.xx.xx.xx]

TASK [Install wireguard] ***************************************************
changed: [xxx.xx.xx.xx]

TASK [wg0 down in case it's up] *******************************************
fatal: [xxx.xx.xx.xx]: FAILED! => {"changed": true, "cmd": "wg-quick down wg0", "delta": "0:00:00.017250", "end": "2022-01-14 05:39:29.010561", "msg": "non-zero return code", "rc": 1, "start": "2022-01-14 05:39:28.993311", "stderr": "wg-quick: `/etc/wireguard/wg0.conf' does not exist", "stderr_lines": ["wg-quick: `/etc/wireguard/wg0.conf' does not exist"], "stdout": "", "stdout_lines": []}
...ignoring

TASK [Create wireguard keys directory] ************************************
changed: [xxx.xx.xx.xx]

TASK [Create wg server and client keys] ***********************************
changed: [xxx.xx.xx.xx]

TASK [Get server key] *****************************************************
changed: [xxx.xx.xx.xx]

TASK [Create wg0.conf from template] ************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: If you are using a module and expect the file to exist on the remote, see the remote_src option
fatal: [xxx.xx.xx.xx]: FAILED! => {"changed": false, "msg": "Could not find or access 'wg0.conf.j2'\nSearched in:\n\t/poor-mans-vpn/templates/wg0.conf.j2\n\t/poor-mans-vpn/wg0.conf.j2\n\t/poor-mans-vpn/templates/wg0.conf.j2\n\t/poor-mans-vpn/wg0.conf.j2 on the Ansible Controller.\nIf you are using a module and expect the file to exist on the remote, see the remote_src option"}

PLAY RECAP **************************************************************
xxx.xx.xx.xx             : ok=7    changed=5    unreachable=0    failed=1    skipped=0    rescued=0    ignored=1   

Why are you not using Docker(-Compose) instead of installing and setting up Wireguard?

Setting up a VM with Ansible is really great 👍🏻 but why do you not use a docker container? This would make your playbook much easier (install docker and docker-compose, copy docker-compose.yml and execute docker-compose)

For example: https://github.com/linuxserver/docker-wireguard#usage

---
version: "2.1"
services:
  wireguard:
    image: lscr.io/linuxserver/wireguard
    container_name: wireguard
    cap_add:
      - NET_ADMIN
      - SYS_MODULE
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
      - SERVERURL=wireguard.domain.com #optional
      - SERVERPORT=51820 #optional
      - PEERS=1 #optional
      - PEERDNS=auto #optional
      - INTERNAL_SUBNET=10.13.13.0 #optional
      - ALLOWEDIPS=0.0.0.0/0 #optional
    volumes:
      - /path/to/appdata/config:/config
      - /lib/modules:/lib/modules
    ports:
      - 51820:51820/udp
    sysctls:
      - net.ipv4.conf.all.src_valid_mark=1
    restart: unless-stopped

You mention about keys being regenerated on every run - was this intentional? If you run the playbook again to reconfigure the system, is it desirable to regenerate keys?

Feel free to use the space to just say that you wanted it to do it this way :D

NOTE: I haven't tested this change as I don't have ansible, a system to test against/time right this second to spin up a docker container to run against, sorry :/

Also, this repo got posted on HN :) https://news.ycombinator.com/item?id=29913515