Pour remplacer Nginx comme reverse proxy, vous recommandez :

I can't wait until #Anubis ends up as a #Caddy plugin so I can stick that in front of all of our self-hosted apps.

Automatic HTTPS with Encrypted ClientHello (ECH)
https://caddyserver.com/docs/automatic-https#encrypted-clienthello-ech #caddy #docs #ech #infosec

Caddy 2.10 has been released, featuring fully-automated Encrypted ClientHello (ECH), post-quantum key exchange (x25519mlkem768), ACME profiles (6-day certs!), and many improvements/fixes. Please verify it works for you and deploy away! #caddy #ech
https://github.com/caddyserver/caddy/releases/tag/v2.10.0

Caddy 2.10 web & reverse proxy server lands with support for ECH, post-quantum key exchange, global DNS config, and wildcard certs by default.
https://linuxiac.com/caddy-2-10-web-server-debuts-enhanced-tls-privacy/

Matthew Holt released #Caddy version 2.10.0. https://caddyserver.com/

把 nginx 換成 Caddy

把 blog 主機從 nginx 換成 Caddy，算是嘗試看看？ 前面有擋 CloudFront 的情況下，Caddy 自己對 Let's Encrypt 的處理有卡住，原因是 CloudFront 連到 origin server 的時候會需要有 valid HTTPS connection，但 CloudFront 上開 HTTPS only 導致 dead loop。 404.tw 在 CloudFront 修正設定變成與 client 端相同的 protocol 就正常了，但 blog 本身的 blog.gslin.org 與放圖片用的 i.gslin.com 就一直失敗，結果重試太多次撞到 Let's Encrypt 的 rate limit... 後來想到有可能是 cache 造成的，但清了 cache 然後等一個小時後發現還是不行，就先 bypass Clou…

https://blog.gslin.org/archives/2025/04/17/12351/%e6%8a%8a-nginx-%e6%8f%9b%e6%88%90-caddy/

Wow, someone found a way to make their #localhost #setup even more convoluted! Now, instead of just typing "localhost:4333", you can go through the joyous process of configuring #launchd daemons, editing /etc/hosts, and wrangling #Caddy for that sweet appname.localhost experience. Truly the pinnacle of #productivity for when you have too much time and not enough friends.
https://inclouds.space/localhost-domains #devlife #HackerNews #ngated

Some cleanup to the #Caddy #NixOS wiki page, especially documentation on the new plugin support with NixOS 25.05 https://wiki.nixos.org/wiki/Caddy#Plug-ins

Run Your Homelab Behind your VPS
…with the power of Tailscale & Caddy!
https://blog.arkadi.one/p/run-your-homelab-behind-your-vps/

Hit my head against the wall a long time before I figured this out. Hope it helps other #selfhosters

Ok, so it took me more than 10 minutes to figure out the right Caddyfile syntax for a reverse-proxy with TLS using DNS challenge from Cloudflare.

Caddy is great, and generally it is super easy, but this particular case was not.

So in the interest of saving some other poor frazzled soul like myself from digging through the interwebs, I'm throwing an example up on my blog. Hope it saves someone a few.

https://christopherbauer.org/blog/caddy-rev-proxy/

#SelfHosting
Big fan of single binary applications.
Simple install, download and put binary on your path.
No dependencies for the program to run.
Generally simple configuration.
Examples I use:
#Caddy - web server.
#Rclone - sync files to offsite storage.
#Restic - secure backup to multiple backends,
#Garage - S3 compatible storage
#VSCodium - editor

I have tried them all.
And I finally stick with #sozu + #letsencrypt!

It's a webserver/proxy with:

- hot reload
- builtin metrics
- minimal #toml configuration

You should give it a shot.
It is fairly quick to configure and get running.

#webdev #nginx #caddy
https://github.com/sozu-proxy/sozu

I made this because it reflects my latest experience of doing selfhosted stuff. Still new to all this and my system was running for around 10-11 months without any incidents. A fried SD card is definitely not what I expected to bring down everything

Wir erzählen euch jetzt mal wohin die Reise geht mit #Uberspace8 in unserem ersten Übersichts Blogpost

https://blog.uberspace.de/2025/03/unboxing-uberspace8

Fun (actually not fun at all) fact about Caddy:

This expression will be merged with AND:

@matcher {
    path /foo
    header Header-Name value
}

@matcher {
    expression `path('/foo')`
    expression `header({'Header-Name': 'value'})`
}

So I want to set up a #CI pipeline on my webserver to serve static sites.

I already have a @caddy setup that can serve static files, as well as a bunch of other stuff that all runs in #Docker containers. But I would like to have a CI pipeline that will pick up my repository changes, and build and deploy stuff to a directory that #Caddy can serve.

Now, how ridiculous would it be to have:

- an SSH server running in a Docker container
- @WoodpeckerCI, also in Docker

and get Woodpecker to build the site and use scp to copy files over to the SSH server, that will have a shared volume with the Caddy container that maps to the /var/www directory?

I am not ready to set up a whole @forgejo instance to serve from Forgejo Pages. Plus, why use the Pages thing when I have a perfectly good Caddy server running already, that would be serving the Forgejo instance anyway?

Why not some sort of S3 compatible service in a container?
Why not FTP?
How many containers can a guy run?
Am I losing my mind (probably)?

I was tuning some cache headers and had questions. I checked the usual—Stack Overflow, blogs, AI—but they all disagreed. Then I remembered: the best source is to RTFM! Aka, read the RFCs. RFCs are your friend (and the OG source of truth) — https://datatracker.ietf.org/