semicole

Sorry, circling back to this, I gave up for a bit, but trying to fix this issue now. I turned Enable IP Forwarding on and Reenabled Unraid services listen on Tailscale IP and am still seeing the same issue. The IP address in my NextDNS DNS rewrite does not refer to the Tailscale IP, it refers to my local Unraid IP, this enables me to use the DNS rewrites when connected to Tailscale and when not connected to Tailscale. Since I can connect using the DNS rewrites on my local network without Tailscale, I know the DNS portion is working, it has to be some kind of issue or something I'm missing within the Tailscale config of my Unraid machine.

Hi All, I have been banging my head against the wall for a while now trying to get to the root of this issue. Previously I had this working perfectly fine, but I wiped my Unraid flash because of some unrelated issues and moved my Unraid config to a new flash drive. Now ever since essentially starting from scratch I cannot get Tailscale to work the same as it was previously. Essentially what I am trying to do is use Tailscale + NextDNS + NGINX to access my Docker containers (namely Sonarr and Radarr) when I am away from my home network. I have the following setup below. I would love for someone to review and see if I am missing anything anywhere. NextDNS rewrite setup so that if I type *.homelab, traffic is directed to my local Unraid IP This has remained unchanged since before I changed my Unraid flash NGINX proxies setup for all of my containers so that sonarr.docker.homelab for example navigates to my Unraid ip + the port for my sonarr container This has also remained unchanged since before I changed my Unraid flash Tailscale nameserver is setup to use my NextDNS configuration correctly This has also remained unchanged since before I changed my Unraid flash I can access all of my containers using the .homelab rewrite when on my local network perfectly fine, but when trying to do so when away from home and connected to Tailscale it doesn't work Only differences are the following Most or all of my containers do not have a custom docker network setup or assigned, they are all on bridge or host I don't know for sure if I have the Tailscale plugin settings setup correctly to facilitate what I am trying to do, I've pasted a screenshot below

After updating to 7.0.1 yesterday I seem to be running into some intermittent issues and crashes. I first noticed it when I went to watch Plex and my server wasn't showing up. I hard re booted and watched for a bit and my server became unresponsive after about 30 minutes and I had to hard reboot again. I have swapped over to ipvlan after this issue since I know that was an issue on previous builds, but I still saw the same issue after doing that, so I don't think that was the problem. Previously I was on 6.12.4 and didn't have any issues. I run a few dozen docker containers and 2-3 VMs. I've attached my syslogs here for reference. Any idea what the issue could be? syslog-192.168.1.167.log

So I would just need to adjust my NPM container to use the default 80 and 443 ports as opposed to 1880 and 4443 and then it should work using only the local names with no ports designated? Edit: That did it thanks!

Interesting, I had not been inputting the ports - I kind of thought that was part of the whole point of this was to not have to worry about inputting the IP or port and only using the local name. However using your input I was able to get it working with NPM set on the same docker network as my containers and adding the port at the end. So with that being said, if I did want to not have to type in the port number every time as well, how would I get that working in order to only have to type in example.local with no port? Also to add onto your Tailscale point - I believe MagicDNS only works for unique machines, so it wouldn't work for docker container addresses, only for unique machines that had an instance of Tailscale running on them.

I am about to go nuts trying to get local DNS working and accessing my docker contaiers by name on my local network. For reference I am using a Unifi UDM Pro for my router. I've had my Unraid server running for a few years now and have always used IP:PORT to access containers on my local network. I have also been using NPM to access the containers from an external network. I just recently got the itch to do some tinkering and swap over to using Tailscale VPN in order to access my containers remotely instead of NPM. I wanted to get local hostnames working so that once I start using Tailscale I can just turn on the Tailscale VPN and then type in my local host names and access the containers easily. I thought this would be as simple as setting up local DNS records in my UDMPro that reroute DNS requests from x.y.local to container IP:PORT. After doing that it didn't work so I have done a ton of research and tried all of the following and still have had 0 success. Enabled host access to custom networks Placed all containers that I would like to access remotely on a custom docker network I also tried placing NPM container on br0 in order to give it its own static IP on my local network Created proxy host in NPM that uses sonarr.x.y to forward to Sonarr container HTTP IP:PORT Created local DNS record in UDMPro that redirects sonarr.x.y to NPM IP I even installed NextDNS on my UDMPro thinking that maybe the UDMPro wasn't handling local DNS records correctly and am still seeing the same behavior I have verified that I can access the containers using their IP:PORT, but for some reason using local names is still not working. I can also still access them remotely using NPM, but just can't access them on my local network by name. I threw some screenshots in the Imgur album here for reference if needed: https://imgur.com/a/RiiYxID

I ended up going with a whole different solution altogether after realizing how difficult it was going to be to get this working how I wanted. I ended up making a new server in a Jonsbo N2 and I use the M720q as a standalone pfsense box.

I have had an R720 setup with Unraid for a while and am now looking at switching to something more power efficient and that generates a little less heat. I currently have 6 3.5" array drives + a 3.5" parity drive + a 2.5" cache SSD in my R720. I am looking at switching to a Lenovo M720q for my actual Unraid server that I'll run my Docker and VM's (if any) on and a NAS/DAS for my file storage, but had a couple of logistical questions. I've never used a NAS or DAS before and have only ever had my drives located locally in my server. If I were to move to a DAS/NAS + the Lenovo M720q, what does that setup look like exactly? I assumed I'd use the NVME in the Lenovo 720q as my cache drive, but what about my parity/array drives? I planned on putting them in the DAS/NAS, but how do those interface with Unraid exactly? Do they all show up as individual drives as if they were local to my server? Can someone help me understand exactly how that would work? I've never actually used a NAS before, so I am not exactly sure how to go about this.

I had my setup working great for a while using a GTX 1060 and just recently updated my Unradid to 6.10.3. After doing so, my Nvidia Driver seemed to bugout a bit, so I had to reinstall the plugin in order for it to work correctly and detect my GPU. So I got that working again and now when trying to start the tdarr node I get an error about the runtime. docker: Error response from daemon: Unknown runtime specified nvidia. However, I have the runtime input correctly as --runtime=nvidia and have made no changes to my tdarr node, so not sure what is going on here.

Hi All, I am trying to get Organizr server auth setup for all of my reverse proxied docker containers so that I can use Organizr as the single entry point into my server and I have been struggling to get it working. I already have all of my containers setup correctly with Swag and can reverse proxy into all of them just fine, but now when I am trying to get the Organizr server auth working I think I am doing something wrong in my nginx proxy conf files. According to the Swag proxy-conf templates it should be as simple as renaming the organizr-auth.subfolder.conf.sample file as a conf file and including the following below into each conf file that I want to setup through Organizr server auth. auth_request /auth-0; location ~ /auth-(.*) { internal; proxy_pass http://server ip address that organizr is running on:organizr port/api/?v1/aut> proxy_set_header Content-Length ""; } However, when I do that, I get the following error below in Swag logs and when trying to access the container through Organizr server auth, I get a refused to connect error. nginx: [emerg] "location" directive is not allowed here in /config/nginx/proxy-confs/radarr.subdomain.conf:6 I get the same error above for the organizr-auth.subfolder.conf.sample file as well, pointed to the "location" line in the file. Any ideas what I am doing wrong?

I have been running the My Servers plugin since mid last year with little to no issues. However just recently within the last week or so My Servers dashboard is constantly showing as remote access, even when I am on my local network. Because of this I cannot login to my server locally. I have tried runningthe unraid-api restart command with no luck. Any ideas what the issue could be?

I’m having an issue getting the ProjectZomboid container/server going. I’ve left everything in the container as default except the admin password. Reading the container log it looks like the server is functioning correctly. I’ve opened all the ports on my router, but when I try to join from the ProjectZomboid server screen it shows the server as not responding. Am I missing anything? Will update this post shortly with container logs if needed.

I'm having the same issue, but none of the fixes have worked for me. I am getting the "not connected to mothership" error in the top right drop down menu. My server is functioning fine other than this issue. I have tried the following: -rebooted numerous times -ran unraid-api restart command numerous times, both before and after a reboot -uninstalled and re installed My Servers plugin I'm at a loss as to what to do now.

I am having an odd issue with Sabnzbd beginning this morning - I've had the same setup for months now with no issues. I keep getting the following error when trying to start up the container: Error response from daemon: driver failed programming external connectivity on endpoint binhex-sabnzbd (48d3c0a31a0410c1aae7ccad21ad072b1641d1e7e137d80451110d8cada326a6): Bind for 0.0.0.0:8090 failed: port is already allocated. I have tried many different ports and get the same issue and it is doing it for both ports. If I change one port it will give me an error on the other port. I removed the container and re installed and still get the same issue. I've checked multiple times and don't have any other services or containers running on these ports. I am using port 8082 instead of 8080 and have had it setup this way for months now with 0 issues, then this pops up today. I can't get to any logs because I can't even get the container started. Any ideas?

Scratch that, I was able to find my WAN address of my router and it does match my public IP, so I think I’m good there and I have the correct ports forwarded and have verified from my ISP that they do not block ports 80 and 443, so what should my next steps be?