whiter

Update. I got it to work by reading through the plugin code and adding ALLOW_FUNNEL="1" in /boot/config/plugins/tailscale/tailscale.cfg Not sure why this is disabled by default in such a hidden spot. But at least it's resolved for now.

Hiya. I've updated the tailscale plugin to the latest version, and noticed my Funnel had disappeared. When I try to recreate it, it works for a few seconds, but then it is automatically changed into a Serve, which is not publicly accessible. I note the following line appearing in /var/log/tailscale-utils.log every time I set up the Funnel: Tailscale funnel is enabled, but config does not allow it, resetting serve config Unfortunately it gives no hint of which config it is talking about, and I can't find anything. Where should I be looking?

For those coming across this in 2025: This is the correct solution if your "Preferences.xml" file is 0 bytes in size. You will find the "Preferences.xml" in the "/Plex-Media-Server/Library/Application Support/Plex Media Server/" subfolder of whatever is set as your 'appdata' Share, which should be listed on the Share tab of your Unraid web console. If you have no backup of your Preferences.xml, simply replace it with a file that says nothing but: <?xml version="1.0" encoding="utf-8"?> <Preferences /> I used 'vi' in the terminal window: vi /mnt/user/appdata/Plex-Media-Server/Library/Application\ Support/Plex\ Media\ Server/Preferences.xml Once saved, restart the docker container and it should start working again.

For anyone stumbling upon this in 2025. I got this to work on my Starlink super easy now by doing the following: Register a free Tailscale account. Install the official Tailscale plugin from the Apps section in my Unraid web gui. It's called "Tailscale (Plugin)". Don't pick any of the other options. Once the plugin is up and running open the Unraid terminal and issue the following command: "tailscale funnel --bg 32400" (If your plex doesn't listen on the default port of 32400, change it appropriately.) and follow any prompts it gives you. That's it. Easypeasy lemon squeezy. Simply proceed to connect to the URL Tailscale gave you to open your Plex. E.g. "https://yourunraidserver.splur-splork.ts.net/" Note that the 'funnel' command makes the Plex publicly available on the internet. It will still require Plex authentication of course. If you don't issue the 'funnel' command the Plex will still be available, but only within the VPN, so to devices that have Tailscale running on them and are authorised.

Ah so the file appears on one of the individual /mnt/diskX's but not the aggregate /mnt/user which only shows folders. Weird flex but OK

I was messing around a bit working directly in a terminal on the unraid filesystem. I copied a file to /mnt/user/ wondering what would happen. Half expecting the file to sit amongst the array folders. But when doing an 'ls' no files are present, only the configured shares. So... now I'm curious. What happened to the file? I mean, it doesn't need to be there and it's just an academical exercise for my own learning, but Is there any way I can still make it visible? Or does anything copied directly in this place make it effectively go to /dev/null ?

Users created in the Unraid user interface are added to /etc/passwd. Files uploaded via an 'official' sharing mechanism like SMB honour the Linux file permissions and create new files using the user ID and group ID as assigned to the logged in user in the /etc/passwd file. Linux users for accounts other than root are very much used. Running docker, and a loading a container, is WAY overkill for a built-in core capability of the OS. I've no intention to overcomplicate things, and beef up the CPU and memory of the system hosting nothing but my backup drives, for the sake of running a basic capability that it already has but is just made extra difficult to enable. Keep It Stupid Simple.

I've no idea why they have made it so hard to do this. I'm the single and only user of my unraid setup and my main mode of transferring data is via rsync & SCP. I *must* be able to have a working user that is not root to have SSH access for this even when the system unexpectedly reboots. So after a bunch of trial and error I've come up with the expanded version of the /boot/config/go script below. Shared here in case it helps somebody else who's been struggling with this omission. The user 'USERNAME' was created and password set using the web GUI. All you'd need to do is change the word USERNAME to your actual, well... username, and double check the 1000:100 user:group numbers are the same for your situation. If this messes up your unraid config somehow, it's non-destructive. Reverting to default settings, because you just want to or because you messed up, is a matter of opening a terminal via the web gui or on the physical console and removing everything but the first & last line of the /boot/config/go file again. #!/bin/bash # Make homedir mkdir /USERNAME chown USERNAME:users /USERNAME # Set homedir and assign shell cat /etc/passwd | sed -e s/USERNAME.*false/"USERNAME:x:1000:100:User description:\/USERNAME:\/bin\/bash"/ > /etc/passwd.1 mv /etc/passwd.1 /etc/passwd # Ensure user profile doesn't try to send you to the root homedir upon login cat /etc/profile | sed -e s/"export HOME=\/root"/"export HOME=\/\`whoami\`"/ > /etc/profile.1 mv /etc/profile.1 /etc/profile # Allow all users to SSH in. # (Alternatively append your specific desired username after 'root', separated with a space: # i.e. "AllowUsers root USERNAME") cat /etc/ssh/sshd_config | sed -e s/"AllowUsers root"/"# AllowUsers root"/ > /etc/ssh/sshd_config.1 mv /etc/ssh/sshd_config.1 /etc/ssh/sshd_config /etc/rc.d/rc.sshd reload # Start the Management Utility /usr/local/sbin/emhttp &