Zan

Yep, they're on the same custom bridge. I've changed back to the default and it's working. Thanks saarg. Now to get the freshrss android app working. I'm currently getting a "This url is not correct error" as others have had in the past - https://git.feneas.org/christophehenry/freshrss-android/-/issues/70 I haven't found a decent rss app on android (had FeedMe but it's too slow to refresh feeds) and the html ui for freshrss isn't great on mobile as the post titles get truncated. If anyone has any recommendations for a good Android RSS reader that works with freshrss, would appreciate it

Letsencrypt reverse proxy question: After setting up my subdomain forward for freshrss.<mydomain>, letsencrypt doesn't work with the default freshrss.subdomain.conf. I've had to change the following lines because otherwise letsencrypt proxies to 172.18.0.7:80 (default freshrss docker ip/port). Anyone know why this is? I assume it's something to do with the resolver??? < set $upstream_app freshrss; < set $upstream_port 80; --- > set $upstream_app 192.168.1.1; > set $upstream_port 8084;

Hi, Will lsio be upgrading this container to 10.2 or maybe adding a new one for 10.2? There are some window functions I'm using in a project that I'd like to run on my unRAID server and would rather use an lsio docker but could roll my own if needed https://mariadb.com/kb/en/library/window-functions/

Has anyone tried IGD passthrough to a Windows VM using the the Ryzen 3 2200G or Ryzen 5 2400G IGD?

This could also be due to an issue with the cx23885 code not working well with VT-d /VT-x enabled. See https://www.spinics.net/lists/linux-media/msg119385.html I've changed my syslinux.cfg to set the cx23885 to debug level 5 which has helped - you might want to give that a try and see if it helps eg. append initrd=/bzroot,bzroot-gui cx23885.debug=5

"Plexpass" release now named "Beta"... StSimm1 Plex Dev Team LondonPosts: 697Members, Plex Employee, Plex Pass, Plex Ninja Plex Employee October 12 edited October 12 Plex Media Server 1.9.5 is now available to Plex Pass users ( this will not get auto-update notification please update manually ) NEW: - (Trailers) Allow specifying preroll with a file path. - (Trailers) Allow specifying alternate prerolls with file paths separated by semicolon. - (Trailers) Allow specifying sequential prerolls with file paths separated by comma. - (Update Channels) New release channels names. "PlexPass" channel is now named "Beta".

OK, I latest plex update (1.7.3.3937) corrected an issue with some WinTV-quadHD cards. Mine has now been detected by plex.

Thanks saarg, I think they pulled the WinTV-quadHD from the supported list because the ATSC version isn't working however I read somewhere that the DVB version that I have, might still be ok. I'm still really keen to drop my tvheadend docker and associated tvhproxy VM I'm currently running for plex DVR. Just to test that the docker can get signal from the card, I was thinking of building w_scan from source inside the docker. Or would there be another easier way to test this?

I'm not sure, saarg. I've bash'd into the docker and can see that the DVB adaptors are passed through and registered, but plex doesn't see them when I try to add a DVR. On the plex site it says NAS-based plex only supports networked tuners so I assumed the docker would be the same https://support.plex.tv/hc/en-us/articles/225877427-Supported-DVR-Devices-and-Antennas They've also removed the WinTV-quadHD specifically, so possibly an issue just with that card. Anyway hoping you or others could confirm whether other cards can be detected by the plex docker, or give me some pointers on what to do next. I also tried a Ubuntu vm today with the card passed through and media tree installed as per hauppages instructions but that also didn't get the card detected in plex.

I'm interested in doing this too, it'd save me from having to run tvheadend in a docker and tvhproxy in a VM. Let us know if you make any progress!

Hey Saarg, I've found that tvheadend with the default recording cache scheme (System) is grabbing memory and not releasing it until I assume when the recording ends. This has been causing my tvheadend docker to re-start. I've since change the cache scheme to Sync + Don't Keep. I was thinking this might be a good default option for you to set in the docker. What do you think? That seems to be one of the reasons why my mkvs werent "seekable" in vlc (the mkvs were abruptly cut off when tvheadend crashes) - another issue seems to be the duration of the mkv but I'm not sure if it's then vlc that isn't good with large mkvs or maybe a tvheadend mkv corruption issue... Will keep investigating.

OK, just re-updated from CA-Apps and all good. Not sure what happened there but will keep monitoring it. Thanks.

Hi Ken-Ji, I've been getting this error for weeks (first a countdown now I'm locked out). This is even after a re-start, which based on your comment on Tuesday should have caused an automated upgrade. [ALERT]: You're using an old version of Dropbox. Please update to the latest version to continue using Dropbox. Can I "bash" into the docker and force an update manually?

This docker seems to have a conflict with some of the browser cookies that other unraid dockers are storing for the same IP address. I get stuck on the login screen even though the user and password are correctly populated. I have to clear the cookies before I can pass the login screen. Is this a known issue that anyone is looking to resolve?

Is anyone else using mkv recording profile? The mkv files tvheadend is producing can't be "seeked" on my Win10 PC with VLC. Also comskip is not generating .edl files when mkv profile is selected. I've switched to passthrough and can now seek and generate .edl files (which vlc can't make use of so now switched to smplayer) but I'd like to switch back to mkv if possible. Has anyone been able to resolve the "seek" and edl issues I've experienced?

Can someone help me out, I'm trying to pass through some devices on a PCI-E card (6:00.0 and 7:00.0) to my Windows 10 VM: 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Controller 00:16.0 Communication controller: Intel Corporation 9 Series Chipset Family ME Interface #1 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V 00:1a.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2 00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller 00:1c.0 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 (rev d0) 00:1c.2 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 3 (rev d0) 00:1c.4 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 5 (rev d0) 00:1c.6 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d0) 00:1d.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1 00:1f.0 ISA bridge: Intel Corporation 9 Series Chipset Family H97 Controller 00:1f.2 SATA controller: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode] 00:1f.3 SMBus: Intel Corporation 9 Series Chipset Family SMBus Controller 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] 03:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01) 04:00.0 PCI bridge: Pericom Semiconductor Device 2304 (rev 05) 05:01.0 PCI bridge: Pericom Semiconductor Device 2304 (rev 05) 05:02.0 PCI bridge: Pericom Semiconductor Device 2304 (rev 05) 06:00.0 Multimedia video controller: Conexant Systems, Inc. CX23885 PCI Video and Audio Decoder (rev 03) 07:00.0 Multimedia video controller: Conexant Systems, Inc. CX23885 PCI Video and Audio Decoder (rev 03) 08:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 03) 09:01.0 USB controller: NEC Corporation OHCI USB Controller (rev 41) 09:01.1 USB controller: NEC Corporation OHCI USB Controller (rev 41) 09:01.2 USB controller: NEC Corporation uPD72010x USB 2.0 Controller (rev 02) When I start the VM, I immediately lose access to the emhttp interface but can still ssh into my server. However I when I try ps -ef or virsh list the command hangs so I can't figure out how to terminate the VM, and have to power down the server via a hard reset. Does anyone know why emhttp is not responding, and why ps -ef and virsh list is locking up and how I can work around it?

Solved it myself. Just re-read the first post, says to use SeaBIOS. I've been selecting OVMF by default. Created a new VM with SeaBIOS and all good.

Is IGD passthrough as easy as just creating a new VM with the IGD video and audio and starting it? I'm wondering whether there is anything simple in the BIOS, boot params or unRAID settings (eg. CPU Pinning) I might have missed. I currently run a Win10 VM with PCI-E ASUS R7-240 passthrough (all Logical CPUs ticked). And I'm trying to add a second VM using IGD, but getting no video via motherboard HDMI output on startup. I set up the VM using VNC, then switched to IGD (after installing TeamViewer so I could still remote into it), but, while Win10 detected the HD Graphics 4600 and installed the drivers, Device Manager reports the hardware as not working, from memory with error code 32. My rig is a ASRock H97M-Pro4 Motherboard and i5-4460. Any ideas?

I went back to defaults (nobody:users) a while ago but the permissions issue continued. I've deleted the docker image and re-created it and it's working fine again. Cheers.

Hi Ken-ji, I keep having to change owner on the app folder from root to nobody:users and then re-link, every time I do an upgrade (I also chmod 777 on the app dir as the config dir is 777). Is this normal or have I set something up incorrectly? Cheers, Zan

Thanks ken-ji, all good now

Hi Kenji, I set up this docker container just using the defaults but noticed that I then didn't have any access to files. So I set the ENV variables for DROPBOX_USER and DROPBOX_USERID so that the user I regularly access my unRAID box with can get to the files, but now the container won't start and the log file is empty. Here's the command line: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="Dropbox" --net="bridge" -e DROPBOX_USER="zan" -e DROPBOX_USERID="1000" -e TZ="Australia/Sydney" -p 17500:17500/tcp -p 17500:17500/udp -v "/etc/localtime":"/etc/localtime":ro -v "/mnt/cache/appdata/dropbox/config":"/dropbox/.dropbox":rw -v "/mnt/cache/appdata/dropbox/app":"/dropbox/.dropbox-dist":rw -v "/mnt/user/Dropbox":"/dropbox/Dropbox":rw roninkenji/dropbox-docker Any ideas?

Hi jonp, Can I make do with pc-i440fx-2.3 machine type or must it be 'pc'? I'm not able to convert a q35 machine to pc - getting some sort of pci 000:00.00 error. So I've tried to create a pc-i440fx-2.3 machine for ubuntu, but still getting errors when trying to pass through the below PCI-E tuner card. Any thoughts on how I could pass through a DigitalNow Quad tuner which is appearing in the PCI devices list as: 05:00.0 PCI bridge: PLX Technology, Inc. PEX8112 x1 Lane PCI Express-to-PCI Bridge (rev aa) 06:00.0 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) 06:00.1 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) 06:00.2 USB controller: VIA Technologies, Inc. USB 2.0 (rev 65) I've enabled PCIe ACS Overrides, because previously these devices were appearing with a bunch of other ones in group 9, now they're separated into IOMMU group 16: /sys/kernel/iommu_groups/16/devices/0000:05:00.0 /sys/kernel/iommu_groups/16/devices/0000:06:00.0 /sys/kernel/iommu_groups/16/devices/0000:06:00.1 /sys/kernel/iommu_groups/16/devices/0000:06:00.2 Here's my XML: <domain type='kvm'> <name>Ubuntu</name> <uuid>f153e902-4e72-aab4-3996-cf39214fbfab</uuid> <metadata> <vmtemplate name="Custom" icon="ubuntu.png" os="ubuntu"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' threads='1'/> </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/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/cache/VMs/Ubuntu.img'/> <target dev='hdb' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/Software/ISOs/Ubuntu/ubuntu-14.04.3-desktop-amd64.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user'/> <target dir='Shares'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </filesystem> <interface type='bridge'> <mac address='52:54:00:ad:5b:49'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Ubuntu.org.qemu.guest_agent.0'/> <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'/> <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='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='vmvga' vram='16384' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x2'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x0c' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x2'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x0b' function='0x0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </memballoon> </devices> </domain>

Do you have 'Hide "dot" files:' set to no in SMB settings? That'd be a good option but it'll affect all shares, which I don't want at this stage. If I can hide dot files only on this share I'll definitely do it, otherwise hoping you might have another option? :-)

Hi everyone, I'm using vfs recycle for my Windows Media Center Recorded TV. When I delete the file in WMC, vfs recycle moves it to .Recycle Bin, but as WMC also has access to that directory, the file re-appears in the Recorded Shows list a few seconds later. Initially I told my family just to delete it a second time, but I would like to have a solution that avoids this. I'm thinking that I will move the 'Recorded TV' directory down to a sub-directory of a 'TV' share which I'm sure will work, but wondering if anyone could think of another solution that's a little more elegant and saves me having to change settings in WMC, Plex, Emby, etc?