Ex0danify

Hello everyone, does anybody else have problems with their SSL Certificates after the latest update? It seems that it only takes cert.crt and private.key in the /config/keys directory, regardless of what is configured in the virtual hosts in /config/apache/sites-confs/default.conf. If I try to replace private.key and cert.crt with my own key and certificate, the cert.crt gets overwritten when I restart the docker container. When I list the /config/keys directory after the container restart I see two files: cert.crt (the one I copied) and cert.crt\r (generated by the startup script) Any Advice on this?

Hello everybody. Today I successfully installed OSX with the help of this thread. Gerat work! But it seems I'm having trouble to passthough anything. My XML looks as follows: <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>OSX El Capitan (10.11)</name> <uuid>0ba39646-7ba1-4d41-9602-e2968b2fe36d</uuid> <metadata/> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='5'/> <vcpupin vcpu='3' cpuset='6'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.7'>hvm</type> <kernel>/mnt/user/VM_VDisks/OSX/Extra/enoch_rev2795_boot</kernel> <boot dev='hd'/> <bootmenu enable='yes'/> </os> <features> <acpi/> </features> <cpu mode='custom' match='exact'> <model fallback='allow'>core2duo</model> </cpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/user/VM_VDisks/OSX/ElCapitan.img'/> <target dev='hda' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0' model='piix3-uhci'> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <model name='i82801b11-bridge'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:00:20:30'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </interface> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <memballoon model='none'/> </devices> <seclabel type='none' model='none'/> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=03:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=03:00.1,bus=root.1,addr=00.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:1d.0,bus=root.1,addr=00.2'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=06:00.0,bus=root.1,addr=00.3'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=08:00.0,bus=root.1,addr=00.4'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd'/> <qemu:arg value='-device'/> <qemu:arg value='usb-mouse'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=--REMOVED FOR OBVIOUS REASONS--'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> </qemu:commandline> </domain> When I then try to start the VM the following error appears: internal error: process exited while connecting to monitor: 2017-03-08T10:01:39.349446Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: error opening /dev/vfio/21: Operation not permitted 2017-03-08T10:01:39.349474Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 21 2017-03-08T10:01:39.349483Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed It says the same when I try to only pass through one device. Has anyone an Idea whats going on with this? Help would be appreciated. --Ex0

I have temperature readings on the Dynamix Web GUI. Temps are reaching from 35°C to 49°C max. So I don't think heat is the problem in this case. Thanks for the suggestion though

Thanks for this Info, didn't know that there was such a thing as a trouble shooting mode!!! So, my box froze again. The last log was from 09:29Aam. When I woke up at 09:50am my box was frozen. I couldn't find anything realted to errors in the syslog. Maybe one of you guys can check again? Help would be appreciated. Thanks very very much in advance qraid-diagnostics-20161127-0929.zip

Hello guys, I recently started to run Unraid as my primary OS on my old QNAP Box. Most of the time it works like charm. Sadly that's MOST of the time. From time to time it happens, that the complete system locks up. This problem has always been there. Running Unraid on my QNAP since version 6.2.2 lockup means: --------------------- - No Web UI - No SSH (client says connected but then a SocketTimeOut Exception occours) - No keyboard/mouse input over the Unraid Server itself (mouse,keyboard,monitor directly connected to it) - No blinking cursor in the Terminal on the Unraid GUI (connected monitor directly to the box) Offcourse I want to analyze the problem because it's hell of annoying, but I need the sys logs for that. Are there any ways I'm currently not aware of to save the syslog before I reboot? Sometimes the problem happens after 1 day, but it also can run fine for like 3 days (I think that's the longest so far). The only possibility then is to hard reset my box. Any ideas?

How did you manage to get the FAN working correctly? I also got UnRaid up and running on my Box, but the FAN is always spinning at full speed. I tried installing the Dynamix FAN Controller Plugin, but when enabled, it turns my FAN down to 9% and stays there. Meanwhile the CPU Temps are rising up to 68°C in idle. I guess the Plugin is monitoring the array temperature? Did you experience such a thing? Btw.: My model is the QNAP TS-469L

Hello, I seem to have a problem with the folder permissions. I installed the docker with the config folder pointing to /mnt/user/Webserver. The Server starts fine. The Problem ist that I can't modify/create/delete anything from the files and fodlers created by the Docker. It always tells me that I require permissions from Tower\nobody (SMB Share). Are the apache webserver files and folders designed to only be accessible via the root account through something like ftp/sftp? Can I change the permissions, so I can work with said files/folder with my Unraid user account?

Thanks for such a nice plugin, making it fairly easy to run a web server on UnRaid. I have on problem though. Something seems wrong with the php permissions? I tried running phpMyAdmin and got the following: phpMyAdmin - Error Error during session start; please check your PHP and/or webserver log file and configure your PHP installation properly. Also ensure that cookies are enabled in your browser. session_start(): open(SESSION_FILE, O_RDWR)) failed: Permission denied (13) It doesn't matter if I run the webserver as 'nobody' or as a user. What's wrong here? How can I change the permissions needed?

Thanks for the quick reply. This Unraid community is just great I will move all my data off the NAS and try to get everything up and running. If someone else has ever tried this before, please feel free to tell

Hello there Unraid community, A few years ago (4-5 years now)I bought a QNAP TS-469L and back then, I really did not regret it. But today, I really don't like the software anymore. Sure: It has a clean Interface and is very easy to administrate, but for my taste now, it's too closed. I already have an Unraid Server Running on my main Gaming Rig and I must say, I'm damn satisfied with how smooth it is running.So I thought: Why not also run Unraid on my QNAP NAS Box? I tried booting unraid 6.2 on the Qnap with the USB drive from my gaming rig --> Worked It detected all drives --> Nice RAM utilisation was at 35% (3GB RAM Installed)--> Seems OK to run a few Dockers and use SMB shares CPU Usage was at 5-25% Idle --> Should suffice The NAS has an Intel Atom [email protected] (which has a 64-bit instruction set I guess. The CPU is not listed in the Intel Ark DB) The NAS has a 512MB DOM storage for the system. Can I use the DOM to boot Unraid? Does a DOM have an UID I can register? I have two reasons for wanting it to run from DOM: 1. I have one USB port more 2. I have the fear that, when the QNAP OS boots from DOM instead of Unraid (for whatever reason), It whipes my disk at initialisation. Has anyone ever tried such a thing? Does anybody know if things will work with 3GB and said CPU?

Upgrade from rc4 went without any issues. One thing I noticed though: When I try to login on the web GUI with any other user than root it simply won't work. I also tried logging in via SSH. If I try to login with any other user than root I get the following console output: ----------------- Ex0danify@SKYFIRE:~$ ssh [email protected] [email protected]'s password: Linux 4.4.19-unRAID. Connection to 192.168.2.100 closed. ----------------- Anybody else with this problem?

If you shutdown the Windows 10 VM normally (not force stop) are you able to start the VM up again and get past UEFI boot? When the VM hangs at the Tianocore UEFI: force stop again, edit the VM, uncheck all but 1 CPU core, Save and try launching the VM again. Does it get past Tianocore UEFI at that point? I Just noticed that my Windows VM won't shutdown at all.... It just keeps saying "Shutting down". I though mabye this problem is Window update related, so l let the VM "Shut Down". On the next morning I checked the machine and it was still "Shutting Down". I tried to boot with 1 core, no difference. Maybe it is a Windows 10 related Issue? Do you have the latest virtio drivers installed? Mine shuts down fine I completly deleted the Windows 10 VM and created a new one with a new virtual disk and everything. It's running fine now. Was a Windows problem then I guess.

If you shutdown the Windows 10 VM normally (not force stop) are you able to start the VM up again and get past UEFI boot? When the VM hangs at the Tianocore UEFI: force stop again, edit the VM, uncheck all but 1 CPU core, Save and try launching the VM again. Does it get past Tianocore UEFI at that point? I Just noticed that my Windows VM won't shutdown at all.... It just keeps saying "Shutting down". I though mabye this problem is Window update related, so l let the VM "Shut Down". On the next morning I checked the machine and it was still "Shutting Down". I tried to boot with 1 core, no difference. Maybe it is a Windows 10 related Issue?

Hello, I don't know if the following problem occours since the 6.2rc2 or rc3: I have a Windows 10 VM which is running quite nicely with GPU Pssthrough and everything. If I force quit the VM via the Unraid WebGUI and start it again, the VM hangs at the TianoCore UEFI. I cant't do anything but fircequit the VM again. The VM will only run again, after a complete Unraid server restart. Anyone else experiencing this issue? tower-diagnostics-20160807-2357.zip

Hey there, I just updated my system and run into a VM releated issue. I'm running two Windows 10 VMs. one of them (always the same one) gets halted (yellow pause symbol in the web UI). There are no information in the system log. It happens a few seconds after the following message in the VM log: ehci warning: guest updated active QH My diagnostics file is attached below The "crashing" VM is the "Guest.log". The functioning one is the "SkyFire (Guest mode).log" tower-diagnostics-20160709-1011.zip