dodgypast

Updated fine.

Don't know where it will take me, I installed the leaked DEV version and I just used the insider program menu in settings to add it to the dev channel. I'll see what happens over the next couple of days to see if it gets updated to match up with the insider release. I am wondering if the leaked build was coded to ignore TPM requirements if it detected it was being installed on a QEMU platform. However from what I've gleaned MS seem to be pushing people to upgrade Windows 10 installations to Windows 11 rather than offering a Windows 11 insider program ISO. hopefully @limetech will be working behind the scenes to let us know if / how they'll be supporting TPM going forward. Bearing in mind I can't find anything on Level 1 tech's vfio forum I wouldn't expect anything quickly.

That version doesn't require TMP going forward from the build that will be released next week it will be required: https://www.thurrott.com/windows/windows-11/252333/how-to-get-started-testing-windows-11

Thanks a lot.

I want to pass an environment variable to the Komga docker to limit it's memory usage: JAVA_TOOL_OPTIONS=-Xmx2g The relevant variable page is here for komga: https://komga.org/installation/docker.html#user-group-identifiers Sadly I haven't been able to understand how to use the following part to enter this and google is failing me. Unfortunately this part is TBD in the manual: https://wiki.unraid.net/Manual/Docker_Management#Environment_Variables

I use 8080 for something else. I did some digging and this worked: server { listen 443 ssl; listen [::]:443 ssl; server_name PRIVATE include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; location / { proxy_pass http://192.168.1.153:9999/; proxy_buffering off; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_http_version 1.1; proxy_no_cache $cookie_session; } }

Trying to set this up with lets encrypt via duckdns. but I'm getting a 502 Bad Gateway error. Anyone any ideas how to fix this?

Got it working by using the following in the rule section of the private option: (sec=sys,rw,insecure,all_squash,anongid=1000,anonuid=1000)

I'm sharing a share via nfs to my linux VM, but I've been having ownership issues that I'd like to overcome. The /etc/exports that UNRAID generates is: "/mnt/user/MyMedia" -async,no_subtree_check,fsid=100 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) I tried editing it with nano to: "/mnt/user/MyMedia" -async,no_subtree_check,fsid=100 *(sec=sys,rw,insecure,all_squash,anongid=1000,anonuid=1000) But after rebooting it was reverted back to the original. Anyone know how I can make the edit stick, or achieve the same effects through the gui?

Working for me as well, many thanks.

It worked after the second. root@Tower:~# docker exec -it binhex-qbittorrentvpn bash -c 'sed -i -e "s~--pull-filter ignore\s.dhcp-option\sDNS6.\s~~g" /root/openvpn.sh' Error response from daemon: Container ce7a38e0b3115332106a1687c9c83bdcb3cd3f10f8d3e8fdba76ae86543e59c4 is not running root@Tower:~# docker exec -it binhex-qbittorrentvpn bash -c 'sed -i -e "s~--pull-filter ignore\s.dhcp-option\sDNS6.\s~~g" /root/openvpn.sh' root@Tower:~# docker exec -it binhex-qbittorrentvpn bash -c 'sed -i -e "s~--pull-filter ignore\s.redirect-gateway\sipv6.\s~~g" /root/openvpn.sh' Error response from daemon: Container ce7a38e0b3115332106a1687c9c83bdcb3cd3f10f8d3e8fdba76ae86543e59c4 is not running root@Tower:~# docker exec -it binhex-qbittorrentvpn bash -c 'sed -i -e "s~--pull-filter ignore\s.redirect-gateway\sipv6.\s~~g" /root/openvpn.sh' Thanks for your support.

Didn't like that either: logfile2

I tried latest again and it didn't work, back to 4.2.5-1-01 and it's fine. I'll try and attach log files when I have a bit of time later. Edit: No log file was generated in my /appdata/binhex-qbittorrentvpn/qBittorrent/config folder. But I got this from my logs: logfile

I'm in the same boat.

Any advice as to how to get this working with mullvad VPN would be really appreciated. Edit: I figured it out. Select custom for the VPN Username and password are both your user number. Put unzip the files you generate on the Mullvad site and put them in \appdata\binhex-qbittorrentvpn\openvpn Rename the .conf file as .opvn That got me up and running.

I've actually fixed it by removing the two isos I still had added ( Virt and Windows ) and switching the vdisk location to manual from auto.

Unfortunately it's been failing for me. The line below seems to be the error, though I've inclluded the full log file. /tmp/vmbackup/scripts/default/user-script.sh: line 398: vdisk_types["$vdisk_path"]: bad array subscript 2020-01-22 15:14:16 Starting VM Backup for default config. 2020-01-22 15:14:16 PID: 28052 2020-01-22 15:14:16 User script copied to /tmp/vmbackup/scripts/default/user-script.sh 2020-01-22 15:14:16 Running command: '/tmp/vmbackup/scripts/default/user-script.sh' >> '/tmp/vmbackup/scripts/default/20200122_151416_user-script.log' 2>&1 2020-01-22 15:14 information: official_script_name is user-script.sh. script file's name is user-script.sh. script name is valid. continuing. 2020-01-22 15:14 information: enabled is 1. script is enabled. continuing. 2020-01-22 15:14 information: backup_location is /mnt/user/Backup. this location exists. continuing. 2020-01-22 15:14 information: backup_location is /mnt/user/Backup. this location is writable. continuing. 2020-01-22 15:14 information: timestamp_files is 1. timestamp will be added to backup files. 2020-01-22 15:14 information: /mnt/user/Backup/logs/ exists. continuing. 2020-01-22 15:14 information: log_file_subfolder is /mnt/user/Backup/logs/. this location exists. continuing. 2020-01-22 15:14 information: log_file_subfolder is /mnt/user/Backup/logs/. this location is writable. continuing. 2020-01-22 15:14 Start logging to log file. 2020-01-22 15:14 information: send_notifications is 1. notifications will be sent. 2020-01-22 15:14 information: only_send_error_notifications is 0. normal notifications will be sent if send_notifications is enabled. 2020-01-22 15:14 information: unRAID VM Backup script is starting. Look for finished message. 2020-01-22 15:14 information: keep_log_file is 1. log files will be kept. 2020-01-22 15:14 information: number_of_log_files_to_keep is 1. this is probably a sufficient number of log files to keep. 2020-01-22 15:14 information: backup_all_vms is 0. only vms listed in vms_to_backup will be backed up. 2020-01-22 15:14 information: use_snapshots is 0. vms will not be backed up using snapshots. 2020-01-22 15:14 information: kill_vm_if_cant_shutdown is 0. vms will not be forced to shutdown if a clean shutdown can not be detected. 2020-01-22 15:14 information: set_vm_to_original_state is 1. vms will be set to their original state after backup. 2020-01-22 15:14 information: number_of_days_to_keep_backups is 0. backups will be kept indefinitely. be sure to set number_of_backups_to_keep to keep backups storage usage down. 2020-01-22 15:14 information: number_of_backups_to_keep is 2. this is probably a sufficient number of backups to keep. 2020-01-22 15:14 information: compress_backups is 0. backups will not be compressed. 2020-01-22 15:14 information: use_snapshots disabled, not adding snapshot_extension to vdisk_extensions_to_skip. 2020-01-22 15:14 information: snapshot_fallback is 0. snapshots will fallback to standard backups. 2020-01-22 15:14 information: pause_vms is 0. vms will be shutdown for standard backups. 2020-01-22 15:14 information: enable_reconstruct_write is 0. reconstruct write will not be enabled by this script. 2020-01-22 15:14 information: compare_files is 0. files will not be compared after backups. 2020-01-22 15:14 information: backup_xml is 1. vms will have their xml configurations backed up. 2020-01-22 15:14 information: backup_nvram is 1. vms will have their nvram backed up. 2020-01-22 15:14 information: backup_vdisks is 1. vms will have their vdisks backed up. 2020-01-22 15:14 information: start_vm_after_backup is 0. vms will not be started following successful backup. 2020-01-22 15:14 information: start_vm_after_failure is 0. vms will not be started following an unsuccessful backup. 2020-01-22 15:14 information: disable_delta_sync is 0. rsync will be used to perform delta sync backups. 2020-01-22 15:14 information: rsync_only is 0. cp will be used when applicable. 2020-01-22 15:14 information: actually_copy_files is 1. files will be copied. 2020-01-22 15:14 information: clean_shutdown_checks is 20. this is probably a sufficient number of shutdown checks. 2020-01-22 15:14 information: seconds_to_wait is 30. this is probably a sufficient number of seconds to wait between shutdown checks. 2020-01-22 15:14 information: keep_error_log_file is 1. error log files will be kept. 2020-01-22 15:14 information: number_of_error_log_files_to_keep is 10. this is probably a sufficient error number of log files to keep. 2020-01-22 15:14 information: started attempt to backup Windows 10 to /mnt/user/Backup 2020-01-22 15:14 information: Windows 10 can be found on the system. attempting backup. 2020-01-22 15:14 information: removing old local Windows 10.xml. removed 'Windows 10.xml' 2020-01-22 15:14 information: creating local Windows 10.xml to work with during backup. 2020-01-22 15:14 information: /mnt/user/Backup/Windows 10 exists. continuing. /tmp/vmbackup/scripts/default/user-script.sh: line 398: vdisk_types["$vdisk_path"]: bad array subscript 2020-01-22 15:14 information: finished attempt to backup Windows 10 to /mnt/user/Backup. 2020-01-22 15:14 information: cleaning out logs over 1. 2020-01-22 15:14 information: removed '/mnt/user/Backup/logs/20200122_1505_unraid-vmbackup.log'. 2020-01-22 15:14 information: cleaning out error logs over 10. find: '/mnt/user/Backup/logs/*unraid-vmbackup_error.log': No such file or directory 2020-01-22 15:14 information: did not find any error log files to remove. 2020-01-22 15:14 Stop logging to log file. 2020-01-22 15:14:17 Removed: /tmp/vmbackup/scripts/default/user-script.sh 2020-01-22 15:14:17 Removed: /tmp/vmbackup/scripts/default.pid

Spaceinvaderone has a video addressing this:

Yeah, I checked the logs for sonarr and the authentication failures seemed to start around the same time the docker updated. It's made me think it's a docker problem rather than I've been hacked. Anyway to temporarily downgrade to the prior version? Edit: Deleted my .conf file and manged to log in with the default password, but now realised that the version change hasn't been whiletlisted so I definitely need to revert back to the old version. Edit2: Figured out how to revert to the old version ( 4.19 ). Copied the old .conf file in and it worked, so something about the upgrade to 4.20 seems to be breaking the webUI login, though that can be fixed by deleting your .conf and starting again.

Anyone else suddenly unable to log into qbittorrent? Is there any way I can reset the log in details?