manolodf

Try forcing version 1.4.0 and see if it works for you, I believe I had the same issue when I updated the docker.

I am also getting this error after updating the docker: Update: I had to force version 1.4.0 for it to boot up. I tried 1.4.1 and also did not work, and Latest:1.4.3 as well did not work

One other thing I notice is in Unraid GUI, when I go to plugin settings, sometimes I see the nice presentation that shows your IP, email, like this: yet sometimes, I would say after a while or most of the time it shows it like this, so one does not have that Advertise as Exit Node Button, or logoff button: Is that normal behavior? Not sure if I can pinpoint when that got triggered, because I even have tailscale down currently.

I had to leave the house so I couldn’t risk a tweak but I will continue when I get back. Do you recommend going for the exit node theory out the gate or try the toggles first? I planned on the exit node first, waiting then enabling on webgui if simply enabling did not cause the issue. Then after enabling, having an active session giving each one time to fail. If you have tips on the order I am all ears Sent from my iPhone using Tapatalk

I am on Unraid 6.9.2 and began using the plugin, I followed the directions to advertise subnets (via Terminal ran: tailscale up --accept-routes --advertise-exit-node --advertise-routes=192.168.0.0/24,192.168.1.0/24) , and everything seemed to be working just fine. After leaving it alone and being satisfied with being able to access my local subnet (192.168.0.x) while remotely, and also being able to use my NAS as an exit node, I thought the job was done. What I was not expecting though is that few minutes later all of a sudden my unraid was without internet, i could not access any dockers GUI, access the Unraid GUI, and also my router seemed to not be seeing it online at all. I physically powered down the unraid, then I powered it back up thinking maybe it was an anomaly, sure enough it comes back up, my router sees my unraid, and few minutes later I am able to get into Unraid GUI, and the dockers and VMs come back up. This time a bit more nervous I just wait to see if everything is fine, and sure enough maybe 20 minutes later the same thing happens, the unraid loses all internet from the looks for things (I tried accessing it with hostname, my local IP, via tailscale IP, through tailscale, through local network, all to no avail) So now I am here asking for suggestions, help, or any tips of what could be causing it. Here are my settings: Those were the settings when the issues repeatedly took place. Since then I have just now turned off the exit node, and also set the top two to "No" t see if that changes anything. I also turned off the subnets for now on Tailscale webGUI just in case. Is there anything that stands out that I may ned to change? I have not twaked any of these in a long long time but here are my unraid Network Settings TIA for any help! Update1: With above modifications, turning off the listen on tailscale ip, and forward ip, as well as exit node disabled, and subnets disabled I have about 50min uptime, that is far more than after my reboot. I will try to make one modification per hour and see how I fare to see if I can pinpoint what is causing the crash/loss of internet issue. I also attached diagnostics. Update2: I have advertised subnets back without an issue so I am now able to access my dockers with the local IPs when I am on tailscale. So far the system has been stable. About an hour up. Remaining to test is the exit node, as well as the Tailscale IP and Forward IP settings. Those will come next, and I have a feeling it may be the exit node that was causing the system crash/offline issue. Tower-tailscale-diag-20231024-165630.zip

Awesome that got the timezone result! Maybe the ubuntu upgrade is what gave an error when doing "pip3 install requests" that used to work and had to change it. But definitely getting the desired timezone! Thanks!

I tried adding the TZ Variable within unraid and applied, and same result, still showing UTC time for me when running python script.

I wanted to see if you could help me get my local Unraid Time within code-server, or to set a time. I tried mapping /etc/localtime and that did not seem to work, and the timedatectl did not seem to work also. Is there an argument or parameter I can pass through to assign my timezone so that when testing a python script within code-server it has my correct timezone instead of UTC?

Not sure if you have seen the Linuxserver version of code-server. I think that is what the other user was referring to in terms of a password on a splash screen. I just switched to yours because it’s frankly better since I can run all extensions but the password protection would be a bonus Sent from my iPhone using Tapatalk

I think he meant when pulling up the GUI to enter a password of some sort like some of the the Open-VSCode ones do. What is the passkey for in the config by the way, I did think that was for some sort of GUI Passcode to be able to access?

Have you guys had any success with any of the more recent versions? I just tried 6.11.5 stable and had to revert again to 6.9.2 to get my Time Machine backups working as they had for a decade. I had issues at 6.10.3, downgraded, then tried 6.11.5, and had to downgrade again. Under 6.11.5 I was able to get the initial backup to work once (deleting my sparsebundle) even though I did not want to do that, but the incrementals failed, so eventually I went back and am hoping they finally resolve this once and for all without any necessary tweaks except having the share be a timemachine share.

The thing is it may backup once but the incrementals tend to hang or fail. If you want flawless Time Machine backups downgrade to 6.9.2 until they resolve the issue. I am on the same boat, I have tried 6.10.3 and 6.11.5 and have had to downgrde because in those versions the Time Machine backups were broken, once downgrading they work great again. This is with machines on Catalina, Monterey and Ventura, prior to my upgrade to 6.10.3 Time machines backups had worked for 10 years without a problem on Unraid. I would love to be on the latest Unraid Stable, but Time Machine backups of my computers is up there on the reasons I have Unraid in the first place, and never really heard of the survey so my vote was not in there as I assume many people's that are perhaps not that active.

What version did you upgrade from? I had to revert back to 6.9.2 again to get Time Machine backups to work as they had before. I attempted 6.10.3, and 6.11.5 and both had issues so I had to revert back.

I see, ok so maybe those are few and far between, but I promise you prior to 6.10 TM backups were amazing, I had hourly backups for I believe at least 10yrs, since around 2012 when I got my first mac. All of a sudden this broke in 6.10 and is still not resolved (I tried 6.11.5, but I am about to revert back to 6.9.2 once again) Update: Downgraded to 6.9.2 and Time Machine Backups working great again instantly upon downgrade, I do not foresee incrementals having an issue either but will update if so.

Not sure if it would help diagnose, but I think many of us that have issues have had Unraid for a long time, can you try upgrading from 6.9.2 to a newer version and see if you get the same problems? For some reason I have seen a few people in the forums that say they created this time machine on 6.10.3 or above and have something working, so perhaps attempting on an older version then upgrading to see if you can replicate the issues?

I also completely agree with this. I have been fumbling around until I found this post, I went to 6.10.3, had to go back to 6.9.2, but I do want some of the newer unraid features, so I tired yesterday to go to 6.11.5, and again my time machines do not work, when they had been working for a decade since Unraid's beginnings. I also would prefer to not have to hack my way to get them to work, since it was built in for so so long, and I had a perfect Time Capsule at home for my 4+ macs to backup via timemachine to flawlessly.

So a bit of an update. I downgraded from 6.10.3 (That broke time machine backups) back to 6.9.2 and my Time Machine went back to working flawlessly on my unraid as it had for about 10 years prior without any need for any docker. I decided to wait a while, so after several months I decided to give 6.11.5 a shot to see if the issues were perhaps resolved. I upgraded yesterday and again the time machine issues came back just like when I upgraded to 6.10.3. I do not want to miss out on new features of Unraid, nor be on an older version for various reasons, but Time Machine backups are super important to me as all my mac devices back up to it as they have since the early years of Unraid.

So after downgrading to 6.9.2 from 6.10.3 (Time Machine backups stopped working for me after upgrading to 6.10.3) and having my Time Machine backups work again for a few months I decided to try 6.11.5, and once again the issues arise. I can connect to the share manually in my mac but the time machine cannot connect to disk when running. This exact same behavior happened last time, and when I downgraded to 6.9.2 it started working without any issue again. I have created new users without any change, I have not created a new share as I have had this share for over a decade working just fine, and worked in 6.9.x, while downgrading is an option I do not want to lose on some of the features of unraid going forward, but my time machine backups are very important to me.

I had to downgrade to 6.9.2 to get my time machine backups working again from 6.10.3, has anyone had luck with todays release of 6.11.1 with their time machine backups working like before?

I downgraded right now to 6.9.2 and my Time Machine on all my Macs resumed without any issue. I will attempt to upgrade to 6.11 after these backups continue for a couple of days and see if it keeps working. I hope it does because I enjoyed for better part of a decade to just get home and have my Macs back themselves up to my simulated "Time Capsule"

I also got hit by this on upgrading. I just realized my computers stopped being able to backup to time machine on Sept 10 when I updated to 6.10.3. Has anyone seen any benefit of updating to 6.11?

Has anyone had any luck with the Sym Links?

I installed the metadata, its pretty cool! How would you recommend I do a write test to cache drive? When I was transferring the appdata from array to cache, well my dockers were off, so I could not really see that. Do you recommend a different test I could setup to see the write speed? Do you think there is something in bios I need to do to improve on this? My previous 256gb NVMe M.2 SSD did not have any issues on the speed department that I noticed.

Yes correct, same thing, but I guess I was looking more for the specific command if possible to extract just one folder (to keep permissions as mentioned)

Is there a way to restore a backup of only one docker? It seems my Deluge restore got corrupted at some point. Deluge would not recognize my password, it was reset to default password, as well as some plugins were not working. So i wanted to only restore that one hoping to get it back to how it was. I know on a previous restore it was intact.