this post was submitted on 03 May 2025
27 points (84.6% liked)

Selfhosted

46674 readers
538 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] BlueEther@no.lastname.nz 0 points 1 day ago (1 children)

I did have a slight issue when I went to 0.19.11 with caddy cloudflair, but that is outside of the bounds of what you control

[–] ubergeek77@lemmy.ubergeek77.chat 1 points 1 day ago (1 children)

What issue did you have? If I can handle it for the user automatically, I can add a best effort attempt to avoid it.

[–] BlueEther@no.lastname.nz 1 points 1 day ago* (last edited 1 day ago) (1 children)

Just a build conflict, it was resolved upstream in a day or so:

[proxy builder 2/2] RUN xcaddy build --with github.com/caddy-dns/cloudflare:
...
3.16 go: downloading github.com/googleapis/enterprise-certificate-proxy v0.3.2 

53.19 go: downloading github.com/golang/groupcache v0.0.0-20210331224755-41bb18bfe9da 

53.47 2025/04/10 07:47:10 [INFO] exec (timeout=0s): /usr/local/go/bin/go build -o /usr/bin/caddy -ldflags -w -s -trimpath -tags nobadger,nomysql,nopgx 

68.67 # github.com/caddyserver/certmagic 

68.67 /go/pkg/mod/github.com/caddyserver/certmagic@v0.21.6/solvers.go:386:9: invalid composite literal type libdns.Record 

68.67 /go/pkg/mod/github.com/caddyserver/certmagic@v0.21.6/solvers.go:445:17: zrec.record.Type undefined (type libdns.Record has no field or method Type) 

68.67 /go/pkg/mod/github.com/caddyserver/certmagic@v0.21.6/solvers.go:449:45: zrec.record.Name undefined (type libdns.Record has no field or method Name)
88.82 2025/04/10 07:47:45 [INFO] Skipping cleanup as requested; leaving folder intact: /tmp/buildenv_2025-04-10-0746.3854595282 

88.82 2025/04/10 07:47:45 [FATAL] exit status 1
failed to solve: process "/bin/sh -c xcaddy build --with github.com/caddy-dns/cloudflare" did not complete successfully: exit code: 1`

Ah I see. I've gotten into some back and forth with the maintainer of Caddy about these build inconsistencies and lack of versioning, and he responded by locking issues on me... twice.

After that communication, I resigned to just keep things as they are because upstream is not willing to make the experience better for use cases like these.

He is impossible to work with, but Caddy is just really good :/