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

 

• Install LXC Plugin on Unraid from Community Apps (I like to use Default Network br0)
  • https://forums.unraid.net/topic/123935-plugin-lxc-plugin/
• Go to LXC page/tab next to Docker page/tab
• Add LXC Container
• Enter a name for your container (no spaces)
• Enter an optional description
• Distribution: Debian
• Release : Bookworm
• MAC Address: (automatically generated - or enter your own)
• Start after creation: ON
• Click icon for container and select Terminal

 

• Install Updates & a couple of packages needed for the installations to follow

 

apt-get update
apt-get upgrade
apt-get install apt-utils
apt-get install wget
apt-get install curl 

 

 

• 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

 

• Click container icon and Show Config
• Copy the location of the config file to clipboard (/mnt/path_to_config_file…)
• Stop container
• Open Unraid terminal and edit the config file (nano /mnt/path_to_config_file…)

 

• Add the following to the end of the LXC Config (TUN access so Tailscale can create its network)

 

#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 = 1	# This is a CPU core or list of cores to use for the LXC - omit line to allow all cores
lxc.cgroup2.memory.low = 256M
lxc.cgroup2.memory.high = 768M
lxc.cgroup2.memory.max = 1024M

 

• Save the config file
• Close terminal
• Start LXC container
• Open Terminal into LXC container

 

• Create pre-shared key from your Tailscale Admin page
  • https://login.tailscale.com/admin/machines/new-linux
  • Click the Generate button at the bottom
  • Copy (only) the text after "--auth-key=" - it should start with "tskey-auth-..."

 

• Install Tailscale inside LXC
  • First the package sources

 

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

 

• • Next the install

 

sudo apt-get update
sudo apt-get install tailscale

 

• • Finally running/activating (paste the tailscale up command with the key you copied earlier)

 

sudo tailscale up —auth-key AUTHORIZATION_KEY_GENERATED_ON_TAILSCALE_ADMIN_SITE

 

 

• Access your NPM installation - make sure you enter HTTP and NOT HTTPS or the page won't load
  • http://IP_ADDRESS_OF_LXC_CONTAINER:81
  • Name: [email protected]
  • Password: changeme

 

 

 

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.

 

 

Edited February 23, 20251 yr by Espressomatic
fix typos

[Reserved for additional content]

[Final reserved post] - First post is being edited right now

Cool tutorial!

 

Are you interested in a container archive that you can give to other users for easy installation?

 

Something like this:
https://github.com/ich777/unraid_lxc_pihole

 

This will be maybe be installable through the CA App... Maybe...

Yes, thanks.  Give me a couple of days to go over everything with a closer look, as I want to redeploy from scratch using my instructions to make sure they're clear and work as expected. I wrote that after setting up myself and need to make sure I didn't accidentally forget something.

 

 

1 hour ago, Espressomatic said:

Yes, thanks.  Give me a couple of days to go over everything with a closer look, as I want to redeploy from scratch using my instructions to make sure they're clear and work as expected. I wrote that after setting up myself and need to make sure I didn't accidentally forget something.

Sure, just take a look at the build directory in the linked Git Repo how I create the archives, it should be prette easy to understand and re deployment or even sharing the container archive with others should be pretty simle.