Leaderboard

Hi, I have a feature request for some form of unraid API. I have been using Unraid for along time now and was using with with esxi. Since v6 it has taken over as my host machine and I am doing more with it than ever. I did notice there was a previous request for this in December 2014, Link, for an API but this was highlighted as not a priority at the time and given that unraid v6 was still in early beta stages this makes sense. At the moment almost all the control requires ssh/telnet or web console access. This to me poses a potential security risk and think that an API might be able to provide access to some of the commonly used functions without providing access to all the system functions of unraid. Some of the features that I would like to see in this this API are below: Access token to bypass the basic authentication for API. Possible multiple tokens with different access. example tokens, Global, Docker only, VM only, System only, Docker and VMs only, Plugins.... This could be managed via a webpage with automatically generated token but be able to be manually set or regenerated. Some form of system/docker/vm overview that is easily obtained. I use Zeron's jsonvars plugin to provide me with information about the server for some of my home automation applications and monitoring. I also use SNMP and each has there own advantages. Potentially make the API available for plugins to publish information. Docker remote control. Ability to start/stop/restart containers would be the starting point. I am sure there would be other things that people might like to see. VM remote control. Ability to start/stop/restart vm's would be the starting point. This might be a work around the physical power button problem that has been requested, for example an arduino, home automation system or even IFTTT could be used to send commands. Unraid system control. Starting, stopping, powerdown, restart, start parity, spinup, spindown check etc. This should probably should be limited to non destructive system functions as to limit malicious/accidental control. This may make it easier for third-parties to develop monitoring plugins or integration into automation systems. There could be an option to provide some form of share control. I have recently become more Ransom-ware aware and have put in processes to try an limit damage in the event of an attack. Some of the suggestions on this forum are to change the user share from read-only to write when needed. An API could potentially change a share from read/write status of a share. The control of this could handled by the user in the form of a script or webpage etc. Possibility to run command-line command/scripts. This goes against my non-destructive comment above but could be useful for anything not covered by the API. It probably should have it own API token. There is the possibility that this may be able to be done as a plugin. It might be a good starting location but I still think an API should be part of the core unraid functionality. I have noticed a few businesses/enterprises these days embracing API strategies, (example Telstra Australia) and they usually cite the collaboration, efficiency and development benefits. I have seen first-hand what having everybody developing their own backdoor/link to systems can have, especially on the inability to control system load and when trying to upgrade/change systems. The development and documentation of an API is no small task but I think it might unlock some key development/features for the future of unraid.

I have a Bluetooth dongle that I want to use in a docker container. Docker requires that the Host OS install drivers for the device before it can be passed to the container. Searching the forums it appears I am not alone in that need, particularly for the users of Home Assistant. See this post for more info:

On its way

Windows 10 SMB is a bit of a mess. MS keeps making changes to it on the basis of increasing security. And each of the three main varieties (Home, PRo and Enterprise) are all at different points in the progress. But you can begin by reading this page and see if anything there will fix your computer so that it will work. https://lime-technology.com/forums/topic/53172-windows-issues-with-unraid/?page=2 One quick thing that you can try is to enter the IP address of your server on the Address Bar of Windows Explorer (Not IE) in this format: \\192.168.1.243 Please note the backlashes!!! If this brings up the shares on your server, You can then right click at the left end of that Address Bar and drag it to your desktop. Then create a shortcut on your desktop.

I'm getting 5+MB/sec, up and down, on a 50Mbps connection.

This may sound obvious, but here goes. The CPU die is where the heat is produced. The heat has to be transferred from the inside of the CPU to the CPU case, to the heatsink, to the air inside the case, and moved outside the case. You have to figure out where in the chain the heat is being trapped. The CPU die to case is factory sealed, so that's not typically an issue, the CPU case to the heatsink relies on a solid mechanical connection, with heatsink compound to fill in the little voids between the heatsink and CPU case. The heatsink needs airflow with enough temperature differential to absorb all the heat produced. Either a large volume of warmish ambient air, or a smaller volume of cold air. Follow the heat to find the issue. If the heatsink isn't overly warm when the alarms are going off, then check heatsink compound and fitment of the heatsink to ensure a good tight connection. If the heatsink is piping hot, then chase down the airflow issue, fans, dust, ambient temp, whatever.

Seems to be. Others have experienced this problem with Deluge and large numbers of torrents. rtorrentvpn seems to handle this better.

@Altheran It's being worked on

These keyboard issues are solved in the upcoming unRAID 6.6 -- it includes an updated version of QEMU that has the keyboard mappings fixed.

Solved the problem for anyone needing it...(probably myself in the future when i forget after a server crash!) Hard linking within user shares is possible however you need to keep to one user share only! For example - /data <-> /mnt/user/Torrent Downloads/ Then create your desired folders (Kids/Adults/Dogs whatever) in the same user share the /data is mapped towards which will be for this case /mnt/user/Torrent Downloads. Radarr will then hard link across all drives within that ONE share not duplicating copy's. finally!

I had a similar problem and found this thread. All of my USB devices were showing as being on the xHCI USB controller and therefore in the same IOMMU group. Didn't matter the devices were plugged into USB 2.0 ports on different USB headers. Stupid BIOS! Tried different options with the few USB BIOS options but nothing was working. These started thinking, since xHCI is for USB 3.0 devices, I thought if that controller were not there, the USB 2.0 devices would have to go somewhere. Sure enough, disabling USB 3.0 broke apart my USB 2.0 devices to their proper EHCI controllers, so I can pass through one and not affect the unRAID USB stick. Loosing USB 3.0 support kinda sucks, but for my use case, losing passthrough was worse. My motherboard is an ASRock C226M WS. My other ASRock (E3C224-4L) did not have this issue. Hope I have enough of the right search terms in there to help others find this if they are having a similar issue.

I was having the same problem, and figured out a solution. The codec needs to be updated inside the docker. Here are the steps I took to accomplish this: 1. ssh into your Unraid server (I am on Windows and use Putty) 2. Run the following command to be able to make changes inside the Air Video HD container: docker exec -it <container_name> bash (<container_name> should match what you see in the Unraid GUI, my was "AirVideoHD" so my command was "docker exec -it AirVideoHD bash" without the quotes) 3. You should now be making changes inside the container - the h.265 codec plugin is not available from the Ubuntu repositories, so you will need to add a repository: sudo apt-add-repository ppa:strukturag/libde265 4. Update the packages from the newly added repository: sudo apt-get update 5. Install the h.265 codec plugin for VLC: sudo apt-get install vlc-plugin-libde265 6. Type "exit" to return to the Unraid command line (No longer making changes to the Air Video HD container) 7. Restart AirVideoHD docker container from Unraid GUI (may not be necessary, but I wanted to make sure the changes stuck after the container was restarted) I was successfully able to stream and download videos using the h.265 codec and no longer received the "missing codec" error. (Air Video Converted the files to download to iOS) I am not sure if this container is still being maintained, as it has been over a year since the last update, but if it is, then hopefully this can be included in the next update. Hope this helps anyone having problems playing h.265 video files!