Selfhosted

59905 readers

1187 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Security considerations about hosting Immich from home (lemmy.world)

submitted 4 days ago* (last edited 3 days ago) by Maroon@lemmy.world to c/selfhosted@lemmy.world

35 comments fedilink hide all child comments

So far, my self-hosting has been limited to Pi-Hole, and a static website. I now want to try out something new, an Immich server.

I have a static IP from my ISP, so I don’t need to rent out a VPS. However, given that this IS a home internet, I want to be extra sure that it is going to be secure.

In my existing website, I use Fail2Ban + BadBotBlocker + Anubis + Nginx rate limits to protect it from scrapers, bots and malicious users, and it works well. With photos (especially family photos) at stake, I just want to know more on how to protect my server.

Add: thanks for the helpful replies. I will be sharing the photos with family, many of whom live abroad.

you are viewing a single comment's thread
view the rest of the comments

[–] randombullet@programming.dev 7 points 4 days ago (2 children)

I have it behind OAuth.

And then a reverse proxy via NPM.

I don't know what else to do on it aside from keeping it fully VPNed.

[–] femtek@lemmy.blahaj.zone 6 points 4 days ago (1 children)

Yeah, maybe it's because I run public sites on kubernetes at work that I'm not as scared but a good locked down network is fine. Thousands or businesses run public URLs, as long as you configure it right you are mostly good. There is always a risk of vulnerabilities in the software for immich, your proxy, your auth provider so doing it that way increases your attack surface than just the VPN.

[–] curbstickle@anarchist.nexus 7 points 4 days ago

Thousands or businesses run public URLs, as long as you configure it right you are mostly good.

Part of "configuring it right" for companies is generally having the public-side be pretty well walled off from anything internal though, there isn't anything wrong with taking the same approach at home, too

[–] lemmyvore@feddit.nl 1 points 3 days ago

Add mTLS to the reverse proxy and to the Immich client app and forbid access without it.

The mTLS certs can be self-generated. There are tutorials for generating your own CA and individual mTLS certs for each device. Then you put the ca.pem file in a place accessable by NPM and add a couple of commands to the "Advanced" tab of the Immich proxy host, and you put the mTLS cert on the phone and load it into the Immich app.

mTLS is a super strong method, not only does it serve as great authentication for that particular device, it also checks the TLS connection for tampering so it can't be hijacked even if somehow you get rogue certificates loaded on your phone, you can revoke certs if your phone gets lost or stolen etc.