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.

Vanse01

Members
  • Joined

  • Last visited

  1. I have installed another container that I use tailscales with, calibre-web. It is behaving the same way. I can access it via the tailscaleIP:Port or thr tailscale url, but not the unraid provided webui links which is serverIP:port. All the docker containers that do not use tailscale work with the webui link. This started after I upgrades unraid to 7.1.2. So not sure if it a tailscale support issue or upgrade support but it would be great to figure out what changed so I am not surprised down the road when/if some other function is disrupted. Thanks for any help Andrew
  2. I am having a few issues with some of my docker containers after upgrading unraid from 7.0.1 to 7.1.2. and am looking for help. Things that were broken but are now fixed: I have both sabnzbd and qbittorrentvpn installed. both want to use port 8080 so I moved sabnzbd to port 8081, that worked fine before the upgrade but would not load the web interface after the upgrade. I found I had to change the WebUI to http://[IP]:[PORT:8081] in the advanced setting not just in the docker container port type variable. It did work before, but not after until the change in the advance setting. This was 1/2 of the problem with the qbittorrentvpn problem. that container would still not load the web interface if the VPN was turned on. the only way I could fix that was to delete the VPN configuration and reconfigure it. After thatthe webUI would load fine with the VPN enabled. Now to the 2 containers I have not fully fixed yet: both audiobookshelf and komga have tailscale installed so they can be accessed outside my network but only by devices on my tail net. This all works fine. I can still access them both inside my network and out via the taiscale url. But I can no longer access those 2 containers via the internal webUI link that is the {unraidserverIP}:{container port}. All docker containers that do not have tailscale install still work from the internalIP:port but the 2 ones using tailscale will not. I can access the containers so it is not a critical issue but something changed as I was able to access it that way before the update. I always get concerned when there is a change to the server that I do not understand so I would like to restore the internal connection or at least understand why it stopped working. thanks for any help, Andrew
  3. I found the problem/solution. It was a problem with the way I was assigning the VLAN to the server. I was using VLAN override on the client settings rather than changing the VLAN on the port it is connected to. I changed the port default VLAN and turned off VLAN override and now I can boot the VM, it gets its own IP and can access the network.
  4. This is my first attempt at VMs under Unraid. I have 2 unraid servers both similar in hardware configuration. I will list both as I have tried to make the same VM on both with the same issue. Main Server: MB/CPU - MSI z390 carbon pro/intel I9 99ook 64 GB DDR4 ram Nvidia RTX 4060 8gb low profile LSI 9300-16i HBA Mellanox 10gb SPF+ NIC Backup server: MSI z97-sli/Intel i-7 4790 32 GB DDR3 ram Nvidia RTX 3060 LSI 9200-8i Mellanox 10gb SPF+ NIC so as I said I have tried on both but stopped working on the main server when I had issues so I will just go forward with tests on the backup until I get it right. I am assuming the solution to 1 will be the solution to the other as the problem is the same and the hardware is so close. When I create the VM I leave most things default with the following exceptions 2 cpu cores 2048mb ram and I change the primary vdisk location to manual and point it at the Home assistant image file. I leave the network source as br0 and the network modle virtio-net. when I start the VM with console, HA boots up and grabs an IP address from my router but the unraid GUI becomes unresponsive via network. I can still log into the console to shutdown or if i happen to be in the GUI boot mode everything still works but no network access from unraid os. I am thinking that the default VM setting are somehow conflicting with my Mellanox Nic card and are keeping it from working for unraid OS when I go into Tools>system devices, my Mellanox NIC shows up like this [15b3:6750] 03:00.0 Ethernet controller: Mellanox Technologies MT26448 [ConnectX EN 10GigE, PCIe 2.0 5GT/s] (rev b0) would that conflict with the default VM PCI device <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> I am not sure how the address found in the system devices translates to th XML of the VM but it seems to have 5 entries similar that index 1 thru 5 us incement values in the port (0x10 - 0x14) and function(0x0 - 0x4) fields. the domain bus and slot fields are the same for all 5 I would like to have everything work thru the one 10gb NIC but I also have an unused 1gb network port on the MB that could be used for VMs if there is some advantage to that. I currently the onboard NIC unplug but it is configured as bonded listed as active backup. In an ideal configuation the onboard 1gb would be a failover for the 10Gb and both unraid OS and VM would go thru whatever is available but for now if i can just get the VMs working on one or the other I could progress. I did search around a little but did not find a discription of how the PCI device address of physical devices are converted to the XML format of the VM config file. the few posts i did see were about passing a GPU thru to the VM which will be the next project on a 3rd server after HA get setup on the main machine. So hopefully I can learn from my mistakes here for future projects. Thanks in advance for any help the community can provide Andrew
  5. I thought the i9 would be better for plex, I did plan on putting a 3060 or 2080ti in for trancoding. Is the i9 better for that then the dedicated gpu?
  6. If the i7 can handle the server workload I would use the i9 9900k for something else, it is still a viable gaming processor, the i7 4700 not so much.
  7. I am working on my first unraid build and could use some advice. I have 2 MB/processors to chse from. Msi z97-g55 sli with a i7 4790k and a msi z390 gaming carbon pro with a i9 9900k. The server will primarily be for storage but I would like to get a plex server going as well. Ether MB/processor choice will get the same additional hardware. 8x 8tb 4kn drives 1x 9207-8i controller 2x samsung ssd for cache pool 16gb ram 3060 graphics card I would like it to be a power light as possible and I don't plant to be using the plex server for much at least at the beginning. My question is how much does unraid and or plex benefit or get hurt by the older mb/processor combo. Any other advic3 would be great Thanks

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.