# Roon Extension Manager v0.11.9 \[Obsolete\] **URL:** \ **Category:** Roon API\ **Created:** [June 5, 2017, 9:50am UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632 "2017-06-05T09:50:08Z")\ **Posts on this page:** 20\ **Page:** 22
**Author:** ![Marcor](https://community.roonlabs.com/letter_avatar/marcor/32/5_5575768a8748004e209b776fc1b2916d.png) [@Marcor](https://community.roonlabs.com/u/Marcor)\ **Post date:** [May 9, 2020, 10:28pm UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632/424 "2020-05-09T22:28:50Z")
that was exactly my feeling, even because, just as a test, I tried also to update the diet pi version and the update failed as well. I cannot understand how this keep happening. I am sure that in the past, while cleaning the floor, the plug once or twice could have been unplugged, but I am pretty sure it didn’t happen this time, as the screen of the web controller was still showing the last song that was playing 2 days ago. I clicked on it and it waked roon up but after that the screen was frozen. I did a remote reboot and then I got the message that web controller wasn’t starting and then I realised REM wasn’t there. So far I haven’t managed to understand what trigger the issue. I have re-installeld the image and now everything is working as expected. I even updated REM to the latest version. A suggestion to all the users who don’t know this, you want to make sure you have a backup image of the system somewhere. Once your system is up and running spend 20 minutes making a backup img. If something happen you just reinstate it rather than re-installing all by scratch. M ---
**Author:** ![RobOK](https://community.roonlabs.com/user_avatar/community.roonlabs.com/robok/32/148502_2.png) [@RobOK](https://community.roonlabs.com/u/RobOK)\ **Post date:** [July 22, 2020, 7:13pm UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632/425 "2020-07-22T19:13:56Z")
Could someone post more basic instructions for Mac OS? It seems I need Homebrew to then install Node.JS, is that where I start? Then i install Git. Seems like a lot of work to get Extensions… Any tips appreciated… ---
**Author:** ![Rugby](https://community.roonlabs.com/user_avatar/community.roonlabs.com/rugby/32/360588_2.png) [@Rugby](https://community.roonlabs.com/u/Rugby)\ **Post date:** [July 22, 2020, 7:26pm UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632/426 "2020-07-22T19:26:57Z")
Do you have a pi running dietpi? ---
**Author:** ![RobOK](https://community.roonlabs.com/user_avatar/community.roonlabs.com/robok/32/148502_2.png) [@RobOK](https://community.roonlabs.com/u/RobOK)\ **Post date:** [July 22, 2020, 7:35pm UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632/427 "2020-07-22T19:35:57Z")
I think i got it. Homebrew brew install node brew install git paste command to run it set up Automator this is all on MacOS for me ---
**Author:** ![Jan\_Koudijs](https://community.roonlabs.com/user_avatar/community.roonlabs.com/jan_koudijs/32/48346_2.png) [@Jan\_Koudijs](https://community.roonlabs.com/u/Jan_Koudijs)\ **Post date:** [July 23, 2020, 7:16pm UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632/428 "2020-07-23T19:16:45Z")
### Roon Extension Manager v0.11.6 is now available This time a small update to improve usability while installing Docker based extensions, like CD Player/Ripper. When no Optical Drive Path is supplied during installation then `/dev/cdrom` is now used as the default. `/dev/cdrom` refers to the first detected drive. In a basic (Raspberry Pi) setup this is probably the USB drive you connected. This makes the drive likely to be detected without supplying detailed settings. ![default-docker-settings](https://roon-community-uploads.s3.amazonaws.com/original/3X/1/a/1a2597bd2981c37a1a61761e8812fb15f968607f.png) ### Bug fix release v0.11.7 This release fixes a bug in the handling of OS signals which caused the logging of Extension Manager output to be turned on unexpectedly. ---
**Author:** ![seagull](https://community.roonlabs.com/user_avatar/community.roonlabs.com/seagull/32/48296_2.png) [@seagull](https://community.roonlabs.com/u/seagull)\ **Post date:** [July 31, 2020, 9:11am UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632/429 "2020-07-31T09:11:13Z")
My DietPi Extension Manager stopped working. It is running on a RPi 4. I installed the official PoE HAT v2 to get rid of the power adapter. Upon rebooting I noticed that there was a new version available: > DietPi v6.28.0 : Update available > dietpi-update : Run now to update DietPi from v6.28.0 to v6.31.2. When I run the updater I get the follwing error: > [FAILED] DietPi-Set\_software | Checking URL: [https://raw.githubusercontent.com/MichaIng/DietPi/master/dietpi.txt](https://raw.githubusercontent.com/MichaIng/DietPi/master/dietpi.txt) > > - Command: wget --spider -t 1 -T 5 [https://raw.githubusercontent.com/MichaIng/DietPi/master/dietpi.txt](https://raw.githubusercontent.com/MichaIng/DietPi/master/dietpi.txt) > Spider mode enabled. Check if remote file exists. > –2020-07-31 11:03:23-- [https://raw.githubusercontent.com/MichaIng/DietPi/maste](https://raw.githubusercontent.com/MichaIng/DietPi/maste) r/dietpi.txt > Resolving [raw.githubusercontent.com](http://raw.githubusercontent.com) ([raw.githubusercontent.com](http://raw.githubusercontent.com))… failed: Connection timed out. > wget: unable to resolve host address ‘[raw.githubusercontent.com](http://raw.githubusercontent.com)’ Then I noticed that Roon does no longer discover any extensions. What do I need to do? Run a fresh install of DietPi and Extension Manager? **EDIT: a reboot fixed the discovery of the extensions in Roon. What about the v6.31.2 update?** ---
**Author:** ![Jan\_Koudijs](https://community.roonlabs.com/user_avatar/community.roonlabs.com/jan_koudijs/32/48346_2.png) [@Jan\_Koudijs](https://community.roonlabs.com/u/Jan_Koudijs)\ **Post date:** [August 1, 2020, 10:20am UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632/430 "2020-08-01T10:20:03Z")
> [@seagull](#): > > What about the v6.31.2 update? I haven’t had any issues after the update to v6.31.2, but it hasn’t been in very active use. ---
**Author:** ![seagull](https://community.roonlabs.com/user_avatar/community.roonlabs.com/seagull/32/48296_2.png) [@seagull](https://community.roonlabs.com/u/seagull)\ **Post date:** [August 1, 2020, 11:17am UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632/431 "2020-08-01T11:17:36Z")
Can this be caused by a firewall rule? I’m not managing the firewall myself and it is configured for a small business in a Windows environment. ---
**Author:** ![John\_Warden](https://community.roonlabs.com/letter_avatar/john_warden/32/5_5575768a8748004e209b776fc1b2916d.png) [@John\_Warden](https://community.roonlabs.com/u/John_Warden)\ **Post date:** [August 12, 2020, 8:35am UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632/432 "2020-08-12T08:35:17Z")
I’ve pulled the image for Roon Extension Manager and created a container in Docker For Windows, and the Docker Desktop reports it’s running, but Roon doesn’t see the extension. I’m exploring running REM using DFW on a small headless PC running Windows 10 Pro Version 2004 with WSL2. My objective is to be able to install, amongst other things, @Jan_Koudijs’ [CD Ripper](https://community.roonlabs.com/t/roon-extension-cd-ripper-v0-4-0/66590/142), which I tried unsuccessfully to install on my Synology Disk Station (which is where my Core runs). Here’s the log. Is the bit I’ve highlighted a problem? > [@](#): > > `{` > `'roon-extension-manager': '0.11.5',` > `'roon-extension-manager-updater': '0.4.0'` > `}` > `Docker for Linux found: Version 19.03.12` > `url: https://raw.githubusercontent.com/TheAppgineer/roon-extension-manager/master/.gitignore` > `2020-08-12T07:56:57.055Z - Inf: Installing: roon-extension-repository...` > `2020-08-12T07:56:57.134Z - Inf: Roon Extension Manager started!` > `url: https://raw.githubusercontent.com/TheAppgineer/roon-extension-repository/master/.gitignore` > **`.gitignore file not found`** > `2020-08-12T07:57:09.921Z - Inf: Installed: roon-extension-repository (0.3.15)` > `{}` > `2020-08-12T07:57:09.940Z - Inf: Extension Repository loaded` I can ping my network from the container command line, but I don’t know if DFW is giving the container an IP address that is outside my network, although I thought the **–network host** option would avoid that. (On the resources tab of DFW I haven’t changed the Network default of 192.168.65.0/28) The container inspection report from DFW looks like this: ![image](https://roon-community-uploads.s3.amazonaws.com/original/3X/f/a/fa9618988bb2da22ed5c618693ba403de181064f.png) Any pointers would be helpful. Please bear in mind I’m used to using Windows and GUI, so I’m pretty much a novice with CLI. Many thanks ---
**Author:** ![Jan\_Koudijs](https://community.roonlabs.com/user_avatar/community.roonlabs.com/jan_koudijs/32/48346_2.png) [@Jan\_Koudijs](https://community.roonlabs.com/u/Jan_Koudijs)\ **Post date:** [August 14, 2020, 5:31pm UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632/433 "2020-08-14T17:31:36Z")
> [@John\_Warden](#): > > I don’t know if DFW is giving the container an IP address that is outside my network Docker for Windows uses a VM to run Linux containers and also adds a virtual switch to the mix, meaning that extension discovery doesn’t work. In order to run the Docker based extensions Docker for Linux is required. What does work however is running a Linux VM and installing Docker for Linux in it. A light weight solution for this is running DietPi in the VM. You can find instructions for installation [here](https://github.com/TheAppgineer/roon-extension-manager/wiki/VM-Setup-Instructions). ---
**Author:** ![Adi\_Linden](https://community.roonlabs.com/user_avatar/community.roonlabs.com/adi_linden/32/111366_2.png) [@Adi\_Linden](https://community.roonlabs.com/u/Adi_Linden)\ **Post date:** [December 29, 2020, 7:03am UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632/434 "2020-12-29T07:03:58Z")
I installed roon-extensions-manager on DietPi v6.34.3 (on x86\_64 not actual rPi). All installed well and I can browse extension in the Roon app. However, when I try to install the alarm clock, this is what it responds with after a brief wait: ![Screen Shot 2020-12-29 at 1.01.09 AM](https://roon-community-uploads.s3.amazonaws.com/original/3X/8/f/8f40d520ab769f2fd36411dc28bcd4b61eecd17a.png) ---
**Author:** ![Jan\_Koudijs](https://community.roonlabs.com/user_avatar/community.roonlabs.com/jan_koudijs/32/48346_2.png) [@Jan\_Koudijs](https://community.roonlabs.com/u/Jan_Koudijs)\ **Post date:** [December 31, 2020, 12:29pm UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632/435 "2020-12-31T12:29:58Z")
Can you supply a log file so that I can investigate? I made a description on [how to get a log file](https://github.com/TheAppgineer/roon-extension-manager/wiki/Troubleshooting#collecting-log-files) on the Wiki. ---
**Author:** ![Adi\_Linden](https://community.roonlabs.com/user_avatar/community.roonlabs.com/adi_linden/32/111366_2.png) [@Adi\_Linden](https://community.roonlabs.com/u/Adi_Linden)\ **Post date:** [December 31, 2020, 10:59pm UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632/436 "2020-12-31T22:59:35Z")
This isn’t working well. Logging, this is how it looked by default already… ![Screen Shot 2020-12-31 at 4.54.25 PM](https://roon-community-uploads.s3.amazonaws.com/original/3X/c/2/c257205cb621359e5c1b5cebc108a409a0ae1429.png) I clicked install for the Alarm Clock extension… ![Screen Shot 2020-12-31 at 4.55.27 PM](https://roon-community-uploads.s3.amazonaws.com/original/3X/0/4/0424b735e747ecd304746ca27654640db600d3e2.png) Upon completion I clicked on the link… ![Screen Shot 2020-12-31 at 4.58.23 PM](https://roon-community-uploads.s3.amazonaws.com/original/3X/6/0/60324e438484e2d593bdae49fba2b0e11cafe4c9.png) It downloaded the extension-logs.tar.gz file, but it’s empty… ![Screen Shot 2020-12-31 at 4.56.36 PM](https://roon-community-uploads.s3.amazonaws.com/original/3X/4/6/463f323cfdfe16b1767a5799008f99897363d56c.png) ---
**Author:** ![Adi\_Linden](https://community.roonlabs.com/user_avatar/community.roonlabs.com/adi_linden/32/111366_2.png) [@Adi\_Linden](https://community.roonlabs.com/u/Adi_Linden)\ **Post date:** [December 31, 2020, 11:15pm UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632/437 "2020-12-31T23:15:17Z")
I poked around the .RoonExtensions directory. There is a .RoonExtensions/lib/node\_modules/roon-extension-alarm-clock directory present. After a restart of DietPi the Alarm Clock extension shows in the list. So just to see what happens I went to install the MQTT extension. Some thing happens, it says installing for a while, but then shows: ![Screen Shot 2020-12-31 at 5.08.20 PM](https://roon-community-uploads.s3.amazonaws.com/original/3X/2/7/27bee6a810b27b8f053452dff51a866f95036b15.png) I do see that .RoonExtensions/lib/node\_modules/roon-extension-mqtt is present now, but not showing in the list of extensions in the Roon app. When I look at Extensions Settings, it only provides the option to Install MQTT as I already did in the previous step. I reboot the DietPi and once alive again, the MQTT extension is present and I can proceed to start it. I uninstalled both Alarm Clock and MQTT Extension and both uninstalled just fine without errors. ---
**Author:** ![Jan\_Koudijs](https://community.roonlabs.com/user_avatar/community.roonlabs.com/jan_koudijs/32/48346_2.png) [@Jan\_Koudijs](https://community.roonlabs.com/u/Jan_Koudijs)\ **Post date:** [January 1, 2021, 6:08pm UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632/438 "2021-01-01T18:08:13Z")
As the error is reported by the Extension Manager, you have to restart that one with logging. So select it from the System category and perform the Restart with logging action, this is also what is shown in the screenshot on the Wiki page. ---
**Author:** ![Adi\_Linden](https://community.roonlabs.com/user_avatar/community.roonlabs.com/adi_linden/32/111366_2.png) [@Adi\_Linden](https://community.roonlabs.com/u/Adi_Linden)\ **Post date:** [January 1, 2021, 7:49pm UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632/439 "2021-01-01T19:49:34Z")
Got it! Here is the roon-extension-manager.log file ---
**Author:** ![Daniele\_Piancastelli](https://community.roonlabs.com/user_avatar/community.roonlabs.com/daniele_piancastelli/32/64319_2.png) [@Daniele\_Piancastelli](https://community.roonlabs.com/u/Daniele_Piancastelli)\ **Post date:** [January 2, 2021, 12:46pm UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632/440 "2021-01-02T12:46:04Z")
I have a problem. I had to re-install everything in my server (i took the opportunity to upgrade to ubuntu desktop 20.04.1) and now i can’t configure roon extension correctly Help!!! ``` roon-extension-manager.service - Roon Extension Manager Loaded: loaded (/etc/systemd/system/roon-extension-manager.service; enabled; vendor preset: enabled) Active: failed (Result: start-limit-hit) since Sat 2021-01-02 13:37:19 CET; 25s ago Process: 1375 ExecStart=/home/roon/.RoonExtensions/bin/roon-extension-manager.sh (code=exited, status=0/SUCCESS) Main PID: 1375 (code=exited, status=0/SUCCESS) gen 02 13:37:19 roon systemd[1]: roon-extension-manager.service: Scheduled restart job, restart counter is at 5. gen 02 13:37:19 roon systemd[1]: Stopped Roon Extension Manager. gen 02 13:37:19 roon systemd[1]: roon-extension-manager.service: Start request repeated too quickly. gen 02 13:37:19 roon systemd[1]: roon-extension-manager.service: Failed with result 'start-limit-hit'. gen 02 13:37:19 roon systemd[1]: Failed to start Roon Extension Manager. ``` ---
**Author:** ![Jan\_Koudijs](https://community.roonlabs.com/user_avatar/community.roonlabs.com/jan_koudijs/32/48346_2.png) [@Jan\_Koudijs](https://community.roonlabs.com/u/Jan_Koudijs)\ **Post date:** [January 2, 2021, 6:48pm UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632/441 "2021-01-02T18:48:06Z")
It turns out that the Extension Manager doesn’t work when npm version 7.x is used. You are probably running v7.3.0. Please confirm by running: ``` npm --version ``` @Daniele_Piancastelli, can you check the npm version as well? ---
**Author:** ![Daniele\_Piancastelli](https://community.roonlabs.com/user_avatar/community.roonlabs.com/daniele_piancastelli/32/64319_2.png) [@Daniele\_Piancastelli](https://community.roonlabs.com/u/Daniele_Piancastelli)\ **Post date:** [January 2, 2021, 7:26pm UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632/442 "2021-01-02T19:26:17Z")
My version is 6.14.4 ---
**Author:** ![Jan\_Koudijs](https://community.roonlabs.com/user_avatar/community.roonlabs.com/jan_koudijs/32/48346_2.png) [@Jan\_Koudijs](https://community.roonlabs.com/u/Jan_Koudijs)\ **Post date:** [January 2, 2021, 8:55pm UTC](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632/443 "2021-01-02T20:55:14Z")
Can you provide me the output of: ``` journalctl -u roon-extension-manager ``` [Previous page](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632.md?page=21) [Next page](https://community.roonlabs.com/t/roon-extension-manager-v0-11-9-obsolete/26632.md?page=23)