strike

Do this please: https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Are you on a bridge network? if so go to http://serverIP:8080/web/admin and you should be able to set up the admin user.

If you want to test on another windows machine you can just set up a vm. ISO is free to download and you don't need to buy a key to activate it.

Try adding this to smb extras under settings-SMB: domain master = yes preferred master = yes os level = 255 force user = nobody force group = users create mask = 0666 force create mode = 0666 directory mask = 0777 force directory mode = 0777 Then try again

I can't find the link where they were talking about iGPU, but here is the link to the script I mentioned. https://github.com/ahmetoner/whisper-asr-webservice/issues/93

Yes,just remove the extra parameter value and it will use the cpu. Just click edit on the container, make sure advanced view is enabled and remove it from ekstra parameters. I found an github issue some time ago talking about igpu ,but I can't remember if someone got it working or not. Will link it tomorrow, on my phone in bed right now. I also found a great script to automate things which I've been using. Haven't used it in a while, but I'll link that too tomorrow. It was working great tho at least in English.

Have you confirmed the VPN connection is up when this happens? I haven't tried NordLynx but does it auto re-connect when it loses it's connection? All VPN's loose their connection, some more freqvently than others. Sounds like it goes down and then never comes back up before a restart is forced. Have you tried changing VPN endpoint?

I don't see what I'm missing. The script does that too.. This is from the hdparm manual: -S Put the drive into idle (low-power) mode, and also set the standby (spindown) timeout for the drive. This timeout value is used by the drive to determine how long to wait (with no disk activity) before turning off the spindle motor to save power. Under such circumstances, the drive may take as long as 30 seconds to respond to a subsequent disk access, though most drives are much quicker. The encoding of the timeout value is somewhat peculiar. A value of zero means "timeouts are disabled": the device will not automatically enter standby mode. Values from 1 to 240 specify multiples of 5 seconds, yielding timeouts from 5 seconds to 20 minutes. Values from 241 to 251 specify from 1 to 11 units of 30 minutes, yielding timeouts from 30 minutes to 5.5 hours. A value of 252 signifies a timeout of 21 minutes. A value of 253 sets a vendor-defined timeout period between 8 and 12 hours, and the value 254 is reserved. 255 is interpreted as 21 minutes plus 15 seconds. Note that some older drives may have very different interpretations of these values. SO then you set the first script with a value 0 and in the unraid disk settings you set never spin down. and run it at 7am. Disks will not spin down until you run the second second script (at 1am? or something) with the correct value that (whatever value 15 min is, do the math yourself).

Btw if you're not that familiar with running script this scripts has 3 settings you can turn on/off: # ######### Settings ################## # set to "1" to enable spinning down disk if power mode is IDLE_A idle_b_spindown=1 # set to "1" to enable spinning down disk if power mode is IDLE_B idle_c_spindown=1 # set to "1" to enable spindown timer through "smartctl -s standby,241 /dev/sdb". "241" means 30 minutes advanced_spindown=0 So you want to set the fist two to 0 and the last one to 1 and just adjust the timer (241, which means 30 min) So you need to find the correct value for the timeer. Then you set up two scripts in userscripts. One to run at night and one during the day, with the timer you want. This scripts does exactly want you want.

On second thought, it would be best if you run the script I linked in my first post as it says in the description that the status isn't always right. Reporting standby while it's spinning etc. The script accounts for that.

The script has an option to do that: # set to "1" to enable spindown timer through "smartctl -s standby,241 /dev/sdb". "241" means 30 minutes advanced_spindown=0 Or you can have two scripts running just that command if you don't want the rest of the script, one at day and one at night. Just adjust the timer to what you want and add the disks. Now, why "241" means 30 min I don't know. Haven't look that one up.

That should be possible, you can maybe use this script or modify it to your needs: https://forums.unraid.net/topic/106508-advanced-disk-spindown/

Have you guys set up all the ports for all your apps in the VPN container? And remember they are now all on the same VPN network so you need to use localhost:port in your apps to get them to communicate with each other, or the IP of the VPN container. You can watch this one which explains how to do it: https://www.youtube.com/watch?v=hgcFdUIOf5M

So I figured this out. Installed the preview plugin an then I got a warning that I had to approve the exit nodes. After I did that it works. Now I have one more question, is there a way to use the docker containers DNS? I do not want to use tailscale DNS as it's super slow for me. I want to use the DNS server of my VPN container on my devices so I don't get DNS leaks.

So I finally updated to unraid 7.0.1 and enabled exit node on my VPN containers, but they do not show up as exit nodes on any of my devices. Do I need to run the preview version of the tailscale plugin for this to work? I'm running 1.78.1-t8903926f7-gc4163954e right now. Edit: I see the tailscale version on the containers are 1.80.2 but the plugin is 1.78.1

You could also look at cleanuperr to block these files: https://github.com/flmorg/cleanuperr

.lnk files are shourtcut files which usually contains a virus. If you're getting lots of them switch torrent site or block them in your torrent client. I also think there's an option in one of the recent sonarr updates to treat .lnk files as malicious files.

From the release 7.0.0 notes:

I get it, most of us already have a busy every-day life, it wasn't meant as a personal attack against you. Was just voicing my opinion that it should have it's own thread. If we had one, many users here probably would be able to help out with support when they have time. This forum in general is a perfect example of that.

Ah, nice. It wasn't when I installed it a long time ago, but then the template has been updated. Going to bed here now soon as it's 1:20 am here

It was explained in mye link in my earlier post. You need to map It in your template then use the container path in sftpgo. So in this example the host path: /mnt/user/Cameras is mapped to /Cameras in sftpgo

You should also go to the template enable advanced view top right and add this to extra parameters: --user 99:100 To run it as the correct unraid user. Or else you probably will have permission errors later on.

I will just link this post by another user in another thread, so I don't have to write it all myself, as it was just about this

By default all apps have no public access unless you open ports for them in your router or use reverse proxy or something. If you want public access it would be best to use tailscale or another VPN service. Or you can also use the very good security features in SFTPGo itself., but then it's a must to set up ssh keys and use SFTP. You can set up whitelist/black list so only certain IP can log in. Autoblock after x failed login attempts etc. But if you only want LAN access you're good to go from the start no need to configure anything. Just use your favorite (S)FTP client of choice and connect to the IP. As you see in the template FTP uses port 2121 and SFTP 2022.

It's not listed in your docker tab? Did you get a an error when installing it?