-
Can't access the WebUI after a faulty shootdown.
Is this too complicated? I have no idea how to do that, should I just follow the folder structure? also, I removed one of the GPUs and now even the shares are not running... I'm wondering how to not loose all of my shares, the USB has all the configuration inside? whiteserver-diagnostics-20241107-0614.zipwhiteserver-diagnostics-20241107-0614.zip
-
Can't access the WebUI after a faulty shootdown.
-
Can't access the WebUI after a faulty shootdown.
It doesn't work. It will just not answer, accessing with the name or with the IP has the same result, although SMBs and pings to it are working without any problems...
-
Can't access the WebUI after a faulty shootdown.
Here they are whiteserver-diagnostics-20241104-1040.zip
-
-
Can't access the WebUI after a faulty shootdown.
I have my Server connected to a UPS, and after a power outage, I sent a shutdown instruction to my UNRAID server. However, it seems the UPS may not have lasted long enough for the server to fully shut down. This appears to have caused an issue, as now I can’t access the WebUI. I've tried searching online but haven't been able to determine the cause of the problem or how to resolve it. I've rebooted the server several times to try to get the WebUI working, but without any luck. Unfortunately, it seems that this also creates another issue since the diagnostics are cleared after each reboot. I'm far from being an expert, and I've barely tweaked my server at all. I’ve seen other posts about similar issues, but they’re hard for me to understand. I hope you can dumb it down a bit. I hope someone can help me. Thank you! Might be relevant: `/etc/rc.d/rc.nginx status` Nginx is running I recently upgraded to the latest version (I'm not sure if this is causing the issue or if it is related) unRAID Server OS version: 6.12.13 Linux 6.1.106-Unraid "IPv6 address: not set" whiteserver-diagnostics-20241104-1040.zip
-
6.9.1 Problem with Docker containers and NAT Port Forwarding
Amm, have you checked in LAN? in my case a similar thing happened and I can't access ports even in the same LAN. After checking with Advanced Port Scanner, it will show every docker port closed, although unraid ports are working: Port 21 (TCP) vsftpd Misconfigured Port 22 (TCP) OpenSSH 8.4 protocol 2.0 Port 23 (TCP) Linux telnetd Port 80 (TCP) nginx Port 111 (TCP) rpcbind Port 139 (TCP) Samba smbd 3.X - 4.X workgroup: WORKGROUP Port 445 (TCP) Samba smbd 3.X - 4.X workgroup: WORKGROUP I recently moved my entire network (including my router) to a new house (just a modem swap) and now I can't access my servers although anything that does not require a port seems to be working fine (everything on my VMs) Any help is appreciated.
-
6.9.2 - Plex HW transcoding, low GPU usage and buffering
You are not impliyng that @sodennis solution does the same, correct? Because I/O doesn't seem to be the problem. I'm running a Win10 VM with plex using hardware acceleration (transcoding) on a NVIDIA Quadro P2000 and this are the stats: CPU - 15% Memory - 19% Disk - 0% Ethernet - Sent: 20.3 Received: 57.8 (I have a 1 gb internet connection but I'm testing locally) GPU - 18% : 3D - 1% Copy - 0% Video Encode - 7% Video Decode - 18% Dedicated GPU memory usage - 1GB out of 5 Shared GPU memory usage - 0.2 out of 8GB Reading from the array at 14 MB/s maximum I have the understanding that the max is at least 80 MB/s from an array full of 7200rpm HDDs I have no idea why whould it buffer