Caddy 2 web server on Ubuntu 24.04 LTS by cloudimg. Pre configured with the cloudimg landing page on port 80, automatic Let's Encrypt HTTPS one Caddyfile edit away, and the admin API on loopback only. 24/7 expert support.
## Caddy 2 on Ubuntu 24.04 by cloudimg
Caddy 2 on Ubuntu 24.04 LTS (Noble Numbat), purpose built for Microsoft Azure and maintained by cloudimg. Caddy is the modern open source web server with automatic HTTPS via Let's Encrypt baked in — no Certbot dependency, no manual cert ceremony. Drop a domain into the Caddyfile, reload, and Caddy provisions a real cert on the first request and auto-renews it forever.
Why Choose cloudimg?
* 24/7 Expert Support with guaranteed 24 hour response for all requests and one hour average for critical issues. Contact support@cloudimg.co.uk
* Production Ready from Launch Pre configured, security patched, and validated before publication
* Azure Native Integration Built with Azure Linux Agent, cloud init, and Gen2 Hyper V support
* Automatic HTTPS Out Of The Box Caddy ships with Let's Encrypt integration as a first class feature. Edit one line in the Caddyfile, reload, and the cert is provisioned on the first request to your domain. Renewal runs silently in the background
What is Included
* Caddy 2.x server installed from the official Caddy team Cloudsmith APT repo
* Default Caddyfile at /etc/caddy/Caddyfile serving the cloudimg landing page on TCP 80; comment block at the top shows the customer how to swap in their domain to flip on automatic HTTPS
* Document root at /var/www/html
* Listeners: TCP 80 (HTTP), TCP 443 (HTTPS once configured), TCP 2019 (admin API — bound to 127.0.0.1 only)
* caddy.service systemd unit auto starting on boot, running as the caddy system user
* caddy-firstboot.service systemd oneshot that writes endpoint info on first customer boot
* caddy validate run as part of the build to confirm the shipped Caddyfile is syntactically valid
* Ubuntu 24.04 LTS base with latest security patches applied at build time
* Azure Linux Agent for seamless cloud integration and SSH key injection
Why Caddy vs Apache or Nginx
* Automatic HTTPS by default. No Certbot install, no apache plugin, no manual cert renewal cron. Caddy talks ACME natively.
* Single binary. No runtime dependency tree to manage; the official .deb installs one file.
* Modern config language. Caddyfile syntax is dramatically more readable than apache or nginx config for the common case (static site, reverse proxy, TLS termination).
* HTTP/2 + HTTP/3 + WebSocket out of the box. No extra modules to enable.
* Programmable runtime. The admin API (loopback only by default) lets you reload config, fetch metrics, and manage certs without restarting the server.
Use Cases
* Static site hosting with automatic HTTPS
* TLS terminating reverse proxy in front of internal application servers
* Local dev HTTPS (Caddy provisions self signed certs for *.localhost out of the box too)
* Drop in replacement for Apache or Nginx where automatic cert management is the highest priority
* Edge cache + reverse proxy for Grafana, Prometheus, Jenkins, and other internal tools that ship without TLS
Technical Specifications
* Operating System: Ubuntu 24.04 LTS (Noble Numbat)
* Caddy Version: 2.x (official Caddy Cloudsmith APT repo)
* Document Root: /var/www/html
* Config: /etc/caddy/Caddyfile
* Ports: 80 (HTTP), 443 (HTTPS once domain configured), 2019 (admin API on 127.0.0.1 only)
* Default User: azureuser (sudo enabled)
* Service Management: systemd (caddy.service, caddy-firstboot.service)
* Recommended Size: Standard_B2s
* VM Generation: Hyper V Gen2 with UEFI boot
Support
cloudimg provides 24/7/365 expert technical support. Contact support@cloudimg.co.uk or visit www.cloudimg.co.uk for the latest documentation and deployment guides.