duckdns
acme.sh
Our great sponsors
duckdns | acme.sh | |
---|---|---|
6 | 280 | |
35 | 36,504 | |
- | 2.5% | |
1.3 | 8.9 | |
12 months ago | 5 days ago | |
Go | Shell | |
- | GNU General Public License v3.0 only |
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.
duckdns
-
PSA: unless you are using wildcard certificates, all your subdomains get published in a list of issued Let's Encrypt certificates. You can see if your subdomains are published here: https://crt.sh/
(1) https://github.com/caddy-dns/duckdns
-
What are y’all using to set up a domain on your LAN so that your services are like `whatever.local/gitea` instead of `192.168.0.50:8080`. Pretty sure I need a reverse proxy but I’ve never set one up that wasn’t publicly available, so I’m not sure if a different set of rules apply.
My domain provider is not supported by Caddy, so I use duckdns.org for dynamic dns and dns challenge - it can be routed to my domain (see https://github.com/caddy-dns/duckdns). It might be possible to use duckdns.org directly instead of buying a domain, but the url will be xxx.duckdns.org or similar. (e.g. gitea-xyz.duckdns.org routed to 192.168.0.50)
-
Router ports open but reverse proxy not working (Docker, Caddy, DuckDNS)
Why are you using the email global directive for DuckDNS? Why not just use the DuckDNS addon (Github) module?
-
Let's Encrypt ACME DNS alias mode
Also known as "DNS challenge delegation".
I have this implemented (with help) for the libdns plugin for DuckDNS, which can be used with Caddy.
So basically, you can use a free https://www.duckdns.org/ domain to solve DNS challenges, for your domain which may be managed by any other DNS provider.
https://github.com/caddy-dns/duckdns#challenge-delegation
I do this with my domain I have registered with Google Domains, because they have no API at all right now.
-
Synching iOS Contact/Calander to Nextcloud 22.0 - Localhost - NO SSL?
- Using caddy reverse proxy + https://github.com/caddy-dns/duckdns
-
Caddy + Namecheap + DuckDNS configuration
But if you need wildcard certs, then using duckdns makes a whole lot of sense because namecheap's DNS API is some hot garbage (requires fetching the entire set of DNS records for the zone, making your change, then pushing back up the entire set, as XML). The alternative is to use DNS challenge delegation, which is quite easy to do with the duckdns plugin for Caddy https://github.com/caddy-dns/duckdns#challenge-delegation
acme.sh
-
Setting up a Homelab: Part 1 Proxmox and LetsEncrypt
A self-signed certificate was generated and used by Proxmox which will always generate a warning on the browser. I did not like seeing this when trying to work on my home lab. So, I started looking for ways to put a valid SSL certificate in Proxmox. During my research, I found that Proxmox could be made to integrate with acme.sh; a free SSL certificate generator powered by ACME(Let's Encrypt).
-
How to Build Email Server with Exim on Alma Linux 9
Next, we will install acme.sh, a command-line tool for managing SSL/TLS certificates. I prefer acme.sh over certbot, as it does not depend on the OS version. For more details about acme.sh, check its GitHub repo here.
-
Dehydrated: Letsencrypt/acme client implemented as a shell-script
A very relevant question. Acme.sh, a similar shell script ACME client, had a remote code execution problem last year.
https://github.com/acmesh-official/acme.sh/issues/4668
-
Ask HN: What is your experience with ZeroSSL?
As a result, any certificates issued (or renewed) after Feb 8th will not work on older Android devices (< 7.1.1), unless the ACME client has been configure to request an alternate certificate chain. The "alternate chain" workaround will also stop working on June 6th.
I need to support these older Android devices so I am looking for alternatives. I have seen ZeroSSL mentioned a few times; it is also the default CA for acme.sh (the ACME client I am using nowadays) [2]. They have a number of paid plans but ACME certificates are free [3].
I'll be testing this over the next few days, but I would also like to ask if people here have experience with ZeroSSL (good or bad :-). Any feedback would be helpful.
[1]: https://letsencrypt.org/2023/07/10/cross-sign-expiration.html
[2]: https://github.com/acmesh-official/acme.sh
[3]: https://zerossl.com/documentation/acme/
-
Why Certificate Lifecycle Automation Matters
Huh, the environment variable thing was specifically aimed at acme.sh which rather arbitrarily changed the config value from ACMEDNS_UPDATE_URL to ACMEDNS_BASE_URL, never acknowledged this in a changelog and then silently failed after an automatic upgrade as recommended by the default install:
https://github.com/acmesh-official/acme.sh/commit/2ce145f359...
It's also cleared out my .account.conf files when run on the suggested cron.
I've started using updown which also monitors my TLS certs simply because I no longer trust the process to work as documented.
-
The Bureau of Meteorology website does not support connections via HTTPS
It depends on your provider though. I can tell from experience that with OVH and their API, it's been easy to set up the automatic renewal via DNS verification. Apparently, the official client has support for the DNS API of 159 providers: https://github.com/acmesh-official/acme.sh/wiki/dnsapi
-
I made a tool for automatically updating the current and next (rollover) TLSA DNS records with acme.sh and the Cloudflare API
For the few people here that happen to run a self-hosted email server with acme.sh for TLS key/cert generation and Cloudflare for DNS management, I have made a tool that i personally use to get a perfect 100% score on Internet.nl's email test.
-
How to get LetsEncrypt certs from PfSense/ACME to other machines? (automated??)
All of this is to say it's a decent amount of work to save the hassle of deploying certbot or acme.sh on the remote machines, pick your poison.
-
Hosting at home & SSL
Here is a really solid guide for setting up the ACME DNS challenge with pretty much any DNS provider
-
This is Fine
People wonder why I like using the shell-based ACME client like dehydrated (or acme.sh):
* https://packages.debian.org/search?keywords=dehydrated
* https://github.com/acmesh-official/acme.sh
Versus the official client certbot:
* https://packages.debian.org/search?keywords=python3-certbot
A kludgy as very long shell scripts are (thought to be), I have a better chance of being able to go through all the code and understand it than a dozen(+) Python libraries.
What are some alternatives?
acme-dns - Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely.
letsencrypt - Certbot is EFF's tool to obtain certs from Let's Encrypt and (optionally) auto-enable HTTPS on your server. It can also act as a client for any other CA that uses the ACME protocol.
lexicon - Manipulate DNS records on various DNS providers in a standardized way.
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
lexicon - A fun react dictionary app to learn some new words!
dehydrated - letsencrypt/acme client implemented as a shell-script – just add water
CoreDNS - CoreDNS is a DNS server that chains plugins
lego - Let's Encrypt/ACME client and library written in Go
pterodactyl-installer - :bird: Unofficial installation scripts for Pterodactyl Panel
docker - ⛴ Docker image of Nextcloud
cfssl - CFSSL: Cloudflare's PKI and TLS toolkit