Binhex-herdr-core

Binhex Herdr Core is a Caddy web server container with the DuckDNS DNS challenge plugin that automatically issues Let's Encrypt TLS certificates for DuckDNS…

  • AI
  • Tools & Utilities
Binhex Herdr Core is a Caddy web server container with the DuckDNS DNS challenge plugin that automatically issues Let's Encrypt TLS certificates for DuckDNS hostnames without exposing port 80, making it a useful home-network reverse proxy.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

42/100 Fair

Maintained
72last commit 3 days ago
Popular
00 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
0
Open issues
0
Last commit
2026-11-18
License
GPL-3.0
Activity
rising

Checked 2 days ago - source: GitHub (binhex/arch-herdr-core)

Resources & Compatibility

Requirements not published yet.

Checked 2 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Installation Deploy as a Docker container. It is available in the Unraid Community Application Store, and the container builds from the binhex/arch-herdr-core GitHub repository. source

Fetched yesterday - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Where do I put the Caddyfile for this container?

Place it at /config/caddy/Caddyfile. An example with reverse proxy settings is created there on first run.

Which ports should I map for a basic reverse proxy setup?

Map 8080 for HTTP and 8443 for HTTPS, and set http_port 8080 and https_port 8443 in the Caddyfile global block. The example also maps 2019.

How do I use DuckDNS for automatic TLS without opening port 80?

Set DUCKDNS_TOKEN and reference it in the Caddyfile as {env.DUCKDNS_TOKEN} inside the duckdns DNS challenge block. The image includes the DuckDNS plugin for Let's Encrypt certificate issuance and renewal.

Where are Let's Encrypt account data and certificates stored?

Caddy stores them under /config/caddy/data, inside the /config bind mount. If you have an existing deployment, add storage file_system /config/caddy/data to the global options block.

How can I install extra Arch packages on container startup?

Set ENABLE_STARTUP_SCRIPTS=yes and put scripts in /config/caddy-duckdns/scripts. Use STARTUP_SCRIPTS_MODE wait to run scripts sequentially or parallel to run them at the same time.

Answers sourced from github.com

Community

No community discussions collected yet.