unknowing8343

joined 2 years ago
sorted by: new top controversial old
47
If I use Caddy for reverse-proxying into another local machine... is my local connection not HTTPS? (discuss.tchncs.de)
 

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.

Release 1.3.0 Advanced Redaction, Security enhancement and code improvements · Stirling-Tools/Stirling-PDF · GitHub in c/selfhosted@lemmy.world
[–] unknowing8343@discuss.tchncs.de 2 points 2 months ago (1 children)

Is there a way one could load this up as a Nextcloud app, or something?

GitHub - sergi0g/cup: 🥤Docker container updates made easy in c/selfhosted@lemmy.world
[–] unknowing8343@discuss.tchncs.de 4 points 5 months ago (1 children)

Let me stop you right there: the chances of Jellyfin going rogue are much smaller. It's libre software. It's GPL. It's copyleft. We are pretty much safe.