You must log in or # to comment.
As long as you don’t directly connect it to the internet, it’s not hard.
When you do, it does become hard.
Only if you care about security, which you should ofc.
People who don’t care about security are the cancer of the selfhosting-world. Billions of devices are part of a botnet because lazy/stupid owners don’t care about even the most basic shit, like changing the stock password. It’s insane.
I setup caddy and a proxy server for ingress.
Essentially I have a server with wireguard connections between my home server and the external VM.
Proxy using proxy protocol with nginx so it preserves the ip.
DNS certificate management with cloudflare, and I’ve got Authelia in front of the majority of my websites, with some exclusion rules, say for a share link.
Authelia has mandatory 2FA, anything less is silly, with Grafana alloy scrapping caddy metrics.
Anywho most of my stuff runs in docker. The stuff I don’t want on the WAN but on tailscale/Lan has a filter to block the wireguard interface.
Tell that to someone starting out and look at their deer in the headlight face. Then you’ll realize that the point went over your head.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters DNS Domain Name Service/System HTTP Hypertext Transfer Protocol, the Web nginx Popular HTTP server
2 acronyms in this thread; the most compressed thread commented on today has 12 acronyms.
[Thread #134 for this comm, first seen 5th Mar 2026, 16:50] [FAQ] [Full list] [Contact] [Source code]
I wouldn’t say it’s “hard”, but taking responsibility for all the photos your wife took of your darling children growing up is… a thing.
For old photos, you can easily have half a dozen copies on old HDDs, DVDs, cloud… a few GB maybe? How many photos can be that important?
If you bork your server, those photos are not lost, just harder to access. The Missus can still be upset, just not as much.
I know there are solutions, but if you never get involved its never your responsibility.
Because it is for those who aren’t sysadmins or at least amateur Linux enthusiasts. The easiest tools quickly become very hard when something breaks and you got no one who could fix things for you you don’t know anything about.
Who are they? Hard for who?
I propose a new title… “This thing I know a lot about is easy!”
Immich is amazing until you update and your wife is complaining she can’t see her photos.
The most reliable piece of hardware and software I have is my Synology.
Now that it’s in stable release, is it really still the case?
You know, I have been using Immich since forever. The last issue was probably a year ago.
Honestly, the time i had to manually intervene since ~2 years is less then 5-10 times, and that is way before the stable release. So I doubt that.
Don’t update anything without a way to restore.
I just rename the immich file, install a new immich instance and copy the data over manually to the new install, deleting the old install file after a week or so
I’ve had the least buggy experience that way
Immich updating is a dogwater experience
I wish it was that simple. I have over 15 TB of videos and images as far back as the 1970s. Mostly in raw format or slog format. Copying and pasting an instance would take me a ton of time.
Yeah I wouldnt trust immich with directly storing it myself
Get that stuff off on its own and have immich access that as shown in Louis Rossmann’s setup video
Think of it like having a dedicated steam drive with the os on its own, so if you have to format or decide to distrohop, you don’t have to download and reinstall a dozen +250GB games
