vitis

Did you sort this out? I tried in the allow list these - local docker network IP, server IP, my public IP and IPs from my Cloudflare proxied domain. All of those got me rid of the warning but Collbora was not working. Solution: Add all Cloudflare IPs to the allow list Source: https://github.com/nextcloud/all-in-one#notes-on-cloudflare-proxytunnel

Hi @Mattyfaz, I tried your steps but I am failing on creating the rocketchat user. I keep getting this error message. 2020-01-02T17:43:21.893+0100 E QUERY [js] uncaught exception: Error: couldn't add user: command createUser requires authentication : _getErrorWithCode@src/mongo/shell/utils.js:25:13 DB.prototype.createUser@src/mongo/shell/db.js:1370:11 @(shell):1:1 I had to switch authorization to disabled in the config file. More reading here: https://stackoverflow.com/questions/27784956/error-couldnt-add-user-not-authorized-on-test-to-execute-command-createuser Edit: Web frontend port and the port in the rocketchat url has to correspond. Otherwise the file uploads would not work.

Hi guys, I would like to passthrough AR9280 wifi card. It is a minipcie card in an pcie adapter. I am getting an error similar to the one when trying to passthrough an M.2 drive. Execution error internal error: qemu unexpectedly closed the monitor: 2019-11-28T22:34:20.363830Z qemu-system-x86_64: -device vfio-pci,host=0a:00.0,id=hostdev4,bus=pci.6,addr=0x0: vfio 0000:0a:00.0: failed to add PCI capability 0x11[0x70]@0x90: table & pba overlap, or they don't fit in BARs, or don't align I tried reading through the M.2 topic and also this one - but I was not able to find a solution. The passthrough is not working on any VM. So I am testing it on a fresh Linux VM (not even installed). Here is my VM xml config. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Fetch</name> <uuid>5b9c78d5-32e9-bbb8-58e3-c91d217894ec</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='5'/> <vcpupin vcpu='1' cpuset='15'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/5b9c78d5-32e9-bbb8-58e3-c91d217894ec_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='1' threads='2'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/TinyCorePure64-current.iso'/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/user/domains/Fetch/vdisk1.img'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user/email/'/> <target dir='Mail'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </filesystem> <interface type='bridge'> <mac address='52:54:00:f5:eb:71'/> <source bridge='virbr0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='cz'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> </domain> The device in question is the last one - Oa:00.0. Thanks for any advice. Viktor

Hi guys, Can please anyone confirm that the Hauppauge WinTV dualHD works with LibreELEC or TBS OS drivers? I just bought different Silicon Labs Si2168 based tuner and it only worked with Crazy Cat drivers that seem to have uncertain future at this point so I am returning it. I also have a Realtek RTL2838/Sony CXD2837ER based tuner. I was unable to make the Sony DVB-T2 tuner visible so I ended up only with the Realtek DVB-T capable. I found out that the cooperation between the RTL and CXD chips should be already fixed but I was unable to make it work with the available drivers. RTL chip itself works with LibreELEC package. More info on the RTL/CXD issue: https://git.linuxtv.org/media_tree.git/commit/?id=d695eb5b3b963230652db29eae341a9706c593f4 - RTL driver updated to work with the CXD demod https://github.com/torvalds/linux/pull/567 - this suggest that it might work in kernel 5.0 but I still got only RTL chip in tvheadend visible

Hooked up the drive bays with Corsair AX860i and it works. Case closed. Cables are already new. Errors showed up with the old ones and I am (well unraid is) still watching these smarts. Thank you guys! You are the best!

That is an interesting point actually! I will check the PSUs internals for bad caps as that is the only thing that can be bad. I doubt that it is overloaded. Server sits at idle during the parity check start and as I mentioned I already did the parity check with this setup. Attached are specs of the PSU.

Hi guys, A parity check was started automatically last midnight and as I woke up I heard painfull sounds from the server. Sounds like all drives are spinning up and then suddenly stopping. I saw that the parity check is still on zero percent after 7 hours so I stopped it immediatelly. The system log is full of errors. If I start the parity check manualy, this is what I get. Oct 16 21:34:13 Tower emhttpd: req (12): startState=STARTED&file=&cmdCheck=Check&optionCorrect=correct&csrf_token=**************** Oct 16 21:34:13 Tower kernel: mdcmd (46): check correct Oct 16 21:34:13 Tower kernel: md: recovery thread: check P Q ... Oct 16 21:34:13 Tower kernel: md: using 1536k window, over a total of 5860522532 blocks. Oct 16 21:34:14 Tower kernel: ata10.00: exception Emask 0x10 SAct 0x0 SErr 0x4890000 action 0xe frozen Oct 16 21:34:14 Tower kernel: ata10.00: irq_stat 0x0c400040, interface fatal error, connection status changed Oct 16 21:34:14 Tower kernel: ata10: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Oct 16 21:34:14 Tower kernel: ata10.00: failed command: READ DMA EXT Oct 16 21:34:14 Tower kernel: ata10.00: cmd 25/00:00:00:3d:00/00:03:00:00:00/e0 tag 8 dma 393216 in Oct 16 21:34:14 Tower kernel: res 50/00:00:ff:3c:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error) Oct 16 21:34:14 Tower kernel: ata10.00: status: { DRDY } Oct 16 21:34:14 Tower kernel: ata10: hard resetting link Oct 16 21:34:20 Tower kernel: ata10: link is slow to respond, please be patient (ready=0) Oct 16 21:34:24 Tower kernel: ata10: COMRESET failed (errno=-16) Oct 16 21:34:24 Tower kernel: ata10: hard resetting link Oct 16 21:34:29 Tower kernel: ata10: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 16 21:34:29 Tower kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT1.SPT5._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Oct 16 21:34:29 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT1.SPT5._GTF, AE_NOT_FOUND (20180810/psparse-516) Oct 16 21:34:29 Tower kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT1.SPT5._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Oct 16 21:34:29 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT1.SPT5._GTF, AE_NOT_FOUND (20180810/psparse-516) Oct 16 21:34:29 Tower kernel: ata10.00: configured for UDMA/33 Oct 16 21:34:29 Tower kernel: ata10: EH complete Oct 16 21:34:30 Tower kernel: ata10.00: exception Emask 0x10 SAct 0x0 SErr 0x4890000 action 0xe frozen Oct 16 21:34:30 Tower kernel: ata10.00: irq_stat 0x0c400040, interface fatal error, connection status changed Oct 16 21:34:30 Tower kernel: ata10: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Oct 16 21:34:30 Tower kernel: ata10.00: failed command: READ DMA EXT Oct 16 21:34:30 Tower kernel: ata10.00: cmd 25/00:40:c0:7c:00/00:05:00:00:00/e0 tag 7 dma 688128 in Oct 16 21:34:30 Tower kernel: res 50/00:00:bf:7c:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error) Oct 16 21:34:30 Tower kernel: ata10.00: status: { DRDY } Oct 16 21:34:30 Tower kernel: ata10: hard resetting link Oct 16 21:34:33 Tower emhttpd: req (14): startState=STARTED&file=&csrf_token=****************&cmdNoCheck=Cancel Oct 16 21:34:33 Tower kernel: mdcmd (47): nocheck Cancel No errors appear asside the drives list in the main tab and everything works. Apart from the parity check. I turned it off and checked all cables already, even thought I did not touch them in the last week. I have already done the parity check on this setup for four times. I attached my diagnostic files. Have you encountered this? Are you able to help? Thanks tower-diagnostics-20191016-1951.zip

Hi guys, I was fidling around with my pfsense VM. I tried the change the vDisk location (not even sure why now), but the VM did not like it so I just put everything back and restarted the VM. However I am unable to boot the vDisk and pfsense wants to start fresh installation on every boot. I tried restarting the VM service and I got libvirt not found error. I deleted it, rebooted unraid and started the VM service again - successfully. I backed up everything before Operation Major Mistake so I recovered the xml VM setup and loaded the existing vdisk but I am still getting the same - fresh installation is the only option. Is there a way how to push the existing vdisk to boot? Or just get the pfsense config from the vDisk? As that is the only file I do not have backed up. I also did a "fix permissions" from tools in unraid as I had some files with wrong permissions. So this might have something to do with this whole problem. Thanks for your time

Hi guys, did anyone tried to video support to piwigo? https://github.com/xbgmsharp/piwigo-videojs/wiki/How-to-add-videos#add-video-support I have done the config changes but I am not sure if I can add the ffmpeg and other stuff to the container.

I just wanted to let you know that I solved this issue. I was using a template config file, which had a lot of examples and commented lines and I guess that the plugin could not handle this while inserting it's own stuff to it. I downloaded PIA's ovpn files which worked, so I changed my files to look alike the PIA ones and then it started working. It is not really a fix, it's just a workaround.

Hello, I have installed the client and I am having issues while connecting. I have a working unified ovpn profile and also ovpn/cert/ca - both verified and working. But when I am trying to connect with this Unraid client, the plugin inserts 10 lines saying "dev tap5" to my ovpn profile and that breaks it, so it does not work. Has anybody encountered this problem? You can see part of the ovpn profile below. ############################################## # Sample client-side OpenVPN 2.0 config file # dev tap5 # for connecting to multi-client server. # dev tap5 # # # This configuration can be used by multiple # # clients, however each client should have # dev tap5 # its own cert and key files. # # # # On Windows, you might want to rename this # # file so it has a .ovpn extension # ############################################## # Specify that we are a client and that we dev tap5 # will be pulling certain config file directives # from the server. client dev tap5