<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Homelab on rikosjett</title><link>https://rikosjett.com/topics/homelab/</link><description>Recent content in Homelab on rikosjett</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 07 Mar 2026 00:00:00 +0100</lastBuildDate><atom:link href="https://rikosjett.com/topics/homelab/index.xml" rel="self" type="application/rss+xml"/><item><title>Exposing Immich over Tailscale with a companion container</title><link>https://rikosjett.com/blog/exposing-immich-over-tailscale-with-a-companion-container/</link><pubDate>Sat, 07 Mar 2026 00:00:00 +0100</pubDate><guid>https://rikosjett.com/blog/exposing-immich-over-tailscale-with-a-companion-container/</guid><description>&lt;p&gt;I already had &lt;a href="https://immich.app"&gt;Immich&lt;/a&gt; running on a &lt;a href="https://docs.immich.app/install/synology/"&gt;Synology NAS&lt;/a&gt;, with the &lt;a href="https://tailscale.com"&gt;Tailscale&lt;/a&gt; package installed on the NAS itself. Accessing Immich meant hitting the NAS IP and port. It's functional, but not great. I wanted a proper subdomain, HTTPS, and no port in the URL.&lt;/p&gt;
&lt;p&gt;My idea was to run a Tailscale container alongside Immich, use &lt;code&gt;ts serve&lt;/code&gt; to terminate HTTPS and proxy traffic, and not touch the existing Immich setup at all.&lt;/p&gt;
&lt;h3 id="the-tailscale-container"&gt;The Tailscale container&lt;/h3&gt;
&lt;p&gt;Create a new directory for the stack, e.g. &lt;code&gt;/volume1/docker/IMMICH-TAILSCALE/&lt;/code&gt;, and create the sub-directories &lt;code&gt;state&lt;/code&gt; and &lt;code&gt;config&lt;/code&gt;. You should also prepare some files on your computer, that you will upload before running the stack.&lt;/p&gt;</description></item></channel></rss>