Linux & Azure cloud engineer. Sometimes a wolf, or a fuzzy dragon.

  • 0 Posts
  • 3 Comments
Joined 1 year ago
cake
Cake day: December 27th, 2023

help-circle

  • There’s nothing bad per se, but obviously not sharing the inner workings of your internet facing server is just another step to protect yourself.

    You mention in the OP this is for a business, my opinion you should be working on a professional resource/developer to manage this for you and not random Lemmy users.

    On the use of Caddy, your configs here host a lot of sites with many specific configurations, I’m not sure caddy can support all of this. nginx is the tool of choice for a wide majority of the internet for a good reason.


  • idk what nonsense the other commenter is posting but essentially your network flow should look like this:

    internet user -> your IP (found via dynamic DNS) -> firewall/router DNAT port 443 -> proxy (nginx/caddy) listening on 443, backend set to port 80 -> vaultwarden port 80

    You’d load your SSL certificate into the reverse proxy, I’m not familiar with caddy but I use nginx for this purpose.