ptr78

I have experiencing very slow Unraid WebGUI speeds lately. I checked the log and there are these two lines recurring: Oct 27 08:54:51 Tower nginx: 2020/10/27 08:54:51 [crit] 5843#5843: *1992 connect() to unix:/var/tmp/qBittorrentVPN.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.XXX.YYY, server: , request: "GET /dockerterminal/qBittorrentVPN/token HTTP/1.1", upstream: "http://unix:/var/tmp/qBittorrentVPN.sock:/token", host: "tower", referrer: "http://tower/dockerterminal/qBittorrentVPN/" Oct 27 08:54:51 Tower nginx: 2020/10/27 08:54:51 [crit] 5843#5843: *2050 connect() to unix:/var/tmp/qBittorrentVPN.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.XXX.YYY, server: , request: "GET /dockerterminal/qBittorrentVPN/ws HTTP/1.1", upstream: "http://unix:/var/tmp/qBittorrentVPN.sock:/ws", host: "tower" I also got the following notification email form the unraid server: The email title: cron for user root /usr/bin/run-parts /etc/cron.daily 1> /dev/null The email contents: error: error setting owner of /var/log/nginx/error.log to uid 0 and gid 0: Operation not permitted I have not changed the docker config for at least 6 months. Any ideas what might cause this? All help truly appreciated.

There is a configuration item that forces a check after a download has completed. It is disabled by default. Enabling it prevents the above issue. Config item: Advanced\RecheckOnCompletion=true

Good comments from AirVPN providers regarding wireguard: https://airvpn.org/forums/topic/24292-wireguard/?tab=comments#comment-104315

Hi, I have a wireguard remote tunneled access up and running and it works beautifully. However, how can I configure the wireguard client so that it would not use the tunnel for local addressed (192.168.1.0/24)? I thought that it would have been discussed already but I didn't find it. So, is there a way to exclude the local packets to be sent to the tunnel? The client is Windows10 computer. Any help very much appreciated, thank you! >>> Found a solution (kind of) with more googling. Seems that it is a Wireguard Windows client issue. https://williamjshipman.wordpress.com/2019/12/31/wireguard-vpn-on-windows/

A newbie question. What is meant by pass through here? That is, I have a disk mounted by UD and it is used by few dockers via path "/mnt/disks/.." Is there an issue or can I continue using it like this? I have not enabled the pass through for the disk in UD.

OK. Has it been figured out how to do the password change with the least amount of hassle?

It seems that there a lot issues with the latest update. Have they been resolved, so is it OK to update? Or should one wait for a new update? Thank you!

Thank you for the help! Installed Emby instead.

Thank you for this info!

Hi, Didn't get any replies in the CA Appdata Backup plugin thread, so trying here. Any ideas what might cause the issue described on the link below? https://forums.unraid.net/topic/61211-plugin-ca-appdata-backup-restore-v2/page/15/?tab=comments#comment-782926 Any help really appreciated!

Yes, totally understandable. Thank you for the fast reply!

A really newbie question.. I uninstalled this Plex docker but the uninstall did not delete the appdata/plex directory. Is it OK for just delete that directory or should it be done some other/cleaner way?

Is there an option with the "Remote tunneled access" to restrict the access to the Unraid LAN? That is, I would like to make a setup with only IP tunneling/forwarding without an access to the LAN. Is this possible?

Hi, first of all, thank you for this excellent plugin! The plugin works very well except with the binhex's qBittorrentVPN docker. That is, let's assume I have active downloads in the docker and it is stopped when a backup is started. All the previously active downloads are restarted from the beginning after the docker is restarted. If I just manually stop and restart the qBittorrentVPN docker and there are active downloads, the active downloads' state is checked as they should and after the the downloads continue where they were before the stoppage of the docker. So, does the CA Backup plugin stop the dockers in some different way compared to a manual stoppage or what might cause this? I have tested this several times with the identical results.