Using Caddy for Automatic HTTPS with a Digital Membership Card Application

General
1

Hi everyone, I’m working on a digital membership card application where users can access their membership cards online (web-based system). I’m exploring Caddy as a reverse proxy in front of my application.

One thing I really like is how Caddy automatically provisions SSL certificates using Let’s Encrypt, which makes HTTPS setup much simpler compared to traditional setups.

My current setup idea is:

  1. Backend: .NET-based membership system
  2. Caddy as reverse proxy
  3. Domain → Caddy → Backend app

I want to ensure:

  1. Secure access (HTTPS) for member login and digital card viewing

  2. Automatic certificate renewal without downtime

  3. Clean routing for multiple membership endpoints

A. Has anyone here implemented something similar (SaaS / membership / user portal) using Caddy?
B. Any best practices for handling authentication routes or securing member data behind Caddy?

Would love to hear your suggestions or configuration examples.

2

This sounds like your standard reverse proxy use case, doable in 1 line, or even without a config file, with Caddy:

Will need more information to help you with more specifics.