alexfsr

Indeed i have figured out what's going on. You are correct, http://IPAddr works. The reason it wasn't working before was because i never write the http part, just the IP address in the browser field. Coincidentally, i remembered that Chromium based browsers started defaulting awhile back to https unless specified (and my server indeed doesn't have SSL because i could never figure out how to set it up properly. It never worked and caused the server to become completely inaccessible when i last tried to enable it with self-signed/generated SSL). Thank you!

Ok I tried to boot a fresh image of UNRAID configured from the disk imager with the same network settings (static IP, same IP as the original one). The fresh install was again refusing the connection when accessing via the IP address but it worked with "http://tower.local". After i setup a password and got to the main screen, i tried accessing the server with the IP address and it worked. I then went back and booted my orignal flash drive and that one also allowed the connection to the WebGUI via the .local domain. But it still refuses connections when using the IP address. What's going on? Seems to be something with the networking configuration but i don't see anything wrong with it and it hasn't changed since the last time i worked on the server and using the IP to access the WebGUI worked fine. I'll update everything now to see if it fixes but i really don't understand what's going wrong. EDIT: Running lastest stable verion of UNRAID now, all plugins updated. Docker and VM manager disabled. Still no access via IP.

Ok. That's not gonna mess up the HDD array, right?

I have never used the local domain nome to access the server, only IP (static). I don't believe my router is configured for it to work either but i can try it now. It's serverName.local , right?

Hi, I've been using UnRAID for a few years now for my family's NAS and Plex Server (docker). A while back, I also hosted a Windows 10 VM for my mom to use when she does her arts and craft (the server lives in the same room and it has more than enough power to handle light browsing and zoom calls). It has been working fine for a while but the Windows VM started having issues with the GPU recently (driver time out) so i decided to investigate during Christmas break. However, when i went to login to the server, i was faced with a "Connection Refused" error message. The server continues to work just fine as a NAS, all shares are accessible on the network. SSH works as well. But the webGUI is dead for no appearant reason. So far i have tried: Safe mode - No change. Renamed the virtual disk file for the VM to stop it from auto-starting on boot (i couldn't figure out how to stop it with virsh) - VM doesnt start anymore but GUI still missing. Changed the USB port of the boot flash drive. Checked the flash drive on another PC. It reads fine and seems to have all the server files on it as normal. Checked via local terminal with df command - the flash drive seems to properly mount at /boot. Generated a diagnostic zip with the command from local terminal - successfully saved to the flash drive and attached to this post. I don't know what else to do. This server hold a sh*t load of family data and I need to restore it ASAP but i have no idea what's wrong with it. Everything seems to be fine and works fine except for the web GUI. Any ideas? homenas-diagnostics-20230107-1825.zip

I did. But i do want to use SSL but use self-signed cert and just have it redirect 192.168.x.x to https://192.168.x.x

hmmm. Manually putting in the https in front makes it work. wtf?? https://192.168.x.x/ works 192.168.x.x/ redirects

I always do that. But after i enabled SSL it redirects to this "homenas.local" immediately and the browser throws an error because it can't find that (how could it, there is no such thing).

Just upgraded from 6.3.3 and decided to enable SSL. The intention was to use a self-signed cert and keep the server inside my local network. The moment i switched SSL to Yes i lost connection to my server. It redirects to "homenas.local" bullsh*t that windows cannot resolve because the f*ck is that??? I cannot connect to the server's web interface now. How do i disable this shit from a local terminal on the server machine itself to restore connectivity? ***The server has critical data on it and i'm super pissed.

Hello everyone, I'm pretty new to unRAID and VMs. I installed unRAID on an old (but beefy) PC of mine that i used to host servers on (TS3, MC, SE, etc.) in order to convert it into a family NAS as well as use its VM capabilities to run a windows 10 to host my servers. I plugged in 4 4TB drives (1 is parity) and a 128 gig SSD for cache and the NAS runs like a charm. Now onto VMs. I cannot get it to work with passthorugh devices. If i set the VM to use dedicated GPU or the motherboard's sound card, it gives IOMMU errors (below) and doesn't start. If i select VNC as graphics and no sound at all, it runs fine. I tried useing PCIe ACS override but no luck with it either. From what i could gather from extensive google-ing, it seems like proper VT-d support on the chipset i'm using is pretty hit/miss . Machine Specs: Asus P6X58D Premium | Xeon X5650 | 12GB DDR3 RAM | GTX 1050 | RX 480 | 4x4TB NAS drives | 128GB SSD for cache | 120GB SSD for VM vDisks. GTX 1050 is in the top PCIe slot to be used by unRAID. I'm trying to passthrough the RX 480 to the VM (second PCIe Slot). Any idea how i can fix this without getting a new mobo because that's kind of not possible atm (and my friends are w8ing for my servers )? IOMMU report: IOMMU group 0 [8086:3405] 00:00.0 Host bridge: Intel Corporation 5520/5500/X58 I/O Hub to ESI Port (rev 13) IOMMU group 1 [8086:3408] 00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 (rev 13) IOMMU group 2 [8086:3409] 00:02.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 2 (rev 13) IOMMU group 3 [8086:340a] 00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 13) IOMMU group 4 [8086:340e] 00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 13) IOMMU group 5 [8086:342e] 00:14.0 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub System Management Registers (rev 13) [8086:3422] 00:14.1 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 13) [8086:3423] 00:14.2 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 13) [8086:3438] 00:14.3 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub Throttle Registers (rev 13) IOMMU group 6 [8086:3a37] 00:1a.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 [8086:3a38] 00:1a.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 [8086:3a39] 00:1a.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 [8086:3a3c] 00:1a.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 IOMMU group 7 [8086:3a3e] 00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller IOMMU group 8 [8086:3a40] 00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1 [8086:3a44] 00:1c.2 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 3 [8086:3a4a] 00:1c.5 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 6 [11ab:4364] 05:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12) [11ab:4364] 06:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12) IOMMU group 9 [8086:3a34] 00:1d.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 [8086:3a35] 00:1d.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2 [8086:3a36] 00:1d.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3 [8086:3a3a] 00:1d.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1 IOMMU group 10 [8086:244e] 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90) [1106:3044] 08:02.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev c0) IOMMU group 11 [8086:3a16] 00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller [8086:3a22] 00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller [8086:3a30] 00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller IOMMU group 12 [1b4b:9123] 01:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9123 PCIe SATA 6.0 Gb/s controller (rev 10) IOMMU group 13 [1033:0194] 02:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03) IOMMU group 14 [10de:1c81] 03:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050] (rev a1) [10de:0fb9] 03:00.1 Audio device: NVIDIA Corporation Device 0fb9 (rev a1) IOMMU group 15 [1002:67df] 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] (rev c7) [1002:aaf0] 04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aaf0 IOMMU group 16 [8086:2c70] ff:00.0 Host bridge: Intel Corporation Xeon 5600 Series QuickPath Architecture Generic Non-core Registers (rev 02) [8086:2d81] ff:00.1 Host bridge: Intel Corporation Xeon 5600 Series QuickPath Architecture System Address Decoder (rev 02) IOMMU group 17 [8086:2d90] ff:02.0 Host bridge: Intel Corporation Xeon 5600 Series QPI Link 0 (rev 02) [8086:2d91] ff:02.1 Host bridge: Intel Corporation Xeon 5600 Series QPI Physical 0 (rev 02) [8086:2d92] ff:02.2 Host bridge: Intel Corporation Xeon 5600 Series Mirror Port Link 0 (rev 02) [8086:2d93] ff:02.3 Host bridge: Intel Corporation Xeon 5600 Series Mirror Port Link 1 (rev 02) [8086:2d94] ff:02.4 Host bridge: Intel Corporation Xeon 5600 Series QPI Link 1 (rev 02) [8086:2d95] ff:02.5 Host bridge: Intel Corporation Xeon 5600 Series QPI Physical 1 (rev 02) IOMMU group 18 [8086:2d98] ff:03.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Registers (rev 02) [8086:2d99] ff:03.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Target Address Decoder (rev 02) [8086:2d9a] ff:03.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller RAS Registers (rev 02) [8086:2d9c] ff:03.4 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Test Registers (rev 02) IOMMU group 19 [8086:2da0] ff:04.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Control (rev 02) [8086:2da1] ff:04.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Address (rev 02) [8086:2da2] ff:04.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Rank (rev 02) [8086:2da3] ff:04.3 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Thermal Control (rev 02) IOMMU group 20 [8086:2da8] ff:05.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Control (rev 02) [8086:2da9] ff:05.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Address (rev 02) [8086:2daa] ff:05.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Rank (rev 02) [8086:2dab] ff:05.3 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Thermal Control (rev 02) IOMMU group 21 [8086:2db0] ff:06.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Control (rev 02) [8086:2db1] ff:06.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Address (rev 02) [8086:2db2] ff:06.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Rank (rev 02) [8086:2db3] ff:06.3 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Thermal Control (rev 02) Error log from trying to launch a VM: 2017-04-27 16:01:30.249+0000: starting up libvirt version: 2.4.0, qemu version: 2.7.1, hostname: HomeNAS LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-4-Windows 10/master-key.aes' -machine pc-i440fx-2.7,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/9763e8eb-2b5a-476f-9175-233c612de194_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 4096 -realtime mlock=off -smp 4,sockets=1,cores=2,threads=2 -uuid 9763e8eb-2b5a-476f-9175-233c612de194 -display none -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-4-Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device nec-ws 10/org.qemu.guest_agent.0,server,nowait' -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device vfio-pci,host=04:00.0,id=hostdev0,bus=pci.0,addr=0x6 -device vfio-pci,host=00:1b.0,id=hostdev1,bus=pci.0,addr=0x8 -device usb-host,hostbus=7,hostaddr=3,id=hostdev2,bus=usb.0,port=1 -device usb-host,hostbus=7,hostaddr=2,id=hostdev3,bus=usb.0,port=2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x9 -msg timestamp=on Domain id=4 is tainted: high-privileges Domain id=4 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2017-04-27T16:01:30.366602Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio: failed to set iommu for container: Operation not permitted 2017-04-27T16:01:30.366635Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio: failed to setup container for group 15 2017-04-27T16:01:30.366641Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio: failed to get group 15 2017-04-27T16:01:30.366657Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,id=hostdev0,bus=pci.0,addr=0x6: Device initialization failed