david1564

I have a number of Docker apps that refuse to be deleted. They're stopped, set to not start, and yet when I click 'detele' it asks me to confirm, and then refuses to accept when I click proceed. All it does is let me click cancel. I do not believe it is a timeout issue. Is there something I'm missing? Is there a 'nuke' option to get rid of them? A number are duplicates, or merely testing, and now they're there, forever, it seems. A screenshot would be rather useless - ok, here's the button, but I can't click it. Thanks in advance!

Well, this is awkward. I changed nothing, and now it's booting. fine. I....I don't know. Yay? Thanks for all your insight!

I purchased a mini pc last week with the hope of setting up a second Unraid server. it's all pretty off the shelf parts, but I seem to be unable to get it to boot from the USB key. I'm genuinely stumped. I ran the standard usb stick creator and the 'make bootable' extra afterwards. When I boot to the machine, I can get to the bios and set boot sequence, and am selecting the drive as the first in the boot order. However, it'll either go to a UFEI shell prompt, or windows (preinstalled). Has anyone ever run into this, and is there any sort of button I'm missing? There's not a lot of buttons on BIOS. I'll grab some photos in a bit, but I can't really send diagnostics if I can't boot. Thanks!

Hi, I'm having a devil of a time, and could use any insight/thoughts. I actually had it up and running flawlessly, and then my Unraid box stopped responding entirely and I did a full manual power cycle. Since that's happened, Tailscale hasn't been happy, and I don't know why. I've recreated the docker container with new appdata 3 times now. I've linked each to my Tailscale account, I have the right settings for exit node and local subnets, and the Tailscale site correctly recognizes both. However, I can only directly access my Unraid main server (192.168.4.XX) but not other devices on the .4.0/24 subnet. I use .4.0/24 for all my dockers; I like separate IP's for each, rather than a ton of different ports on one main IP. When I turn on subnet routing I can access smb shares remotely; when it's off, I can't. So subnet routing is doing something, but it's only accessing the main IP. When I try other docker containers, it fails. The confusing part is - I had it working just a couple of days ago! Any thoughts or insight would be helpful. I'm genuinely scratching my head at my ability to screw things up. Server Settings --advertise-exit-node --advertise-routes=192.168.4.0/24 Linked to online admin account I did the Ibracorp commands for ipv4 and ipv6 forwarding. Online Account Currently recognizes exit node and subnet routes, both are enabled personal PC using exit node of the server, local connections enabled. I am successfully using the exit node, but I cannot see subnet routes other than the Unraid box itself.

Hi, I'm trying to use the ddns-route53 docker, but I can't seem to find the template. The only one I can find appears to be the actual xml for unraid. Can you post a link to the relevant template? the ddns-route53.yml file. Thanks!