Espressomatic

I forgot to mention earlier, you can (should) give NPM-Plus a try. It's a fork of the original, and since your docker crashes for an unknown reason, you might as well check if it works more reliably.

That's a pretty big problem. Anyone else with the docker running into that issue? I ran the docker for a couple of months and it was always stable. At the time I wasn't however running Tailscale, and when I set that up, I went directly to the plugin.

Any info for this warning from Tailscale? I don't want to get too far into the weeds installing stuff to try and follow the info at the TS help site, unless it's going to be beneficial.

If you can use NPM without Tailscale, you need to be posting in the tailscale docker thread. Otherwise, stop using that docker and try the (recommended) Tailscale Plugin - and then consult its thread. NPM shouldn't require any special configuration for use with Tailscale. I've ran it in docker and now I'm running it in LXC.

It sounds like you're not using DNS challenge but instead are letting LE validate the server. Try DNS challenge instead and it shouldn't matter how (nor whether) your sub-domain is set up or pointing to x or y

Hmm, where is the USB port for the UNRAID Key? USB to serial adapter made with a 128 core Xeon system with 896GB of RAM. Well, technically it's a USB emulator. The system runs Unraid with a VM that mimics a 4GB USB drive, spread across an 8x8GB drive ZFS RaidZ2 pool for redundancy.

I mean a completely different computer. I have a small mini PC powered by i5-1235U running Unraid for Edge Router use. It takes care of my pfSense VM, plus Nginx Proxy Manager, AdGuard Home, Tailscale local Exit node, etc. I also have another mini system on N100 with Unraid running all my Home Automation stuff. That means I can play with other Unraid systems without ever taking down those critical services (internet access and home automation).

Runs great, I just have to reboot every couple of days. SMB performance is a little slow however.

PEBKAC. But if that doesn't work out, then he can always try PEBCAK.

Can't tell you how to get around shutting down the array, but I can tell you with good certainty that setting isn't going to fix nor solve any issues for you. Pretty sure it's not the same issue the OP had. And generally speaking that setting hasn't made much difference for my testing. If you want great (not simply good or decent) SMB performance with MacOS, iOS and generally all clients, you need to make sure your shares have exclusive access enabled and are on a Pool, not the Array. With regards to pfSense, I also virtualize on Unraid, but I keep that on its own system so it's never affected by shares nor containers I use/test. Just food for thought. A nice N100 works well for that.

Run them on different IPs and there's no port conflict. Put them both on br0 network for example.

Photos from different users are never combined, they're always completely separated by design. One user account has nothing to do with another account. You need to look at this in two stages. 1. Get Immich working on its own. 2. Get Tailscale working When both of those are satisfied, Immich will "just work" over Tailscale. In this thread, figure out Immich without Tailscale, including Admin and user setups and uploads. Do everything on your LAN. Make it work with a domain name for ease of use. Then jump over to the Tailscale Plugin thread to set up Tailscale and diagnose any possible issues. If Immich works when first set up and then fails after installing Tailscale, it's nearly 100% caused by bad Tailscale settings.

Can't help with the docker port assignment, other than to suggest changing ports in the container and forget about it. But what I can suggest is running a current version of Unraid, as 6.12.10 is over 7 months old and I can't think that anyone wants to jump back to it to double-check to see if it's something that's been fixed but undocumented.

LXC = Linux Container. Not a VM. I don't know how to get the same functionality using NPM in docker along with the Tailscale plugin.

Did some digging and some testing. You don't need to create an account on the Stremio web site. Creating one on the local instance is enough. To install add-ons, it's easiest if you then ALSO install the Stremio desktop app on your OS of choice. That way you can open the desktop app, set the server address to your local server address, and then log in with your local account. Now when you click on a link to install an add-on, the stremio: URL can be automatically opened by the desktop app after the add-on settings are configured. The add-on data will be saved to the server and available when you access the local web client without the desktop app - using the same account you created earlier. If you don't use a desktop app, then when installing add-ons, you need to configure them and then instead of clicking a final install button, you need to copy the URL from the button and paste it into the webUI. To do that you need to click on the "+Add Addon" button in the addons page, and a text field for the URL will appear. URLS need to point to a JSON file that should have been generated by the add-on configuration process. There are a some add-ons for which this can be tricky or may not work reliably (or at all). Installing the desktop app is easier and it can be deleted after add-ons are set up. This whole process is a pain and really convoluted. IMO, the whole thing is just designed poorly. But... It's worth it to jump through these little hoops to get Stremio going and accessible from iOS - or generally anything with a web browser and doesn't have the ability to install a Stremio client app.

In my instructions, only to migrate the account ID with plugins to your local server. After that it's not used. The issue I had without the site, was adding plugins. I've verified that you can create a local account successfully that doesn't rely on their site. Let me see if anything's changed with plugin installation to see if i can get those going without the need to use their site.

Instead of starting a new thread, here we go, better late than never. Step by step instructions for setting up Stremio Web on Unraid with the ability to access and play content from any device, including iOS via browser without addons or other apps. https://github.com/tsaridas/stremio-docker/issues/44#issuecomment-2383343627

Sorry for not being more specific earlier: Don't run the Tailscale docker container. So far, this is the most versatile way I've found to set this up (spoiler: NPM/Tailscale inside Debian LXC) - instructions below include scripts to for NPM and Tailscale installations in the LXC.

This also doesn't replace Tailscale running as an Unraid Plugin on my systems.

>CGNAT, ipv6, etc... Use Tailscale, don't forward and open ports. If you run Tailscale inside the same container as NPM and on Unraid as a Plugin, you won't have to worry about creating additional special docker-specific networks or configuring any containers for proxying or outside access. You'll be able to access anything you want on the Unraid system, including all containers and VMs from outside with any machine that's connected to the Tailnet (any machine also running Tailscale, like your phone, notebook, machine at another house, etc.)

Here's one way to do it (IMO, much better than running NPM in Docker) - just to note, that if you want a real signed certificate, you have to register your domain name and use a site like Cloudflare to keep track of its DNS settings. This allows Let's Encrypt to validate domain ownership when issuing a certificate. If you just want your own self-signed certificates, you can use whatever domain name you'd like. Just make sure the TLD is a legitimate one so your browser will look up the address and also make sure not to use ".local" as that's reserved for mdns and will never work properly with regular DNS.

You can always use NPM (or other reverse proxy) and Tailscale together on Debian, running inside a Linux Container (LXC). Works very well to get anything with your own FQDN(s) connected to any Docker container or VM on your system(s). If you're interested in trying that out, I've just posted some instructions to the NPM Docker thread.

They must have pulled the 11.3 update as I'm on 11.2 and don't see any update notifications for 11.3. This is a perfect example of why the Supervisor update process in Home Assistant is flawed and needs to be replaced. I gave up arguing about it over a year ago, hopefully this latest development brings the issues/dangers back to light.

Here's a bit of info about an NPM installation that's working solidly for me. You should install Tailscale using the Tailscale plugin for Unraid on every Unraid machine, then on any machines and mobile devices you plan to also use within the tailnet. You can install NPM inside a Linux Container (instead of docker) along with Tailscale. Running NPM on Debian LXC - Instructions: Installing NPM in an LXC: https://medium.com/@rar1871/nginx-installing-proxy-manager-in-lxc-v2-debian-d4d4c98109b1 Script for above instructions: https://github.com/ej52/proxmox-scripts/tree/main/apps/nginx-proxy-manager Setting up Tailscale on Debian (in the LXC): https://tailscale.com/kb/1174/install-debian-bookworm Do this first - all commands to be run inside LXC's Shell Install Unraid LXC Plugin: https://forums.unraid.net/topic/123935-plugin-lxc-plugin/ Pre-Install Updates for Debian in LXC apt-get update apt-get upgrade apt-get install apt-utils apt-get install wget apt-get install curl Read the instructions links above before the installs. Nginx Proxy Manager install using script in LXC sh -c "$(wget --no-cache -qO- https://raw.githubusercontent.com/ej52/proxmox/main/install.sh)" -s --app nginx-proxy-manager Tailscale Install inside LXC curl -fsSL https://pkgs.tailscale.com/stable/debian/bookworm.noarmor.gpg | sudo tee /usr/share/keyrings/tailscale-archive-keyring.gpg >/dev/null curl -fsSL https://pkgs.tailscale.com/stable/debian/bookworm.tailscale-keyring.list | sudo tee /etc/apt/sources.list.d/tailscale.list sudo apt-get update sudo apt-get install tailscale sudo tailscale up —auth-key AUTHORIZATION_KEY_GENERATED_ON_TAILSCALE_ADMIN_SITE TUN Access for Tailscale on Debian - add to LXC Config #Allow TUN access lxc.cgroup2.devices.allow = c 10:200 rwm lxc.mount.entry = /dev/net/tun dev/net/tun none bind,create=file #Resource limitation lxc.cgroup2.cpuset.cpus = 10 lxc.cgroup2.memory.low = 256M lxc.cgroup2.memory.high = 768M lxc.cgroup2.memory.max = 1024M You'll need to create DNS resolver overrides for Unbound if running that, or DNS entries in something like PiHole or AdGuard Home to send specific subdomains to your NPM IP. NPM cert and proxy for every service/FQDN gets filled in the same way as if you were using it from Docker. Don't forget to make a proxy entry for NPM itself.

Are you letting people on the internet access any devices or services behind your firewall without Tailscale? If not, then you don't need to use Cloudflare for anything related to IP pointing (keep it only for DNS validation so you can generate certificates for your intended domain) Tailscale will handle resolution of your domain and NPM will handle certs and subdomains. It also sounds like the way you have Tailscale and NPM set up is way too fiddly and I'd recommend starting from scratch and not following whatever guide you mentioned. Let me see if I can find a good reference for you that's similar to what I have set up - to avoid me having to remember every step. Incidentally, my NPM never crashes.