Anyone use Caddy w Porkbun here? Looking for help after updating Caddy…
from ocean@mander.xyz to selfhosted@lemmy.world on 23 Apr 22:06
https://mander.xyz/post/28686883

I’m slightly freaking out. I recently ran some updates on my Linux Mint server computer. Afterwards, my modules, like Porkbun, had been removed and kept giving a 400 error when trying to add-package. Without the porkbun dns module, caddy can’t pass the keys and nothing with reverse proxy from me. The porkbun git page mentions some upgrade to the DNS system a few days ago that they said was connected to this. Any ideas of what to do? Do I downgrade Caddy until they resolve? I’m not the most computer savvy so I appreciate the help.

#selfhosted

threaded - newest

fishynoob@infosec.pub on 23 Apr 23:17 next collapse

Sorry, I don’t use either of those services. Would you be willing to explain your setup? I use my own CA with HAProxy for TLS termination (with servers side TLS) so I might be able to give some general tips. Maybe.

[deleted] on 23 Apr 23:25 next collapse

.

sugar_in_your_tea@sh.itjust.works on 24 Apr 02:03 collapse

I’m guessing they are doing DNS challenge for getting Let’s Encrypt certs.

Xanza@lemm.ee on 23 Apr 23:55 next collapse

I guess it depends on how you got caddy to begin with. If you used xcaddy, you have to update caddy the same way (recompile via xcaddy) otherwise you’ll get the default binary which has no misc modules by default, which kinda sounds like what’s happened but who knows for sure.

If you’re feeling daring, you can try to compile caddy yourself with xcaddy, it’s super easy.

Save your Caddyfile’s (ultra important), and uninstall caddy. Install xcaddy (apt install xcaddy [or go install github.com/caddyserver/xcaddy/cmd/xcaddy@latest]). Then use xcaddy to compile caddy with the modules you need;

$ cd /tmp
$ xcaddy build --with github.com/caddy-dns/porkbun --with github.com/caddy-dns/cloudflare --with github.com/some-user/whatever-module

Caddy will build and be spit out in /tmp/caddy. Move it to /home/username/.local/bin or something, and make sure that directory is in your path. Don’t forget to chmod +x caddy.

Run caddy like normal and see if this fixes your issue. If not, you’ll likely have to try and older version of caddy (uninstall and specifically install the previous version or if you can’t, use xcaddy with CADDY_VERSION to build a specific version with your modules), or wait until they push a fix for whatever they broke.

sugar_in_your_tea@sh.itjust.works on 24 Apr 02:02 collapse

That’s what I did for Cloudflare and it works well.

sxan@midwest.social on 24 Apr 00:19 next collapse

I’ve never heard of Porkbun, but it doesn’t sound like a caddy issue. Let’s Encrypt requires being able to resolve the DNS name you’re requesting a cert for, and to be able to connect to your web service and fetch a secret to prove you own the domain. If porkbun does something like punch a hole in your LAN firewall and let in http traffic, then porkbun is the problem. Not Caddy.

just_another_person@lemmy.world on 24 Apr 02:00 next collapse

Then why did you comment? 😂

sxan@midwest.social on 25 Apr 11:46 collapse

Because they were wondering if it was a Caddy issue, and I’ll bet real money it isn’t.

Being able to exclude components from being a possible source of the issue is critical to problem solving.

sugar_in_your_tea@sh.itjust.works on 24 Apr 02:02 collapse

and to be able to connect to your web service and fetch a secret to prove you own the domain

This part isn’t true, you can use DNS challenge and they don’t need to connect to your service. I have several services on my LAN that have never been accessible from the internet that have Let’s Encrypt certs.

That sounds like the method OP is trying to use.

sxan@midwest.social on 25 Apr 11:44 collapse

Hmmm. You’re right; it’s a mechanism I’ve never used because it’s more work and it is slower, and I forget about it. All you need to do is be able to prove you own the domain, and control over the DNS record is certainly viable.

Is that what Porkbun does? Because Caddy can automate the http method, but not the DNS challenge method, because both require a handshake and that’s updating the DNS record.

sugar_in_your_tea@sh.itjust.works on 25 Apr 12:29 collapse

Porkbun is a domain registrar, so I’m guessing OP is using their API to edit a DNS record with the challenge so Let’s Encrypt can prove ownership of the domain. Caddy can automate that, however, you need a Caddy build with a plugin for the registrar (use xcaddy), and then supply login details in the Caddyfile.

Here’s the plugin for porkbun, and the README documents how to use it.

I prefer doing it this way so I don’t need to expose my service to the internet to get a TLS cert, and I can also keep port 80 blocked.

Auli@lemmy.ca on 24 Apr 03:44 collapse

Downgrade to 2.9 till the porkbun plugin gets updated to work withb2.10.