Thorsten Gehrig

Disregard my question. I re-installed from the appstore => the image changed the location. THe new location has an updated version... running again 🙂 Best THorsten

Hi seems the "siwatinc/homebridge_gui_unraid" doesnt work anymore 😞 I guess it´s related to outdated npm/node (node 12.20.1 is installed but they are looking for node >=14) npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":"^18.15.0 || ^20.7.0"} (current: {"node":"12.20.1","npm":"6.14.10"}) npm WARN notsup Not compatible with your version of node/npm: [email protected] npm WARN notsup Unsupported engine for @homebridge/[email protected]: wanted: {"node":">=14"} (current: {"node":"12.20.1","npm":"6.14.10"}) npm WARN notsup Not compatible with your version of node/npm: @homebridge/[email protected] Is there any chance this gets fixed - or do i have to find an alternative docker for homebridge? So far it worked like a charm for me ... Thank you i advance Best Thorsten

I have removed my cache drive (disk was broken) and moved the docker image to the main pool - hence from brass to xfs. The image is still xfs. Does that matter? (I have also some instability... and wonder if this could be a root cause). Beside that: any advise how to convert? I don't want to re-buil all my docker (there are still several settings manually made and not backuped for separate restore) Best Thorsten

"Stupid" question. I´ve installed Nerdtools a while ago - then i removed it later. I still see during the boot process that nerdtools are there and get updated each boot. Is this correct as this is included since 6.11.x - or is this a leftover from the install/remove action? Best Thorsten

Hi i have on my unraid also dockers setup as "Network type: custom (bro)" and Fixed IP Address (example) 192.168.0.20 while unraid itself does run un 192.168.0.10. This works like a charm - BUT only docker containers cannot connect to those IP Address. Other clients in the network have no issue. As I'm nowadays transferred my reverse-proxy into a docker - those docker cannot connect to the example docker session. I´m guessing this is due to IP-Tables? I´m guessing the chain "DOCKER" doesn't accept any packages traveling from a 172.17.0.0/24 container to another container which is e.g. 192.168.0.20 ... but i haven't enough clue on the detailed routing. Does anyone can provide me a hint? (where to look, what to try) And finally: how can i make any iptables rules persistant? Thank you in advance Kind regards Thorsten Gehrig

Hi thanks - i wasn't aware that this automatically re-shares. unfortunainlty i still see the issue - even the user have read/write access in the ID settings. Mac still shows error -50 when i want to create files (while it creates an empty file only) Any idea where to check logs? Best Thorsten Gehrig

Hi, i have the following situation & problem: Unraid - unassigned Devices - mounted a DROBO share via SMB. Now i´ll try to re-share via Unraid. I´ve created an SMB share where the DROBO Share is linked. Accessing this share from my Mac does work perfect for reading. I can also save files to the main directory of the directory. For the mounted DROBO shares i can read but not write files. I´ll receive a "-50" unknown error code... Is there any hint? Logfiles to check? I´m open for any hints. Kind regards Thorsten Gehrig