Nice night to have the old Caddy convertible out #Caddy

I have a domain at simply.com with a few services running on a server at home.

Previously I used Caddy with subdomains registered with my hosting provider's DNS panel, and ports 80 and 443 opened to the public internet. Anybody could access my services from the outside.

I've now changed to using WireGuard and a custom build of Caddy with a wildcard certificate for my domain. Pi-hole handles DNS for subdomains, e.g. cloud.example.com for Nextcloud.

I'm using podman system quadlets for Pi-hole and Caddy (both use privileged ports), and podman secrets for sensitive data.

In /etc/containers/systemd/caddy, I have 3 files:

Containerfile
--------------------
FROM docker.io/caddy:builder AS builder

RUN xcaddy build --with github.com/caddy-dns/simplydotcom

FROM docker.io/caddy:latest

COPY --from=builder /usr/bin/caddy /usr/bin/caddy
--------------------

caddy.build
------------------
[Build]
ImageTag=localhost/caddy
SetWorkingDirectory=unit
------------------

caddy.container
-------------------------
[Unit]
Description=Caddy container
After=network-online.target

[Container]
AutoUpdate=registry
ContainerName=caddy
Image=caddy.build
Secret=simply_account_name,type=env,target=SIMPLY_ACCOUNT_NAME
Secret=simply_api_key,type=env,target=SIMPLY_API_KEY
Volume=/srv/containers/caddy/conf:/etc/caddy:Z
Volume=/srv/containers/caddy/data:/data:Z
PublishPort=443:443

[Install]
WantedBy=default.target
-------------------------

The Caddyfile is stored in /srv/containers/caddy/conf/:

Caddyfile
---------------
*.example.com {
tls {
dns simplydotcom {env.SIMPLY_ACCOUNT_NAME} {env.SIMPLY_API_TOKEN}
}

@caddy host caddy.example.com
handle @caddy {
respond "Hello World!"
}
}
---------------

See Caddy documentation for more on wildcard certificates.

https://caddyserver.com/docs/caddyfile/patterns#wildcard-certificates

#selfhosting #homelab #podman #caddy

Caddy - The Ultimate Server with Automatic HTTPS

Caddy is a powerful, enterprise-ready, open source web server with automatic HTTPS written in Go

Caddy Web Server

Hey @homelab ,

has anyone managed to write a working config for running #Caddy with the caddy-security plugin and #OIDC?

I am struggling to make it work. Anyone mind sharing a working config?

(watch out to redact your secrets)

I’ve been playing around with a Rock Pi 4 Plus. Went with the default minimal Debian image, since fighting with U-boot wasn’t something I wanted to tackle yet 😛

Running Caddy on it and hosting https://caddy.ninja for testing purposes.

#sbc #caddy #selfHosting

Caddy Ninja

Setup an HTTPS-enabled webserver with Caddy on Alpine Linux

question for #server touchers: any opinion on #ferron as a remplacement for #caddy ?
#Caddy #Layer4 #Routing ? interesting .....

SearXNG su Linux: motore di ricerca self-hosted privato su VPS

https://www.risposteinformatiche.it/searxng-linux-motore-ricerca-self-hosted-vps/
logging: Add journald encoder wrapper by steadytao · Pull Request #7623 · caddyserver/caddy

Implements the #7611 feature request as an explicit logging encoder wrapper. Summary This adds a new journald encoder that wraps another encoder and prepends the systemd/journald priority prefix (&...

GitHub

He atinado con la solución a lo de iocaine: la versión en debian es muy antigua, actualizándola a la última ya funciona.

#iocaine #debian #caddy

2. Quería configurar iocaine en el VPS que tengo. Sigo todo el manual de instalación, se ejecuta bien de forma local, pero cuando le pongo delante el reverse-proxy con Caddy, aún siguendo la configuración del manual, falla. Cuando se intenta acceder a la página, el navegador encuentra problemas, como si el fallo que da a los bots se lo devolviera al navegador. Aquí creo que es más tema de que la versión de Caddy en el VPS tiene casi 4 años de antigüedad y no entiende la conf.

#caddy #iocaine