Downloading Caddy with wget and curl:
wget -O wget.dat 'https://caddyserver.com/api/download?os=linux&arch=amd64&idempotency=99511049198720'
curl 'https://caddyserver.com/api/download?os=linux&arch=amd64&idempotency=99511049198720' > curl.dat
curl.dat is 46 MB in size and is a working Caddy. wget.dat is 22 bytes in size and contains only the text:
Contact the Caddy team
Ubuntu jammy
Wget 1.21.2
curl 7.81.0
Do you still get the error? The link works for me.
With wget?
I’m still getting the error.
I can reproduce it in Restfox, just by setting User-Agent to Wget/1.21.2.
Ah yeah, @Mohammed90 reminded me, we blocked wget (and soon curl, probably) by default because we wanted to get in touch with people using the download page / build server in likely automated settings, because it’s currently not built to support automation and doesn’t have uptime guarantees.
What is your use case?
Uh, installing/updating Caddy? 
How do you install Caddy with a specific set of plugins? Do you download it to your machine with your browser and then open a WinSCP connection and drag and drop it to your server or what?
I just create the download link in the browser and then go to my SSH window and paste it - like everyone else does, at least I was assuming that until a moment ago.
Your use case isn’t as abusive as others who call the build server with wget on tight loop. You should use xcaddy. This is what most use, or at least should. Some others use Docker by building a custom container.
If you consider that abusive, why have the download page at all?
xcaddy needs Go I think? Like, if I just need a web server on a Raspberry Pi, I don’t really want to install Go on it first. Often there isn’t even enough space on the SD card for that.
The download page is for one-off download. It’s a web page. The endpoint isn’t to be used in scripts. To be clear, your use case isn’t abusive. The abuse is putting it on a tight loop. I’ve seen companies call the build server every 30 seconds! We have cache, but it still burns CPU cycles.
You can do the one-off download using the download page. You can also use xcaddy to build on another machine.
You don’t have to. You can just use docker to easily build a binary for your RPI and extract the binary from such image. Just use the correct —platform for your RPI when building it.
It’s not abusive; we’re just trying to limit its use to the webpage and the official CLI for now. But @elee and others are working on some better infrastructure that will make our petty blockers unnecessary, at least for some time.