u/Do_TheEvolution

been using it for 3 years even in production along veeam.

love the way it functions, where you are not thinking about incremental and full backups, every snapshot is full, but the speed and storage used is that of an incremental, its all deduplicated into hashed chunks that are kept or discarded.

Borg, Restic and others also work the same way... but Kopia is the one that has all the features straight out of the box, mainly being crossplatform, native cloud services support, having a GUI version for simpler dumb deployments, designed day1 for multithread.

Here are my notes on deployments, on linux I use systemd and ntfy to get push notifications on my phone if something fails...

Also planning to make a dashboard for it with prometheus and grafana, like I did for veeam B&R.

It just irks me a bit that on many arch systems I setup its the only package I have from AUR.

Its written in golang, so a single binary without runtime or some dependencies tree, so maybe it should be on the easier side on packaging and maintaining...

• pull request + discussion
• documentation on the change.

since version 2.11, feb-2026

it only applies if the backend is HTTPS

before the change Caddy would forward the original Host header from the client request - whatever.example.com to the upstream

now the default behavior is that from the Caddyfile it picks up upstream host+port and plugs it as the Host header - server-blue:443

so, the typical setup for HTTPS backend was this, where caddy is told to ignore that backend has not a valid certificate:

whatever.{$MY_DOMAIN} {
    reverse_proxy https://server-blue:443 {
        transport http {
            tls
            tls_insecure_skip_verify
        }
    }
}

now you need to add header_up Host {host} if you want previous behavior.

whatever.{$MY_DOMAIN} {
    reverse_proxy https://server-blue:443 {
        header_up Host {host}
        transport http {
            tls
            tls_insecure_skip_verify
        }
    }
}