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.

jr37

Members
  • Joined

  • Last visited

  1. Thank you, currently trying to get it fixed. So am I correct that in addition to the default 192.168.1.0/24, I need the LAN address for the network that my server is connected to (in order to access the unraid UI and the qbittorrent UI)? Or does 192.168.1.0/24 refer to the server's local network? Sorry, I'm relatively new at this.
  2. Is this the setting you are referring to (inside the qbittorrent docker settings)?
  3. I tried switching to wireguard and updated the wireguard conf file to a different endpoint (changed from the Netherlands default), but when I try to access the webUI, the connection times out (it timed out before I changed the default endpoint as well). Currently, I am not on the same network as my server, I am using wireguard hosted on my server to connect to the network my server is on and I can access the unraid webUI but not qbittorrent. Any idea why it might not be working? Thanks.
  4. jr37 joined the community
  5. I recently had to reinstall Unraid on the flash drive I have been using as my boot drive. I did this successfully, but I have no previous backup, and I didn't save any information about the exact configuration of my raid array (i.e. what was/were the parity drive(s) and data drives). I have three 1TB drives, one 2TB drive, and a 256GB SSD. I know that more than likely the 2TB drive was a parity drive, but I am unsure about the others. I followed the instructions on this page https://docs.unraid.net/unraid-os/manual/changing-the-flash-device/ and it suggested I use Unassigned Devices to figure out which drives are not mountable, as those are most likely the parity drives. The 2TB drive is in fact unmountable, but so are two of the 1TB drives (so only one of the 1TB drives and the 256gb SSD are mountable). It doesn't make sense to me that I would have 3 out of 5 drives be parity drives. The instructions on that page suggested I ask in the forums. Here is the result from the syslog file when if I try to mount the unmountable drives: Dec 25 14:25:22 rupert-media unassigned.devices: Error: Device '/dev/sdf1' mount point 'ubuntu-server:0' - name is reserved, used in the array or a pool, or by an unassigned device. Dec 25 14:25:22 rupert-media unassigned.devices: Disk with serial 'TOSHIBA_HDWD120_30FM34JAS', mountpoint 'ubuntu-server:0' cannot be mounted. Dec 25 14:26:39 rupert-media unassigned.devices: Error: Device '/dev/sdd1' mount point 'ubuntu-server:0' - name is reserved, used in the array or a pool, or by an unassigned device. Dec 25 14:26:39 rupert-media unassigned.devices: Disk with serial 'TOSHIBA_HDWD110_27C048VFS', mountpoint 'ubuntu-server:0' cannot be mounted. Dec 25 14:37:16 rupert-media unassigned.devices: Error: Device '/dev/sdf1' mount point 'ubuntu-server:0' - name is reserved, used in the array or a pool, or by an unassigned device. Dec 25 14:37:16 rupert-media unassigned.devices: Disk with serial 'TOSHIBA_HDWD120_30FM34JAS', mountpoint 'ubuntu-server:0' cannot be mounted. Dec 25 14:37:22 rupert-media unassigned.devices: Mounting partition 'sdc1' at mountpoint '/mnt/disks/ubuntu-server:0'... Dec 25 14:37:22 rupert-media unassigned.devices: Mount cmd: /sbin/mount -t 'xfs' -o rw,relatime '/dev/sdc1' '/mnt/disks/ubuntu-server:0' When the two mountable drives are mounted, a grayed out button will appear next to the unmountable drives that says "Reboot." Any help would be appreciated! (FYI, I have rebooted the server several times, the issue persists).

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.