OK. So, still having this freezing, Last night I decided to completely uninstall Tailscale and NPM from my server. I went in and erased all the folders and I uninstalled them just to make sure. 

Reinstalled them both doing fresh installs (no re-install) and started over from scratch. Had everything up and running first try......and then when I woke up this morning I checked on it, and it froze again. Simple restart of the NPM docker and its good again for 1/2 day.

I don't understand ho this can be working for hours....1/2 a day, and then freeze. It either has to be a bug, a conflict that arises over time, or some sort of memory issue.

 

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.

 

 

Edited November 11, 20241 yr by Espressomatic

Thanks for taking the time to help out. I was working all day yesterday so I will go through it all now and see what I can do. I'll keep you updated!

Thanks again!

Thanks again for trying to help. I followed your steps, got the LXC installed, got NPM and Tailscale installed, etc...

Couldn't figure out how to connect them all. Tried for a while, just couldn't get it to go. 

I've removed it now, tried another NPM docker and it wouldn't work at all, went back to the Official version and my setup is working again...I made a couple changes in the config file that were different that the previous NPM I had for the past year to see if that helps the freezing situation.

Will report back.

 

Edited November 13, 20241 yr by orangewhip
typos

Nope, still NPM still freezing up on me.

I guess I'll just have to live with it as it stands for now and hopefully somebody does a step-by-step on how to get it working the way I'm trying to do it. Not saying my way is right or better, its just how I understand it more from the tutorial I watched from Tailscale themselves.

Thanks again for trying to help. I'll keep reading up on all of it and see if I can figure things out.

Hi everybody,

 

I have a strange problem with NPM and renewing my certificates. My setup is as follows:

 

I own several domains; let’s use "example.com" as an example.

 

I’ve configured a CNAME for a subdomain "test.example.com" that points back to example.com. The DNS A record is set to my IP address.

 

However, I’m unable to renew my certificate with this configuration.

 

When I set the CNAME for the subdomain "test.example.com" to a DuckDNS domain (with the same IP as the A record), the certificate is created without any issues.

 

Why on earth is this happening? The ports are open; otherwise, I wouldn’t be able to get a certificate in the first place.

 

 

 

 

Hello everybody..

 

I've got a problem with tailscale and nginx.. I'v e tried to follow some tutorials, but no luck.

i have my 2 containter on the same network. and i'm trying to access my local lan with tailscale.. i am using cloudflare and i have a cname..

 

I've seen this..

 

 

I think the problem might be that, the proxy he is using.. (caddy) when installed is part of the tailscale network .. And mine is not:(

Is there any way intergrate nginx into tailscale as a user the same way this guy did??

 

Hope you can help:)

 

Thank you!

regards

 

10 hours ago, WillyThunder said:

I have a strange problem with NPM and renewing my certificates. My setup is as follows:

 

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

7 hours ago, Mattti1912 said:

Is there any way intergrate nginx into tailscale as a user the same way this guy did??

 

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.

 

 

 

 

Edited November 18, 20241 yr by Espressomatic

8 hours ago, Mattti1912 said:

Hello everybody..

 

I've got a problem with tailscale and nginx.. I'v e tried to follow some tutorials, but no luck.

i have my 2 containter on the same network. and i'm trying to access my local lan with tailscale.. i am using cloudflare and i have a cname..

 

I've seen this..

 

 

I think the problem might be that, the proxy he is using.. (caddy) when installed is part of the tailscale network .. And mine is not:(

Is there any way intergrate nginx into tailscale as a user the same way this guy did??

 

Hope you can help:)

 

Thank you!

regards

 

That's how I set up mine. There is a couple things you need to do in your NPM settings to make the connection. 

I have mine all working, but as you can see above my NPM freezes on me once a day for some unknown reason I still haven't figured out.

Under your NPM docker setup, turn on advanced settings and inside "Extra Parameters" put in this: --net=container:TailscaleDockerNameGoesHere

You also need to set your "Network Type" to: None

That allows your NPM to connect thru your Tailscale Docker. Ohh and yes, you need to use a The Tailscale Docker and NOT the plugin, although I use both so that I can also connect to Unraid itself via the plugin because the Docker allows you to connect thru your custom Network Type only.

Edited November 18, 20241 yr by orangewhip
typos

15 hours ago, orangewhip said:

my NPM freezes on me once a day for some unknown reason

 

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.

 

 

13 minutes ago, Espressomatic said:

 

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.

 

 

Been pretty stable for me and i do have a lot riding on it

17 hours ago, orangewhip said:

I have mine all working, but as you can see above my NPM freezes on me once a day for some unknown reason I still haven't figured out.

 

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.

 

 

4 minutes ago, Espressomatic said:

 

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.

 

 

I haven't heard of that. I'll look into it. I ran NPM for over a year without any issues, but it was a different fork. Once I went to run it all thru Tailscale, the fork wouldn't work anymore because of the IP addresses it used, so I switched over to the Official fork and it works perfectly..  except this freezing. 

 

You can see how I have my stuff setup from my earlier posts.

NPM Plus is in Community apps and is regularly updated.

 

Here's the github, just to make sure you find the right one: https://github.com/ZoeyVid/NPMplus

 

 

 

 

I'm trying to get Adguard Home and NPM and some apps like Sonarr, Radarr to work behind NPM.

 

NAS IP- 192.168.1.10

Adguard Home- 192.168.1.2

NPM IP- 192.168.1.99

 

I can reach NPM via something.home.com- I input the IP address of NPM in Adguard Home.

 

My question is, a lot of people says create a network.  I did, named it proxynet using the command docker network create proxynet.  If I assign Sonarr, Radarr to proxynet, how does it work behind NPM?  I think it will have an ip address of 172.x.x.x.

 

What's the way to fix this?

5 hours ago, jang430 said:

My question is, a lot of people says create a network.  I did, named it proxynet using the command docker network create proxynet.  If I assign Sonarr, Radarr to proxynet, how does it work behind NPM?  I think it will have an ip address of 172.x.x.x.

You put NPM in that network too, not on a separate IP.

If I do that, I think it will get an ip address 172.x.x.x, how can I point adguard home (on 192.168.1.2) to NPM (on 172.x.x.x)?

 

Update:

 

I redid the setup.  Selecting custom br0 for adguard home, assigned ip of 192.168.1.2

Installed nginx proxy manager, and used proxynet, an error occured.

 

"WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
b7c2e2cef967044f781812bece5c0be151faae7ac46b6875a7b6e9fa031b010a
docker: Error response from daemon: driver failed programming external connectivity on endpoint Nginx-Proxy-Manager-Official (1c106880a1f9168700163aa93143253e421c203b1bf839655532736103699c6a): Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use."

 

When I select custom br0, it finishes successfully.  Custom br0 has subnet of 192.168.1.0/24.

 

Pasting my docker settings

 

Edited November 22, 20241 yr by jang430

4 hours ago, jang430 said:

If I do that, I think it will get an ip address 172.x.x.x

It gets bridged so you use the unraid server's ip. 

Since the unraid UI uses 80/443 by default you'll have to change those to something else.

 

If you want to stay on br0 you have to turn on "Host access to custom networks" in Docker settings.

Edited November 22, 20241 yr by Kilrah

Done!  If I use proxynet, I get the same IP address of the NAS.  To get to Nginx, I have to use NAS_IP:880.  Adguard Home DNS rewrites doesn't support NAS_IP:880.  How is it done?

14 minutes ago, jang430 said:

Done!  If I use proxynet, I get the same IP address of the NAS.  To get to Nginx, I have to use NAS_IP:880.  Adguard Home DNS rewrites doesn't support NAS_IP:880.  How is it done?

 

NPM has to listen on 80 and 443. You need to change the ports used by Unraid, and then create an entry in NPM to point to Unraid.

 

This "catch-22" is why I put NPM on its own IP - and easily sharing that with Tailscale is why I didn't use the docker.

 

 

2 hours ago, Espressomatic said:

This "catch-22" is why I put NPM on its own IP - and easily sharing that with Tailscale is why I didn't use the docker.

 

 

I thought so.  I think it would be better to have NPM on it's own IP.  But I cannot get it to work.  I don't know which network to choose for NPM.  Bridge, Host, Custom: br0 or Custom: proxynet (the one I created).  Whether I choose Bridge, or Custom: proxynet, I have to change ports of NPM.  How did you do it?

As Docker, it would be Custom br0 for its own IP within your subnet. That way it can use ports 80 and 443 without any conflicts.

 

I ran it this way for most of this year working very reliably. AdGuard Home also runs on br0 on a different IP. What I don't do is to any rewrites with AGH - it sends upstream to Unbound and I use Overrides on that to send FQDNs to NPM.

 

I only moved away from Docker when I also set up Tailscale with it.

Edited November 22, 20241 yr by Espressomatic

@Espressomatic

Can you share further how to make this work?  I have both Adguard Home and Nginx on Custom: br0.  They have 192.168.1.2 and 192.168.1.3 IPs respectively.  How will Nginx be able to forward to Sonarr if it's on proxynet?

 

Like this:

 

 

You can also change your AGH webUI port number to 80 if you want, as nothing else is on that IP.  Or you can leave it and just set 3000 as the port when you make a proxy host config for it in NPM.

 

 

Edited November 23, 20241 yr by Espressomatic