46
If I use Caddy for reverse-proxying into another local machine... is my local connection not HTTPS? (discuss.tchncs.de)
submitted 1 year ago by to c/selfhosted@lemmy.world
16 comments fedilink hide all child comments
 

Mind that I am very noob into self-hosting, reverse proxies and the like

When I saw that Caddy automatically handled the HTTPS thingies I was like "this is my moment then to go into self-hosting". Caddy seemed so simple.

Turns out... I am suddenly discovering that the connection between the caddy machine and the Home Assistant machine (both in the local network) is non-encrypted. So if another appliance in my local network went rogue... bum, all my info gets leaked... right?

This might sound weird because it might actually be super-duper complicated but... how come in 2025 we still don't auto-encrypt local comms?

Please be kind. Lot's of love. Hopefully I'll dig my way to self-hosting wisdom.

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 1 year ago (6 children)

If you want everything on your local lan to have SSL, look into Step CA. Its not completely beginners friendly, but if you're serious about selfhosting you will manage to set it up :) Caddy works with it also, and their examples are very helpful.

  • permalink
  • fedilink
  • source
  • hideshow 6 child comments
    •
  • [–] 2 points 1 year ago (5 children)

    Or simply create your rootCA, IntermediateCA, keys and certifictes with openSSL.

    Neither of those are begginer friendly but openSSL is probably a bit easier to get started. There's a nice book with openSSL (if you are interested I migh look how it's called) and the last chapter is all about how to create your mini-CA and everthing else to serve your proxy with valid certificates for your homelab.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 2 points 1 year ago (4 children)

    The reason i chose Step CA over openSSL is because with step CA you can automate certificate renewal without any manual intervention. I don't know how that would work with openSSL except some heavy scripting?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 1 year ago* (last edited 1 year ago) (3 children)

    Yeah thats correct !

    I Wouldn't say heavy though (maybe I see it that way because I got a bit better with bash and the like :p) because you can make use of CRL to revoke your certificates and renew them very easily with your intermediate and ready to use config files.

    But yeah, there isn't any automated way to manage certificates like Smallstep does :)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 1 year ago (2 children)

    You mentioned a book though... Now i'm curious ;-)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 year ago (1 child)

    https://www.amazon.com/Demystifying-Cryptography-OpenSSL-3-0-techniques/dp/1800560346

    It's really a good book :) And the last part is all about a mini-ca for your homelab !

    However, don't use the ED448/ED25519 algorithm based certificates for TLS as mentioned in the example... They are still not supported by any browser !

    If you can support the author, please do ! If you're on a budget, it's really easy to find in the piracy corner.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •