OmegaXis

I am unable to access unraid connect. from everything i can tell, all the connections are correct, everything on my server is correct. but i am gettnig the following api errors when i attempt to make the connections { "data": null, "errors": [ { "message": "The CORS policy for this site does not allow access from the specified Origin." } ] }

This release seems really rushed given some of the bugs that are appearing

+1

From what i have seen, KVM is more than capable of handling anything vbox handles. I actually find the kvm interface in unraid easier to use than vbox these days

so would it be possible to use authelia and authy instead of duo?

Been thinking about deploying authelia for a while now, can i ask why not use Authy? I have both but want to know if there is a particular reason to avoid authy.

I have 3 disks that always refuse to export properly, even though the plugin says otherwise. Is there something I am missing?

So i am a bit confused about what is wrong with my config. Any help is appreciated. 2023-06-05 13:42:44 Start logging to log file. 2023-06-05 13:42:44 information: send_notifications is 1. notifications will be sent. 2023-06-05 13:42:44 information: only_send_error_notifications is 0. normal notifications will be sent if send_notifications is enabled. 2023-06-05 13:42:44 information: keep_log_file is 1. log files will be kept. 2023-06-05 13:42:44 information: number_of_log_files_to_keep is 1. this is probably a sufficient number of log files to keep. 2023-06-05 13:42:44 information: enable_vm_log_file is 0. vm specific logs will not be created. 2023-06-05 13:42:44 information: backup_all_vms is 1. vms_to_backup will be ignored. all vms will be backed up. 2023-06-05 13:42:44 information: use_snapshots is 0. vms will not be backed up using snapshots. 2023-06-05 13:42:44 information: kill_vm_if_cant_shutdown is 0. vms will not be forced to shutdown if a clean shutdown can not be detected. 2023-06-05 13:42:44 information: set_vm_to_original_state is 1. vms will be set to their original state after backup. 2023-06-05 13:42:44 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. 2023-06-05 13:42:44 information: number_of_backups_to_keep is 0. an infinite number of backups will be kept. be sure to set number_of_days_to_keep_backups to keep backups storage usage down. 2023-06-05 13:42:44 information: inline_zstd_compress is 1. vdisk images will be inline compressed but will not be compared afterwards or post compressed. 2023-06-05 13:42:44 information: zstd_level is 3. 2023-06-05 13:42:44 information: zstd_threads is 2. 2023-06-05 13:42:44 information: include_extra_files is 0. extra files and folders will not be included in the backup. 2023-06-05 13:42:44 information: use_snapshots disabled, not adding snapshot_extension to vdisk_extensions_to_skip. 2023-06-05 13:42:44 information: snapshot_fallback is 0. snapshots will fallback to standard backups. 2023-06-05 13:42:44 information: pause_vms is 0. vms will be shutdown for standard backups. 2023-06-05 13:42:44 information: enable_reconstruct_write is 1. reconstruct write will be enabled during the backup. 2023-06-05 13:42:44 information: backup_xml is 1. vms will have their xml configurations backed up. 2023-06-05 13:42:44 information: backup_nvram is 1. vms will have their nvram backed up. 2023-06-05 13:42:44 information: backup_vdisks is 1. vms will have their vdisks backed up. 2023-06-05 13:42:44 information: start_vm_after_backup is 0. vms will not be started following successful backup. 2023-06-05 13:42:44 information: start_vm_after_failure is 0. vms will not be started following an unsuccessful backup. 2023-06-05 13:42:44 information: disable_delta_sync is 0. rsync will be used to perform delta sync backups. 2023-06-05 13:42:44 information: rsync_only is 0. cp will be used when applicable. 2023-06-05 13:42:44 information: actually_copy_files is 1. files will be copied. 2023-06-05 13:42:44 information: clean_shutdown_checks is 20. this is probably a sufficient number of shutdown checks. 2023-06-05 13:42:44 information: seconds_to_wait is 30. this is probably a sufficient number of seconds to wait between shutdown checks. 2023-06-05 13:42:44 information: keep_error_log_file is 1. error log files will be kept. 2023-06-05 13:42:44 information: number_of_error_log_files_to_keep is 10. this is probably a sufficient error number of log files to keep. 2023-06-05 13:42:44 information: started attempt to backup flashman, lasermanex, Numbermanexe, Stoneman, bass, virtualmin, Glyde, Macinabox BigSur to /mnt/user/VMBACKUPS 2023-06-05 13:42:44 information: Reconstruct write enabled. 2023-06-05 13:42:44 information: flashman can be found on the system. attempting backup. 2023-06-05 13:42:44 information: creating local flashman.xml to work with during backup. 2023-06-05 13:42:44 information: /mnt/user/VMBACKUPS/flashman does not exist. creating it. 2023-06-05 13:42:44 information: extension for /mnt/user/isos/virtio-win-0.1.190-1.iso on flashman was found in vdisks_extensions_to_skip. skipping disk. 2023-06-05 13:42:44 information: skip_vm_shutdown is false. beginning vm shutdown procedure. 2023-06-05 13:42:44 information: flashman is running. vm desired state is shut off. 2023-06-05 13:42:46 information: performing 20 30 second cycles waiting for flashman to shutdown cleanly. 2023-06-05 13:42:46 information: cycle 1 of 20: waiting 30 seconds before checking if the vm has entered the desired state. 2023-06-05 13:43:16 information: flashman is shut off. vm desired state is shut off. can_backup_vm set to y. 2023-06-05 13:43:16 information: actually_copy_files is 1. 2023-06-05 13:43:16 information: can_backup_vm flag is y. starting backup of flashman configuration, nvram, and vdisk(s). 2023-06-05 13:43:16 information: copy of flashman.xml to /mnt/user/VMBACKUPS/flashman/20230605_1342_flashman.xml complete. 2023-06-05 13:43:16 information: copy of /etc/libvirt/qemu/nvram/0cdc1d3a-fd5f-018f-b281-4c709a5044bb_VARS-pure-efi.fd to /mnt/user/VMBACKUPS/flashman/20230605_1342_0cdc1d3a-fd5f-018f-b281-4c709a5044bb_VARS-pure-efi.fd complete. 2023-06-05 13:43:16 information: extension for /mnt/user/isos/virtio-win-0.1.190-1.iso on flashman was found in vdisks_extensions_to_skip. skipping disk. 2023-06-05 14:00:59 information: copy of /mnt/user/domains/Windows Server 2016/vdisk1.img to /mnt/user/VMBACKUPS/flashman/20230605_1342_vdisk1.img.zst complete. 2023-06-05 14:00:59 information: backup of /mnt/user/domains/Windows Server 2016/vdisk1.img vdisk to /mnt/user/VMBACKUPS/flashman/20230605_1342_vdisk1.img.zst complete. 2023-06-05 14:00:59 information: the extensions of the vdisks that were backed up are img. 2023-06-05 14:00:59 information: vm_state is shut off. vm_original_state is running. starting flashman. 2023-06-05 14:01:05 information: backup of flashman to /mnt/user/VMBACKUPS/flashman completed. 2023-06-05 14:01:05 information: number of days to keep backups set to indefinitely. 2023-06-05 14:01:05 information: number of backups to keep set to infinite. 2023-06-05 14:01:05 information: removing local flashman.xml. 2023-06-05 14:01:05 information: lasermanex can be found on the system. attempting backup. 2023-06-05 14:01:05 information: creating local lasermanex.xml to work with during backup. 2023-06-05 14:01:05 information: /mnt/user/VMBACKUPS/lasermanex does not exist. creating it. 2023-06-05 14:01:05 information: extension for /mnt/user/isos/ubuntu-22.04-live-server-amd64.iso on lasermanex was found in vdisks_extensions_to_skip. skipping disk. 2023-06-05 14:01:05 information: skip_vm_shutdown is false. beginning vm shutdown procedure. 2023-06-05 14:01:05 information: lasermanex is running. vm desired state is shut off. 2023-06-05 14:01:05 information: performing 20 30 second cycles waiting for lasermanex to shutdown cleanly. 2023-06-05 14:01:05 information: cycle 1 of 20: waiting 30 seconds before checking if the vm has entered the desired state. 2023-06-05 14:01:35 information: lasermanex is shut off. vm desired state is shut off. can_backup_vm set to y. 2023-06-05 14:01:35 information: actually_copy_files is 1. 2023-06-05 14:01:35 information: can_backup_vm flag is y. starting backup of lasermanex configuration, nvram, and vdisk(s). 2023-06-05 14:01:35 information: copy of lasermanex.xml to /mnt/user/VMBACKUPS/lasermanex/20230605_1342_lasermanex.xml complete. 2023-06-05 14:01:35 information: copy of /etc/libvirt/qemu/nvram/0963b0b4-8fad-2ff7-461a-367f15356126_VARS-pure-efi.fd to /mnt/user/VMBACKUPS/lasermanex/20230605_1342_0963b0b4-8fad-2ff7-461a-367f15356126_VARS-pure-efi.fd complete. 2023-06-05 14:03:25 information: copy of /mnt/user/domains/lasermanex/vdisk1.img to /mnt/user/VMBACKUPS/lasermanex/20230605_1342_vdisk1.img.zst complete. 2023-06-05 14:03:25 information: backup of /mnt/user/domains/lasermanex/vdisk1.img vdisk to /mnt/user/VMBACKUPS/lasermanex/20230605_1342_vdisk1.img.zst complete. 2023-06-05 14:03:25 information: extension for /mnt/user/isos/ubuntu-22.04-live-server-amd64.iso on lasermanex was found in vdisks_extensions_to_skip. skipping disk. 2023-06-05 14:03:25 information: the extensions of the vdisks that were backed up are img. 2023-06-05 14:03:25 information: vm_state is shut off. vm_original_state is running. starting lasermanex. 2023-06-05 14:03:27 information: backup of lasermanex to /mnt/user/VMBACKUPS/lasermanex completed. 2023-06-05 14:03:27 information: number of days to keep backups set to indefinitely. 2023-06-05 14:03:27 information: number of backups to keep set to infinite. 2023-06-05 14:03:27 information: removing local lasermanex.xml. 2023-06-05 14:03:27 information: Numbermanexe can be found on the system. attempting backup. 2023-06-05 14:03:27 information: creating local Numbermanexe.xml to work with during backup. 2023-06-05 14:03:27 information: /mnt/user/VMBACKUPS/Numbermanexe does not exist. creating it. 2023-06-05 14:03:27 information: extension for /mnt/user/isos/virtio-win-0.1.190-1.iso on Numbermanexe was found in vdisks_extensions_to_skip. skipping disk. 2023-06-05 14:03:27 information: skip_vm_shutdown is false. beginning vm shutdown procedure. 2023-06-05 14:03:27 information: Numbermanexe is running. vm desired state is shut off. 2023-06-05 14:03:31 information: performing 20 30 second cycles waiting for Numbermanexe to shutdown cleanly. 2023-06-05 14:03:31 information: cycle 1 of 20: waiting 30 seconds before checking if the vm has entered the desired state. 2023-06-05 14:04:01 information: Numbermanexe is shut off. vm desired state is shut off. can_backup_vm set to y. 2023-06-05 14:04:01 information: actually_copy_files is 1. 2023-06-05 14:04:01 information: can_backup_vm flag is y. starting backup of Numbermanexe configuration, nvram, and vdisk(s). 2023-06-05 14:04:01 information: copy of Numbermanexe.xml to /mnt/user/VMBACKUPS/Numbermanexe/20230605_1342_Numbermanexe.xml complete. 2023-06-05 14:04:01 information: copy of /etc/libvirt/qemu/nvram/6f69c2e7-1e84-8a67-e6e5-177b7fc67135_VARS-pure-efi.fd to /mnt/user/VMBACKUPS/Numbermanexe/20230605_1342_6f69c2e7-1e84-8a67-e6e5-177b7fc67135_VARS-pure-efi.fd complete. 2023-06-05 14:09:05 information: copy of /mnt/user/domains/Numbermanexe/vdisk1.img to /mnt/user/VMBACKUPS/Numbermanexe/20230605_1342_vdisk1.img.zst complete. 2023-06-05 14:09:05 information: backup of /mnt/user/domains/Numbermanexe/vdisk1.img vdisk to /mnt/user/VMBACKUPS/Numbermanexe/20230605_1342_vdisk1.img.zst complete. 2023-06-05 14:09:05 information: extension for /mnt/user/isos/virtio-win-0.1.190-1.iso on Numbermanexe was found in vdisks_extensions_to_skip. skipping disk. 2023-06-05 14:09:05 information: the extensions of the vdisks that were backed up are img. 2023-06-05 14:09:05 information: vm_state is shut off. vm_original_state is running. starting Numbermanexe. 2023-06-05 14:09:08 information: backup of Numbermanexe to /mnt/user/VMBACKUPS/Numbermanexe completed. 2023-06-05 14:09:08 information: number of days to keep backups set to indefinitely. 2023-06-05 14:09:08 information: number of backups to keep set to infinite. 2023-06-05 14:09:08 information: removing local Numbermanexe.xml. 2023-06-05 14:09:08 information: Stoneman can be found on the system. attempting backup. 2023-06-05 14:09:09 information: creating local Stoneman.xml to work with during backup. 2023-06-05 14:09:09 information: /mnt/user/VMBACKUPS/Stoneman does not exist. creating it. 2023-06-05 14:09:09 information: skip_vm_shutdown is false. beginning vm shutdown procedure. 2023-06-05 14:09:09 information: Stoneman is running. vm desired state is shut off. 2023-06-05 14:09:09 information: performing 20 30 second cycles waiting for Stoneman to shutdown cleanly. 2023-06-05 14:09:09 information: cycle 1 of 20: waiting 30 seconds before checking if the vm has entered the desired state. 2023-06-05 14:09:39 information: Stoneman is shut off. vm desired state is shut off. can_backup_vm set to y. 2023-06-05 14:09:39 information: actually_copy_files is 1. 2023-06-05 14:09:39 information: can_backup_vm flag is y. starting backup of Stoneman configuration, nvram, and vdisk(s). 2023-06-05 14:09:39 information: copy of Stoneman.xml to /mnt/user/VMBACKUPS/Stoneman/20230605_1342_Stoneman.xml complete. 2023-06-05 14:09:39 information: copy of /etc/libvirt/qemu/nvram/067810a2-b75d-ef76-aa6e-cb4c419bb5d9_VARS-pure-efi.fd to /mnt/user/VMBACKUPS/Stoneman/20230605_1342_067810a2-b75d-ef76-aa6e-cb4c419bb5d9_VARS-pure-efi.fd complete. 2023-06-05 14:12:10 information: copy of /mnt/user/domains/Ubuntu/vdisk1.img to /mnt/user/VMBACKUPS/Stoneman/20230605_1342_vdisk1.img.zst complete. 2023-06-05 14:12:10 information: backup of /mnt/user/domains/Ubuntu/vdisk1.img vdisk to /mnt/user/VMBACKUPS/Stoneman/20230605_1342_vdisk1.img.zst complete. 2023-06-05 14:12:10 information: the extensions of the vdisks that were backed up are img. 2023-06-05 14:12:10 information: vm_state is shut off. vm_original_state is running. starting Stoneman. 2023-06-05 14:12:14 information: backup of Stoneman to /mnt/user/VMBACKUPS/Stoneman completed. 2023-06-05 14:12:14 information: number of days to keep backups set to indefinitely. 2023-06-05 14:12:14 information: number of backups to keep set to infinite. 2023-06-05 14:12:14 information: removing local Stoneman.xml. 2023-06-05 14:12:14 information: bass can be found on the system. attempting backup. 2023-06-05 14:12:14 information: creating local bass.xml to work with during backup. 2023-06-05 14:12:14 information: /mnt/user/VMBACKUPS/bass does not exist. creating it. 2023-06-05 14:12:14 information: extension for /mnt/user/isos/virtio-win-0.1.190-1.iso on bass was found in vdisks_extensions_to_skip. skipping disk. 2023-06-05 14:12:14 information: skip_vm_shutdown is false. beginning vm shutdown procedure. 2023-06-05 14:12:14 information: bass is running. vm desired state is shut off. 2023-06-05 14:12:15 information: performing 20 30 second cycles waiting for bass to shutdown cleanly. 2023-06-05 14:12:15 information: cycle 1 of 20: waiting 30 seconds before checking if the vm has entered the desired state. 2023-06-05 14:12:45 information: bass is shut off. vm desired state is shut off. can_backup_vm set to y. 2023-06-05 14:12:45 information: actually_copy_files is 1. 2023-06-05 14:12:45 information: can_backup_vm flag is y. starting backup of bass configuration, nvram, and vdisk(s). 2023-06-05 14:12:45 information: copy of bass.xml to /mnt/user/VMBACKUPS/bass/20230605_1342_bass.xml complete. 2023-06-05 14:12:45 information: copy of /etc/libvirt/qemu/nvram/4a9d6e0c-922c-1b44-39fb-dbf629120504_VARS-pure-efi.fd to /mnt/user/VMBACKUPS/bass/20230605_1342_4a9d6e0c-922c-1b44-39fb-dbf629120504_VARS-pure-efi.fd complete. 2023-06-05 14:12:45 information: extension for /mnt/user/isos/virtio-win-0.1.190-1.iso on bass was found in vdisks_extensions_to_skip. skipping disk. 2023-06-05 14:17:48 information: copy of /mnt/user/domains/bass/vdisk1.img to /mnt/user/VMBACKUPS/bass/20230605_1342_vdisk1.img.zst complete. 2023-06-05 14:17:48 information: backup of /mnt/user/domains/bass/vdisk1.img vdisk to /mnt/user/VMBACKUPS/bass/20230605_1342_vdisk1.img.zst complete. 2023-06-05 14:17:48 information: the extensions of the vdisks that were backed up are img. 2023-06-05 14:17:48 information: vm_state is shut off. vm_original_state is running. starting bass. 2023-06-05 14:17:53 information: backup of bass to /mnt/user/VMBACKUPS/bass completed. 2023-06-05 14:17:53 information: number of days to keep backups set to indefinitely. 2023-06-05 14:17:53 information: number of backups to keep set to infinite. 2023-06-05 14:17:53 information: removing local bass.xml. 2023-06-05 14:17:53 information: virtualmin can be found on the system. attempting backup. 2023-06-05 14:17:53 information: creating local virtualmin.xml to work with during backup. 2023-06-05 14:17:53 information: /mnt/user/VMBACKUPS/virtualmin does not exist. creating it. 2023-06-05 14:17:53 information: extension for /mnt/user/isos/ubuntu-20.04.4-live-server-amd64.iso on virtualmin was found in vdisks_extensions_to_skip. skipping disk. 2023-06-05 14:17:53 information: skip_vm_shutdown is false. beginning vm shutdown procedure. 2023-06-05 14:17:53 information: virtualmin is running. vm desired state is shut off. 2023-06-05 14:17:53 information: performing 20 30 second cycles waiting for virtualmin to shutdown cleanly. 2023-06-05 14:17:53 information: cycle 1 of 20: waiting 30 seconds before checking if the vm has entered the desired state. 2023-06-05 14:18:23 information: virtualmin is shut off. vm desired state is shut off. can_backup_vm set to y. 2023-06-05 14:18:23 information: actually_copy_files is 1. 2023-06-05 14:18:23 information: can_backup_vm flag is y. starting backup of virtualmin configuration, nvram, and vdisk(s). 2023-06-05 14:18:23 information: copy of virtualmin.xml to /mnt/user/VMBACKUPS/virtualmin/20230605_1342_virtualmin.xml complete. 2023-06-05 14:18:23 information: copy of /etc/libvirt/qemu/nvram/b1999575-4fe4-9b2d-fa8c-a02e2eb41c39_VARS-pure-efi.fd to /mnt/user/VMBACKUPS/virtualmin/20230605_1342_b1999575-4fe4-9b2d-fa8c-a02e2eb41c39_VARS-pure-efi.fd complete. 2023-06-05 14:20:32 information: copy of /mnt/user/domains/virtualmin/vdisk1.img to /mnt/user/VMBACKUPS/virtualmin/20230605_1342_vdisk1.img.zst complete. 2023-06-05 14:20:32 information: backup of /mnt/user/domains/virtualmin/vdisk1.img vdisk to /mnt/user/VMBACKUPS/virtualmin/20230605_1342_vdisk1.img.zst complete. 2023-06-05 14:20:32 information: extension for /mnt/user/isos/ubuntu-20.04.4-live-server-amd64.iso on virtualmin was found in vdisks_extensions_to_skip. skipping disk. 2023-06-05 14:20:32 information: the extensions of the vdisks that were backed up are img. 2023-06-05 14:20:32 information: vm_state is shut off. vm_original_state is running. starting virtualmin. 2023-06-05 14:20:38 information: backup of virtualmin to /mnt/user/VMBACKUPS/virtualmin completed. 2023-06-05 14:20:38 information: number of days to keep backups set to indefinitely. 2023-06-05 14:20:38 information: number of backups to keep set to infinite. 2023-06-05 14:20:38 information: removing local virtualmin.xml. 2023-06-05 14:20:38 information: Glyde can be found on the system. attempting backup. 2023-06-05 14:20:38 information: creating local Glyde.xml to work with during backup. 2023-06-05 14:20:38 information: /mnt/user/VMBACKUPS/Glyde does not exist. creating it. 2023-06-05 14:20:38 information: extension for /mnt/user/isos/en_windows_server_2019_updated_sept_2019_x64_dvd_199664ce.iso on Glyde was found in vdisks_extensions_to_skip. skipping disk. 2023-06-05 14:20:38 information: extension for /mnt/user/isos/virtio-win-0.1.190-1.iso on Glyde was found in vdisks_extensions_to_skip. skipping disk. 2023-06-05 14:20:38 information: skip_vm_shutdown is false. beginning vm shutdown procedure. 2023-06-05 14:20:38 information: Glyde is running. vm desired state is shut off. 2023-06-05 14:20:39 information: performing 20 30 second cycles waiting for Glyde to shutdown cleanly. 2023-06-05 14:20:39 information: cycle 1 of 20: waiting 30 seconds before checking if the vm has entered the desired state. 2023-06-05 14:21:09 information: Glyde is shut off. vm desired state is shut off. can_backup_vm set to y. 2023-06-05 14:21:09 information: actually_copy_files is 1. 2023-06-05 14:21:09 information: can_backup_vm flag is y. starting backup of Glyde configuration, nvram, and vdisk(s). 2023-06-05 14:21:09 information: copy of Glyde.xml to /mnt/user/VMBACKUPS/Glyde/20230605_1342_Glyde.xml complete. 2023-06-05 14:21:09 information: copy of /etc/libvirt/qemu/nvram/8f67ba84-f35f-8371-568b-c57337895cdd_VARS-pure-efi.fd to /mnt/user/VMBACKUPS/Glyde/20230605_1342_8f67ba84-f35f-8371-568b-c57337895cdd_VARS-pure-efi.fd complete. 2023-06-05 14:21:09 information: extension for /mnt/user/isos/en_windows_server_2019_updated_sept_2019_x64_dvd_199664ce.iso on Glyde was found in vdisks_extensions_to_skip. skipping disk. 2023-06-05 14:21:09 information: extension for /mnt/user/isos/virtio-win-0.1.190-1.iso on Glyde was found in vdisks_extensions_to_skip. skipping disk. 2023-06-05 14:29:02 information: copy of /mnt/user/domains/Glyde/vdisk1.img to /mnt/user/VMBACKUPS/Glyde/20230605_1342_vdisk1.img.zst complete. 2023-06-05 14:29:02 information: backup of /mnt/user/domains/Glyde/vdisk1.img vdisk to /mnt/user/VMBACKUPS/Glyde/20230605_1342_vdisk1.img.zst complete. 2023-06-05 14:29:02 information: the extensions of the vdisks that were backed up are img. 2023-06-05 14:29:02 information: vm_state is shut off. vm_original_state is running. starting Glyde. 2023-06-05 14:29:10 information: backup of Glyde to /mnt/user/VMBACKUPS/Glyde completed. 2023-06-05 14:29:10 information: number of days to keep backups set to indefinitely. 2023-06-05 14:29:10 information: number of backups to keep set to infinite. 2023-06-05 14:29:10 information: removing local Glyde.xml. 2023-06-05 14:29:10 information: Macinabox BigSur can be found on the system. attempting backup. 2023-06-05 14:29:10 information: creating local Macinabox BigSur.xml to work with during backup. 2023-06-05 14:29:10 information: /mnt/user/VMBACKUPS/Macinabox BigSur does not exist. creating it. 2023-06-05 14:29:10 information: skip_vm_shutdown is false. beginning vm shutdown procedure. 2023-06-05 14:29:10 information: Macinabox BigSur is shut off. vm desired state is shut off. can_backup_vm set to y. 2023-06-05 14:29:10 information: actually_copy_files is 1. 2023-06-05 14:29:10 information: can_backup_vm flag is y. starting backup of Macinabox BigSur configuration, nvram, and vdisk(s). 2023-06-05 14:29:10 information: copy of Macinabox BigSur.xml to /mnt/user/VMBACKUPS/Macinabox BigSur/20230605_1342_Macinabox BigSur.xml complete. 2023-06-05 14:29:10 information: copy of /etc/libvirt/qemu/nvram/5d6a9774-95ee-4494-9c56-fe6054f4e6bf_VARS-pure-efi.fd to /mnt/user/VMBACKUPS/Macinabox BigSur/20230605_1342_5d6a9774-95ee-4494-9c56-fe6054f4e6bf_VARS-pure-efi.fd complete. 2023-06-05 14:29:10 failure: copy of /mnt/user/domains/Macinabox BigSur/BigSur-opencore.img to /mnt/user/VMBACKUPS/Macinabox BigSur/20230605_1342_BigSur-opencore.img.zst failed. 2023-06-05 14:29:10 information: backup of /mnt/user/domains/Macinabox BigSur/BigSur-opencore.img vdisk to /mnt/user/VMBACKUPS/Macinabox BigSur/20230605_1342_BigSur-opencore.img.zst complete. 2023-06-05 14:29:18 information: copy of /mnt/user/isos/BigSur-install.img to /mnt/user/VMBACKUPS/Macinabox BigSur/20230605_1342_BigSur-install.img.zst complete. 2023-06-05 14:29:18 information: backup of /mnt/user/isos/BigSur-install.img vdisk to /mnt/user/VMBACKUPS/Macinabox BigSur/20230605_1342_BigSur-install.img.zst complete. 2023-06-05 14:29:18 failure: copy of /mnt/user/domains/Macinabox BigSur/macos_disk.img to /mnt/user/VMBACKUPS/Macinabox BigSur/20230605_1342_macos_disk.img.zst failed. 2023-06-05 14:29:18 information: backup of /mnt/user/domains/Macinabox BigSur/macos_disk.img vdisk to /mnt/user/VMBACKUPS/Macinabox BigSur/20230605_1342_macos_disk.img.zst complete. 2023-06-05 14:29:18 information: the extensions of the vdisks that were backed up are img. 2023-06-05 14:29:18 information: vm_state is shut off. vm_original_state is shut off. not starting Macinabox BigSur. 2023-06-05 14:29:18 information: backup of Macinabox BigSur to /mnt/user/VMBACKUPS/Macinabox BigSur completed. 2023-06-05 14:29:18 information: number of days to keep backups set to indefinitely. 2023-06-05 14:29:18 information: number of backups to keep set to infinite. 2023-06-05 14:29:18 information: removing local Macinabox BigSur.xml. 2023-06-05 14:29:18 information: finished attempt to backup flashman, lasermanex, Numbermanexe, Stoneman, bass, virtualmin, Glyde, Macinabox BigSur to /mnt/user/VMBACKUPS. 2023-06-05 14:29:18 information: Reconstruct write disabled. 2023-06-05 14:29:18 information: cleaning out logs over 1. 2023-06-05 14:29:18 information: removed '/mnt/user/VMBACKUPS/logs/20230605_1341_unraid-vmbackup.log'. 2023-06-05 14:29:18 information: cleaning out error logs over 10. 2023-06-05 14:29:18 information: did not find any error log files to remove. 2023-06-05 14:29:18 warning: errors found. creating error log file. 2023-06-05 14:29:18 Stop logging to error log file. Did this fail? If so, what needs done to fix it?

I honestly think what happened was either splunk or checkmk docker images went rouge and caused all kinds of havok on the server. I think the best thing is to just attempt to run those via a vm instead of docker.

for me, i ended up being able to install 2 docker containers before I started getting the following messages root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='magnetman' --net='br0' --ip='192.168.128.2' -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="chipshop" -e HOST_CONTAINERNAME="magnetman" -e 'TCP_PORT_443'='8186' -e 'HOSTNAME'='magnetman.moroneylabs.net' -e 'REVERSE_PROXY'='moroneylabs.net' -e 'REVERSE_PROXY_TLS_PORT'='443' -e 'IFRAME'='false' -e 'ALLOW_NEW_ACCOUNTS'='false' -e 'WEBRTC'='true' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='https://[IP]:[PORT:8086]' -l net.unraid.docker.icon='https://github.com/Muwahhidun/logo/blob/main/meshcentral-logo.png?raw=true' -v '/mnt/user/appdata/meshcentral/meshcentral-data':'/opt/meshcentral/meshcentral-data':'rw' -v '/mnt/user/appdata/meshcentral/meshcentral-files ':'/opt/meshcentral/meshcentral-files ':'rw' 'typhonragewind/meshcentral' 2e85e8df3209379e15387668a7a77667df706d67b2d612ac9af7ee4a174801fd docker: Error response from daemon: failed to create the ipvlan port: device or resource busy. The command failed. Not really worth it for me

so i am redoing the docker.img file, would you recommend switching to ipvlan instead of mac? EDIT so turns out ipvlan isnt really an option as it seems to actually be causing more harm than good.

My server today has started throwing all kinds of problems. The biggest one being I'm getting execution error server error messages. Additionally I am getting callback trace messages. I cant start new containers, install new ones, or even stop current ones. attached are the sys logs and diagnostic logs Any assistance in forcing this thing back into proper behavior would be greatly appreciated. chipshop-syslog-20220726-0224.zip chipshop-diagnostics-20220725-2152.zip

I am getting this message How do i fix it?

so, after some additional troubleshooting, i discovered a bigger issue, none of my docker containers that are set to br0 are visible on my wireguard vpn, so thats a separate issue, everything is fine with checkmk

br0

I am trying to run checkmk-raw in custom network type so it gets its own ip address and it is not working. If i switch it into host or bridged mode it works fine, but i really want it working with its own ip address.

im trying to reset my password but i keep getting unable to locate /datat/portainer.db on disk any suggestions?

Honestly, i would look into zerotier, its just like hamachi, but free, very few limitations, native unraid support via the plugin, and open source.

What are the chances of an update to the latest version?

I am having absolutely no luck getting this working, i just installed it, but have not gotten any of the wizards going, nor have i been able to load in paperclip. is there any resources i should be reviewing that show how to load paperclip?