Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Victicious

Members
  • Joined

  • Last visited

  1. I'd love to see an option to add your own background. I poked around in the container for a possible path, but it looks like it's wrapped up in the app executable. Has anyone picked this up yet?
  2. I was also getting a server error when trying to start the container after update. Upon inspection, I noticed the template added the port 5900 mapping, and since a running VM on my server was already using port 5900 for VNC access the container wouldn't start as a result. I removed the port 5900 mapping and everything was fixed. I've always only had port 6080 mapped and have always accessed the web GUI over this port instead. My question is should I be using port 5900? Is there a reason for both port mappings?
  3. For anyone coming across this in the future, twiikker's "Preferred Alternative for recent libvirt + qemu" XML edit in the link above worked for me. My setup is a Dell R720XD with multiple GPUS running Unraid 6.9.2 stable in Legacy Mode. For some reason, GPUs populated in certain PCIe slots would always throw error code 43 once the NVIDIA driver was loaded. They also would not work with Linux VMs once the NVIDIA Linux drivers were loaded. I figured it was the driver detecting the virtual environment because before loading NVIDIA drivers, the GPUs would indeed output video using either default Linux display drivers, or the Microsoft Basic Display Driver. However, once the NVIDIA driver loads, bam, no more video output on Linux and code 43 in Windows! Using twiikker's suggestion, all I had to do for those GPUs with error, was add the following to my XMLs for those VMs: <domain> ... <features> ... <kvm> <hidden state='on'/> </kvm> ... <hyperv> ... <vendor_id state='on' value='whatever1234'/> </hyperv> ... </features> ... </domain> That's literally all I did and it's been fixed ever since. This has worked for both an EVGA GT 1030 and Zotac GT 710 (PCIe x1) cards. Both had VBIOS's dumped by myself on the same system using Spaceinvader's CLI technique. This seems to be an issue that can still occur, perhaps especially on these lower end cards, and depending on specific hardware configurations. Hopefully this helps someone in the future and saves some blood, sweat, and tears!

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.