← Directory

caddy-ui-backend

Backend for caddy/ui, a web interface for managing Caddy servers, Caddyfiles, routes, certificates, logs, and metrics.

  • Infrastructure
  • Network Services
  • Tools & Utilities
Backend for caddy/ui, a web interface for managing Caddy servers, Caddyfiles, routes, certificates, logs, and metrics. Requires the caddy-ui-frontend container and an existing Caddy server. Select the same user-defined Docker bridge network for both UI containers and Caddy. You can use an existing custom bridge network: change Network Type in both templates to that network. If you need a new network, run "docker network create caddy-ui" in the Unraid terminal before installing and select "Custom: caddy-ui". Keep the container names caddy-ui-backend and caddy-ui-frontend. Enable "admin 0.0.0.0:2019" in Caddy's global configuration block; keep the admin API private. Start the backend before the frontend. Set External UI URL to the exact address used in your browser, including scheme and port, such as http://192.168.1.10:9877. Open the frontend to create the administrator, save the

Platform availability

Available on 1 of 9 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)

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.

61/100 Good

Maintained
98last commit 0 days ago
Popular
3345 GitHub stars
Easy to install
201 install platform, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
45
Open issues
30
Last commit
2026-10-22
Latest release
v3.7.0
License
MIT
Activity
rising

Checked today - source: GitHub (zackwag/caddy-ui)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked today - source: Docker Hub image tags and published docs

First-install notes

No first-install notes yet.

Alternatives (7)

  • Apache HTTP Server - Open-source HTTP server offering cross-platform support, modular architecture, secure configuration, robust content delivery, and extensive…
  • BunkerWeb - BunkerWeb is a self-hosted, open-source web application firewall and NGINX-based web server that protects services with secure-by-default s…
  • Caddy - Caddy is an extensible web server and reverse proxy that serves Transport Layer Security (TLS) by default, making it simple to secure and r…
  • Microsoft IIS - Internet Information Services (IIS) for Windows® Server is a flexible, secure and easy-to-manage Web server for hosting anything on the Web.
  • Træfik Proxy - The Cloud Native Application Proxy Simplify networking complexity while designing, deploying, and operating applications.
  • nginx - Nginx is an HTTP web server, reverse proxy, content cache, load balancer, TCP/UDP proxy, and mail proxy server.
  • tsdproxy - TSDProxy is a Tailscale proxy for Docker containers that automatically creates Tailscale machines for labeled containers, providing automat…

Checked today - source: AlternativeTo

Common questions

Does caddy-ui-backend include the web interface in the same container?

No, the web frontend is a separate Docker image that is built with React and served via Nginx.

Can I manage Caddy through the UI without editing config files?

Yes, the UI can manage proxy hosts, redirections, SSL certificates, and advanced routes without touching config files.

Does a Caddy UI have to modify the Caddyfile directly?

No, Caddy can be configured via its API, and the Caddyfile produces the JSON config that Caddy actually runs.

Why might Caddy fail to resolve internal services when used as a reverse proxy?

It can fail when the setup depends on the router's DNS host overrides to resolve internal service names to local IPs.

Answers sourced from github.com, github.com, www.reddit.com, www.redditmedia.com

Community

No community discussions collected yet.