tmchow

@Eurotimmy I've updated the xml file to add the chown directions to avoid the permissions error. It should be picked up by CA within a few hours on the next refresh cycle.

I've had tailscale running on my unraid server for awhile now, but have been using some script method I found way back. #!/bin/bash set -x # check latest version against what's installed VER=$(curl -sL https://api.github.com/repos/tailscale/tailscale/releases/latest | jq -r ".tag_name" | cut -c 2-) if [ "$VER" = "$(tailscale version | head -n1)" ]; then echo "$VER already installed, exiting..." exit 0 fi # download latest version, restart daemon echo "New version $VER available. Grabbing..." curl -fsSL -o /boot/config/tailscale/tailscale_static.tgz "https://pkgs.tailscale.com/stable/tailscale_${VER}_amd64.tgz" if [ $? -eq 0 ]; then pkill tailscaled sleep 1 /usr/sbin/tailscaled -cleanup bash /boot/config/tailscale/install.sh bash /boot/config/tailscale/start.sh fi I just noticed this plugin.. is this the recommended way to go vs rolling my own thing with this script? I cannot remember for the life of me why that script was recommended...perhaps before a plugin was created?

what’s not working with this template that you can’t update to the latest version?

Hmm. I don’t see this option at all in my configuration. https://imgur.com/a/OzZLKl6 I'm not sure how to update the firmware on my unit (I've also got a APC Smart-UPS X 1500). I recall trying to do this connecting the USB cable to a windows laptop but the software couldn't find it. According to the menus I’m currently on: firmware 09.8 ID:20 My date code is 2003 so it should be updated according to this page here: > According to that page my firmware update should work but when I previously tried this it didn't work. I got to 7% and it power cycles with no update successful:

Basic auth isn’t supported anymore so those aren’t needed. As for the error it looks like a permission issue. Make sure the directory and file are accessible by the n8n user

You’re not missing anything. Mistake on my part. I’ve patched the app.

Hi, sorry! I haven't paid much attention to this container I created support for until now as I don't use n8n much. However, I have done updates which should fix this for n8n 1.x launch: - Changed home directory to `/home/node/.n8n` from `/root/.n8n` - Renamed webhook tunnel variable to `WEBHOOK_TUNNEL` - Dropped basic auth config since it's deprecated in n8n 1.x

Thanks. I came to this conclusion after posting my original post. Appreciate you chiming in to reaffirm!

you can also accomplish this within Plex server settings specify the transcode directory to be /transcode/PlexRamScratch instead of it being /transcode

so no issue with a VM on the cache drive causing too many writes to the SSD? Not sure if it’s something to worry about or not

my cache drives are in a cache pool actually. So instead of putting the imagined on a single ssd connected with unassigned drives plug-in, sounds like I should put it on the cache pool?

Deleting the image shouldn't do anyting to your preferences (e.g. saved in /mnt/user/cache/appdata/n8n).

Hey! Sorry, I'm not using this regularly anymore hence me not looking at this. I dived back into this and saw the same "not available" message you had. However, I deleted the container and reinstalled it from scratch and it seems to work. Not sure what is different as the XML is exactly the same. Try reinstalling from scratch?

put it in your go file.

I’m using the unraid.net stuff

I’ve been running Home Assistant in a VM for years on my unraid server. However, the disk image has always been on my array. I didn’t think of this until recently, when I added a Win10 VM, and it was so slow to use. After some research the clear culprit was the image being on the array. I moved it to to an SSD that is connected in unassigned devices plugin. As soon as I did that win10 QAS very responsive. Home Assistanr overall works fine with the image on the array, but ive found it a bit slow for many things like updates. Given my win10 experience it got me thinking whether I should also move this image to the SSD not in the array. Being on the array gives me the security of data protection that comes with the array but wondering the downsides of moving it to the ssd outside the array?

Super basic question that I coiuldn’t find answer to… since this is installed via a plugin, is there any issue with rebooting the system and losing config? Or does the rclone config we add survive reboots?

Thank you! this worked for me too.

Thanks @zgo. This solved my issue… my directories were owned by nobody:users, but the permissions were wrong. Any of the folders that were 755 needed to be 777.

can you just access them via the unraid server’s iP with the port number mapped to the container?

Is it possible to run a given user script on multiple schedules? For example, I’d want one to run at array start, and weekly at say Friday at 8pm. is the only way to do this to create a second user script that either dupes the first script and set that to the second schedule, or have a second user script that just calls the script of the first?

Found answer to my own question: https://gist.github.com/auth/github/callback?return_to=https://gist.github.com/shayne/25e194e068751e281937ef68edefb99b&browser_session_id=fd34397b87999ea789b8fe352a941bd934d618392aa50b2c010b21c5cc417eff&code=5e94e3bb523a98b3e868&state=64cadd3d745b45ef88123c51d63a6fa2cf87cda1cb9c517d93b4d6768ab1462a

Thanks @dsmith44 for this container. Works great for my clients on my tailnet to access my Unraid server more securely when I’m not at home without worrying about wireguard or other clunky VPN setup! I’ve got a 2 questions about something I”m trying to accomplish: I just got Tailscale SSH setup by going into the container command line, and running “/app/tailscale up --ssh”. However, should I be running that by adding the “--ssh” command into the UP arguments of the container config to account for container restarts? Or is it sufficient that it’s done only once via command line and this will persist across container restarts? Larger problem related to #1, is that when I get Tailscale SSH running, if I SSH into my Unraid server, I”m actually connecting to the container itself instead of the Unraid host. Any way around this? I want to eliminate all this SSH key management. I think the only way to potentially do this is to figure out installing Tailscale natively into Unraid and not within a container? One thing I’d like to do is from the Unraid command line, to SSH into another server on my tailnet. Is this possible? Since tailscale is running within the container, the tailscale binary itself isn’t available to Unraid directly, so not sure if this is possible as I don’t think the tailscale magicDNS stuff is recognized at the Unraid level outside the container.

This is really just making sure you understand this that isn’t just exposing the container to your tailnet, but rather your entire Unraid server. That said, this should be expected in the way most, if not all, want tailscale to work on Unraid by installing this container anyways. As long as you are following the default configuration of your tailnet, or your customizations to your ACL config is secure, you should be fine.

Genius thank you! It's Nov 2022 and this still is required.