beire

I had the same issue since updating to unraid 7.1.4 from 7.0.0. The unraid-api command was not there. While installing the connect plugin i could see a message that said unraid-api was not in PATH. i noticed that when i did ls -la /usr/local/bin/unraid-api this returned a directory. On my other server this is not. So i renamed this directory and reinstalled the connect plugin. The PATH error message was gone (now has a check next to it instead of a cross ) and after a few minutes i could sign in to my unraid account. This is what you should see when running the ls command. This is what was there before and me renaming the folder.

Hello @Helmonder Nice build, have you got any idea on power usage of the complete build ? Looking to update my old xeon setup which is using around 150W at idle.

Thank you. I just downloaded the datasheet, am I right the only difference between CRC and ctd type is the frequency difference 2400 Vs 2666? The datasheet does indeed state they are backwards compatible.

Hello, I have a unraid server with currently 32gb ( 2x Samsung M391A2K43BB1-CRC ) of ram memory. I am in need of extra ram ( preferably to 64gb) but it seems the current ram sticks are unavailable in most shops. One local shop gave me the following options: - 2x Samsung M391A4G43AB1-CVF 32gb sticks - 4x Samsung M391A2K43BB1-CTD 16gb sticks Whats is the difference between my current M391A2K43BB1-crc and the other CTD type? Can i mix these CTD type with my current CRC type memory, preventing the need to buy 4 sticks? The shop tells me not to mix with my old memory and i think i would follow them but it would be a waste of money if there is nog a valid reason for it. Or are there other options? Between these 2 options, what is the better? Thank you all for helping.

How is the influxdb node set up? Is the influxdb running on node-red docker (localhost?) Sent from my ONEPLUS A6013 using Tapatalk

Are you saving data IN the node-red docker? Sent from my ONEPLUS A6013 using Tapatalk

adding --user=root seems to have worked. Thanks!

Spants, I use a USB adapter passed through to your node-red docker. The ttyUSB1 device is owned by root and node-red does not have access to it. I can chown ttyUSB1 to node-red user, then it works. But this obvisously does not survive a reboot. Can this be changed? Thx

Are you also still using spants's original docker? You should migrate to the newer official node-red template by spants. You are running 14.7 while the official docker is at 15.7(?). Sent from my Pixel XL using Tapatalk

If your problem is what spants is referring to you should have a flows.json file in the node-red appears folder. This file would be empty. Your old flow.json file should still be there in that same folder. You should backup that file, remove the newer(empty) flows.json and rename your old flow.json file to flows.json If what I seem to remember is correct [emoji14] Sent from my Pixel XL using Tapatalk

Nice build! Where did you get the long pci-e extension cables? I like those...

Is there a disadvantage to using the nextcloud update button in the admin panel vs manual? I previously thoughts manual was the only way. Sent from my Pixel XL using Tapatalk

Hmm. I updated node-red docker to 0.16. Now I crashed after a few minutes minutes with a memory error. Can I easily revert back to 0.15.2 to test is if it was really the new version causing this? Edit: Never mind, I think it's related to a node compatibility issue. I think it's a Samsung-tablet remote node. But I need to investigate more.

Unraid wouldn't be the same without the app store and spant's repo

Isn't it easier to use the app store plugin to install Docker's?

The old node-red image is deprecated i think. You should install the nodered-official image. Your appdata folder van stay the same. Just the flow file you should rename to flows. Just do a backup beforehand! The official image is current 0.15.2 Sent from my Nexus 6 using Tapatalk

You must install new nodes with the new palette editor in 0.15 of the admin tab in 0.14. It's normal that the nodes dissapear when i stalling manually via command line. Changes made in any docker container that are not mapped to a drive in your unraid (appdata) share are never persistent.! Sent from my Nexus 6 using Tapatalk

I had to log out of all servers and log back in as (root) to see my dockers and vm's again. Works fine afterwards though! Sent from my Nexus 6 using Tapatalk

Hmm.. was this discussed in the group? I've been neglecting my reading there due to time constraints so i must have missed it. Sent from my Nexus 6 using Tapatalk

Thx. Announcements for your docker or node-red in general? Sent from my Nexus 6 using Tapatalk

Oh. I Saw it was installatie through npm so thought it should be available already. Sent from my Nexus 6 using Tapatalk

The new node-red-dashboard can not be installed by the admin tab. May be a nice to add to the docker?

Jbrodriguez, Just tried 1.2.4 and my beta23 servers added just fine now!! I'll try the rc1 later, i don't have the password here now. Don't know what cjanged but thanks!! Sent from my Nexus 6 using Tapatalk *Edit: Bingo. Rc1 server also added!

Sorry but still not working. Automatic Discovery scans up until my servers ip, then stops there doing nothing. Manual add same as before, stuck at adding host. Sent from my Nexus 6 using Tapatalk

I never really noticed a problem on any of the unraid servers regarding networking and bridge. And certainly no errors in the logs either. I'll see how the new version goes then. Sent from my Nexus 6 using Tapatalk