Marv

Members
  • Content count

    134
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Marv

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Germany
  1. After upgrading to the latest container my Emby server is stuck (even after rebooting) with the following log entry. Cannot open assembly '/usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe': No such file or directory. Is there another update comming to fix this?
  2. I'm using an Asus H97i-Plus together with an i5-4570S. I just tried your suggestions all together and one by one and also tried enabling CPU Graphics Multi-Monitor but still no luck When connecting my main TV via HDMI to my integrated graphics I have no problem entering the Bios or using the unRAID Gui boot mode. Even after unRAID booted normaly I can still see the loading information. But after starting my LibreELEC via the WebUI the HDMI port just loses connection and my TV does not get a signal anymore. Hope someone got an idea.
  3. Does anyone got a working LibreELEC VM running using iGPU? I tried to set one up to ditch my GT720 I'm using right now but unfortunately I get no video signal at all. I think I'm meeting all requirements described over here: I made sure to use i440fx with SeaBios and my iGPU is also at PCI address 00:02.0 So I have no idea why its not working for me
  4. You don't have to setup fail2ban on the Nextcloud Docker. You need to map the location of the Nextcloud log file in the Letsencrypt container and then you are able to setup individual filters and add them to your jail.local file inside the Letsencrypt container itself.
  5. You don't have to change anything in the Emby settings to get it working like this.
  6. OMG thank you its working finally. I already found this solution before but placed the lines in my default config file of the Letsencrypt container and not inside the one from Nextcloud. Thanks for your post This is how my emby locaton looks like. Only difference is the '/emby' after the port. Strange that movie playback works for you though. location /emby { include /config/nginx/proxy.conf; proxy_pass http://192.168.121.10:8096/emby; }
  7. I just tried playing around with my iGPU and my LibreELEC VM to ditch my GT720 I was using all the time. Unfortunately I don't get any video signal when booting the VM at all. When I switch to the GT720 it works just like before. I made sure to use i440fx with SeaBios and my iGPU is also at PCI address 00:02.0 Can someone help me out here? Here is my xml file <domain type='kvm'> <name>LibreELEC</name> <uuid>b45008c5-6340-90bb-2b32-3a3c28b86ccd</uuid> <description>LibreELEC</description> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="libreelec.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='2'/> <vcpupin vcpu='1' cpuset='3'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.7'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='2' 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/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/LibreELEC/vdisk1.img'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <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> <controller type='pci' index='0' model='pci-root'/> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:62:59:fh'/> <source bridge='br0'/> <model type='e1000'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </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='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> </domain> and my PCI device list IOMMU group 0 [8086:0c00] 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) IOMMU group 1 [8086:0c01] 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) [10de:1288] 01:00.0 VGA compatible controller: NVIDIA Corporation GK208 [GeForce GT 720] (rev a1) [10de:0e0f] 01:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1) IOMMU group 2 [8086:0412] 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) IOMMU group 3 [8086:0c0c] 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) IOMMU group 4 [8086:8cb1] 00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Controller IOMMU group 5 [8086:8cba] 00:16.0 Communication controller: Intel Corporation 9 Series Chipset Family ME Interface #1 IOMMU group 6 [8086:15a1] 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V IOMMU group 7 [8086:8cad] 00:1a.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2 IOMMU group 8 [8086:8ca0] 00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller IOMMU group 9 [8086:8c90] 00:1c.0 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 (rev d0) IOMMU group 10 [8086:8c96] 00:1c.3 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 4 (rev d0) IOMMU group 11 [8086:8ca6] 00:1d.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1 IOMMU group 12 [8086:8cc6] 00:1f.0 ISA bridge: Intel Corporation 9 Series Chipset Family H97 Controller [8086:8c82] 00:1f.2 SATA controller: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode] [8086:8ca2] 00:1f.3 SMBus: Intel Corporation 9 Series Chipset Family SMBus Controller IOMMU group 13 [1b21:0612] 03:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
  8. +1 I'd defiinitely use it
  9. Thanks! Got it working for Emby. Unfortunately my Nextcloud container does not see the real remote IP from a user when logging in but always the Docker network IP 172.17.0.1. This way whenever a user gets a ban all other users get a ban aswell. I already specified my problem a few weeks ago in the Nextcloud thread. I guess this has something to do with Nextcloud running in bridge mode maybe!? Does anyone gets the real remote IP reported in the Nextcloud logs or is there some setting for Nginx that would be the solution? I think it's really strange that Nginx passes the remote IP through Emby but regarding Nextcloud it's not working. I really want to setup fail2ban for Nextcloud aswell.
  10. Oh wow didn't know this is possible and unfortunately I have no idea how the container path would look like Or do I just need a host path here (e.g. /mnt/user/appdata/emby/logs) and leave the container path empty?
  11. I got a question regarding fail2ban and my docker containers running behind nginx. Am I right that I'm not able to setup any custom fail2ban filters here as my letsencrypt-nginx container obviously can't see any logfiles from other containers such as Emby or Nextcloud!? As I understand the use of fail2ban here is that it's restricted to basic_auth only when used with Docker. Is this correct or is there a way to get this working together with Emby for example?
  12. So if you get an A+ I guess you are using nextcloud.server.com? Because I'm using the first way described in your guide with server.com/nextcloud
  13. I only get an A because the '__Host-Prefix' Hardening is missing on my server. Can anyone tell me how to achive this and what it means?
  14. Here is what I'm doing: I run LibreELEC with the latest Kodi Krypton build in a virtual machine on my unRAID server which is connected via HDMI to my main TV. In addition I have the Emby Docker installed which is able to sync your Kodi database. To get this working you need to install the 'Emby for Kodi plugin' on your Kodi setup. That way the Emby Docker can be used as a centralized database for all your Kodi devices. You can even setup an Nginx reverse proxy in a docker to access all your media via Emby when you are away from home.
  15. Hi, just wondering if someone using this container can tell me how and if you are able to shutdown your server and still be able to wake it up automatically for your recordings? Am I right that this may not be possible using Docker?
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.