Ongoing Use of Caddy2 Required?

I set up vw a few months ago using Caddy2 to generate SSL certificates and allow me to create a user account.

Since then, my docker setup has grown to include other services and I’d rather remove Caddy2 entirely to prevent port conflicts.

I’ve disabled my Caddy2 docker container from running at the moment. VW continues to function just fine.

Is Caddy2 necessary for ongoing vw operations, or is it only required to enable https account creation when first setting up vw?

Will I run into problems later if I remove Caddy2 from my system?

A reverse proxy is recommended to enable HTTPS but it does not have to be Caddy2.

Caddy2 has built-in ACME support, meaning it automatically renews the certificates. But you can renew the certificates by using something like certbot instead.

So Caddy2 is not necessary but you should be aware that your certificates will expire if you don’t do something.

1 Like