this post was submitted on 16 Sep 2025
43 points (97.8% liked)

Selfhosted

51526 readers
383 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
43
If I use Caddy for reverse-proxying into another local machine... is my local connection not HTTPS? (discuss.tchncs.de)
submitted 1 day ago by unknowing8343@discuss.tchncs.de to c/selfhosted@lemmy.world
15 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
[–] johannes@lemmy.jhjacobs.nl 1 points 22 hours ago (1 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.

[–] N0x0n@lemmy.ml 2 points 22 hours ago (1 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.

[–] johannes@lemmy.jhjacobs.nl 2 points 22 hours ago (1 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?

[–] N0x0n@lemmy.ml 2 points 21 hours ago* (last edited 20 hours ago) (1 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 :)

[–] johannes@lemmy.jhjacobs.nl 1 points 21 hours ago

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