easy-pwn
acme-dns-client
| easy-pwn | acme-dns-client | |
|---|---|---|
| 5 | 2 | |
| 7 | 98 | |
| - | - | |
| 0.0 | 0.0 | |
| about 2 years ago | 11 months ago | |
| Go | ||
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
easy-pwn
-
Beginner in need of advice guide regarding local home network idea
If you use docker, you can try my compose files. Comes with a Wireguard VPN server (with a web UI) connected to Pi Hole, connect to unbound DNS: https://github.com/rmayobre/easy-pwn
-
Reverse proxy for internally hosted services
You can try this docker stack to get your internal networking and Pi Hole DNS set up: https://github.com/rmayobre/easy-pwn
-
Expose services only via VPN
I have some services I keep behind a Wireguard VPN. I have a docker compose stack that pairs easy-wg (Wireguard with a web UI) with a self hosted DNS and Pi Hole for ad blocking. You can also use pi hole for local dns records to help point to other services and apps. https://github.com/rmayobre/easy-pwn
-
No idea what I'm missing
Try this: https://github.com/rmayobre/easy-pwn
-
Looking for automation of generic tasks
There is a stack "docker-compose-portainer.yml" that does the exact same thing, but adds portainer to the stack. Hopefully my documentation is still accurate: https://github.com/rmayobre/easy-pwn
acme-dns-client
-
Reverse proxy for internally hosted services
In case you're not already familiar with it: one thing I'd recommend is using https://github.com/joohoi/acme-dns to obtain the certificates. You basically just point the subdomain you need wildcard certs for at that DNS server (a one time thing, ie you don't have to do this every three months), and the related tool https://github.com/acme-dns/acme-dns-client can get the certificates in a nice, automated, way without you ever having to expose the private reverse proxy to the Internet.
-
My ISP blocks port 80?
I also have domains on google domains and I use https://github.com/joohoi/acme-dns api to renew all the certificates using the api including wildcard certificates. Just register a new account at https://auth.acme-dns.io/register and start using DNS api. https://github.com/acme-dns/acme-dns-client
What are some alternatives?
docker-traefik-cloudflare-companion - Automatically Create CNAME records for containers served by Traefik
acme-dns - Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely.
wirehole - WireHole is a combination of WireGuard, Pi-hole, and Unbound in a docker-compose project with the intent of enabling users to quickly and easily create a personally managed full or split-tunnel WireGuard VPN with ad blocking capabilities thanks to Pi-hole, and DNS caching, additional privacy options, and upstream providers via Unbound.
AdGuard-WireGuard-Unbound-Cloudflare - The ultimate self-hosted network security guide ─ Protection | Privacy | Performance for your network 24/7 Accessible anywhere [Moved to: https://github.com/trinib/AdGuard-WireGuard-Unbound-DNScrypt]
pi-hole_unbound_compose - pi-hole with unbound and prometheus exporter in docker compose
CasaOS-LinuxServer-AppStore - A CasaOS custom Appstore containing over 100+ LinuxServer.io images.