Welcome to Incremental Social! Learn more about this project here!
Check out lemmyverse to find more communities to join from here!

How do I make my immich available publicly?

I have self hosted immich on Debian on my homelab. I have also setup tailscale to be able to access it outside my home.

Sometime ago, I was able to purchase a domain of my choice from GoDaddy. While I am used to hosting stuff on Linux, I've never exposed it for access publicly. I want to do that now.

Is it something I can do within tailscale or do I need to setup something like cloudflare? What should I be searching for to learn and implement? What precautions to take? I would like to keep the tailscale thing too.

PS: I would like to host immich as a subdomain like photos.mydomain.com.

Thanks!

mojoaar ,
@mojoaar@lemmy.world avatar

I personally just use NPM in front of all of the services I make available public. It's easy and handles the let's encrypt certificates also.

From my Ubiquity router I just have port 80 and 443 forwarded to the NPM.

Chewy7324 ,

I personally would be hesitant to host Immich publicly until they've done a security audit. The risk of accidentally exposing my photos publicly is too big for me.

That's why I recommend using Tailscale or Wireguard directly. Personally I'm using Wireguard for me and Tailscale for other people I want to easily access my services.

DontNoodles OP ,

Your point is valid. I'll use the learnings from this thread for other, robust, services first and keep an eye on the progress of immich in terms of security.

SexualPolytope , (edited )
@SexualPolytope@lemmy.sdf.org avatar

Without anything extra, there are three ways of doing it:

  1. Using Tailscale Funnel
  2. Direct port forwarding in your router, and pointing to the IP using some DDNS provider (e.g. desec.io)
  3. Through Cloudflare tunnel (not recommended due to privacy reasons)

In each case, you'll need a reverse proxy (e.g. Caddy) if you want secure https connections.

If you're willing to spend money, the better way would be to proxy through a VPS (using something like a Wireguard tunnel). In that way, you won't have to open ports on your home router. You can get a very cheap one since proxying doesn't need much CPU power. Just choose one with enough bandwidth. I personally proxy most of my stuff through a $12/yr RackNerd VPS.

Decronym Bot , (edited )

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
HTTPS HTTP over SSL
IP Internet Protocol
NAT Network Address Translation
SSH Secure Shell for remote terminal access
SSL Secure Sockets Layer, for transparent encryption
VPS Virtual Private Server (opposed to shared hosting)
nginx Popular HTTP server

[Thread for this sub, first seen 10th Jun 2024, 17:25]
[FAQ] [Full list] [Contact] [Source code]

fluckx ,

There's also the option of setting up a cloudflare tunnel and only exposing immich over that tunnel. The HTTPS certificate is handled by cloudflare and you'd need to use the cloudflare DNS name servers as your domains name servers.

Note that the means cloudflare will proxy to you and essentially become a man-in-the-middle. You -- HTTPS --> cloudflare --http--> homelab-immich.
The connection between you and cloudflare could be encrypted as well, but cloudflare remains the man-in-the-middle and can see all data that passes by.

Joelk111 ,

I could be wrong, as I'm no expert, but cloud flare's proxy limits file uploads to about 1GB. I had to disable it to upload larger videos to immich. For other services, probably decent advice.

Andromxda ,
@Andromxda@lemmy.dbzer0.com avatar

Tailscale has a very neat feature called Tailscale Funnel, which makes this pretty easy

DontNoodles OP ,

I read about funnel and it is really cool. But it seems to only expose the services through a *.ts.net type of URL. What I want is to use the domain that I've acquired.

GreatRam ,

Wouldn't you be able to cname your domain to the tailscale domain?

mindthegas ,

Certs served by Tailscale will still be on *.ts.net domain.

helenslunch ,
@helenslunch@feddit.nl avatar

You use a reverse proxy. Configure your DNS (GoDaddy in this case) to forward requests to your domain to your WAN IP. Set up port forwarding on your router to send HTTPS requests to your server, then the reverse proxy processes the request and directs it to the proper container.

This is honestly the most confusing and complicated part of self-hosting.

It's also all made very simple using Yunohost.

Also please move away from GoDaddy as soon as possible. Popular alternatives would be NameCheap or Porkbun.

Artemis ,

This is the way.

If you have a dynamic WAN IP (like I do), you can make use of DDNS-updater services such as this.

Also, afaik, Immich does not have chunked uploads yet (not sure if it has been updated to include that) so you might have to check your DNS' policies regarding traffic (e.g. Cloudflare proxy only allows up to 100Mb traffic and can't be used to serve media from what I read).

DontNoodles OP ,

I have used reverse proxy in office setup where my local IP was NATed to a dedicated public IP. But in my home lab, I don't have a dedicated public IP. So, i need to figure a way around that.

gaylord_fartmaster ,

I know everyone loves to shit on Oracle, but a free-tier Oracle VPS would solve this.

Or if you want something decent pay for a cheap VPS.

zqwzzle ,

We’re running home labs because we’ve learned that relying on “free” services eventually comes back to bite you.

gaylord_fartmaster ,

Absolutely, if it was anything I needed or even really wanted to be sure was reliably available I'd never put it on a free VPS.

Now, something trivial like this that just requires installing wireguard and nginx, copying over some configs, and changing a DNS record? Hard to beat free.

Technikus5 ,

I've set up several instances in circumstances like yours. The easiest way is to create a duckdns domain for yourself, and install their updater on one of your systems, to keep your external IP up to date with their DNS-Servers. Then you can use a DNS-Provider of your choice (I use Cloudflare) to create a "CNAME" DNS Record, that basically just tells a browser to redirect from your domain to the IP Address of the duckdns domain. That way you can have an automatically updating public IP behind your domain name. Then you "just" have to set up a reverse proxy (I use Nginx Proxy Manager, but there are newer and easier alternatives), and create the correct port forwarding rules in your router/firewall, and you should be good to go

Bakkoda , (edited )
@Bakkoda@sh.itjust.works avatar

Just run a cron job updating your IP every 24 hours. All I've ever done for the last decade or so.

I should clarify, I use namecheap as my registrar and Afraid as my nameserver. Afraid has curl, cron and even just a url i think you can use to update your IP.

DontNoodles OP ,

Thank you! I'll look into it.

shaked_coffee ,
@shaked_coffee@feddit.it avatar

Is immich the only service you want to expose? And did you installed it using docker or directly on your system?

DontNoodles OP ,

For now only Immich, but on a sub domain like I said in the PS. And yes, immich is installed using docker.

shaked_coffee ,
@shaked_coffee@feddit.it avatar

Then I would suggest you to take a look at Reverse Proxies, which are programs that let you publicly expose different services hosted on the same computer under different (sub)domains.

The easiest to start with (and also probably the one that better fits your needs) afaik is NGINX Proxy Manager, which can be set up really easily using docker, and you can find plenty of tutorials online (here is one I watched when I was starting to look into docker and selfhosting, it's a bit old but should still be valid).

If after having set up that you will to thinker around it a little bit and dive a bit deeper, there's also Traefik which is pretty cool and also has a lot of materials to learn online.

I don't remember if the video I linked mention it or not, but to use a reverse proxy to expose your services on the web you will first need to set up a dynamic dns (probably the easiest way is to use Cloudflare) or to ask your ISP for a static IP, then go into your routers settings and find the Port Forwarding section where you should tell your routers to send all the incoming traffic from ports 80 (HTTP) and 443 (HTTPS) to the local IP of your server. And then you should be ready to use spin up Nginx Proxy Manager or Traefik on your server.

(idk if I was clear or not but I swear it's easier that how it seems ahah)

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • selfhosted@lemmy.world
  • random
  • incremental_games
  • meta
  • All magazines
    •