It’s not the easiest to self host, as you need to know how to build docker images etc, since none is provided, but it’s more or less a splitwise substitute straight up
Caveats: its completely auth-less, so easy for people to cheat if that would be an issue for some reason. But you also dont have to force anyone to create an account
Not yelling, but pointing out, to people who also dont math, that if we assume $10 per 10k emails (or $1 per 1k, for simpler math), that’d be $84 for 84000 emails in a month, so you need to add another 0 to the figure (ie 840k emails in a month)
I’ve mainly gotten false positives, myself. When I’ve added another subdomain or something and the certificate gets set up differently, so then you get 2-3 emails saying domain X will expire, but if you connect to the url you see it has 80+ days left.
Setting up your own monitoring solution is probably long overdue for myself, and it’s nice I’m getting forced to do it, in a way
I set up uptime kuma to also monitor certs this week when I got the reminder email about them stopping the email warnings, been using it for some time for uptime monitoring (mostly to see if some auto docker image update screws up my services) and the notification parts has worked nicely for that, so I’m also assuming it will work nicely for the certificates
Your files are now being placed in /opt/wireguard-server/config, not in the folder you have the docker-compose file, can you see them there with ls?
If you want thee files to be created in the directory where your compose file is you should change the path in the volume like so (notice the ./ on the left side of the colon):
- ./config:/config
Volume paths are specified with local-path:container-path, so changing the part before the colon specifies where your files are, and changing the part after the colon specifies where the container sees the files
Hope this makes sense, but I just woke up, so it might not
Still no idea what this app/tool does without clicking the link