# Musicbox extention not visible in web gui

**URL:** <https://discourse.mopidy.com/t/musicbox-extention-not-visible-in-web-gui/3747>\
**Category:** Misc\
**Created:** [February 1, 2020, 9:02am UTC](https://discourse.mopidy.com/t/musicbox-extention-not-visible-in-web-gui/3747 "2020-02-01T09:02:02Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![maphouse](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/maphouse/32/1424_2.png) [@maphouse](https://discourse.mopidy.com/u/maphouse)\
**Post date:** [February 1, 2020, 9:02am UTC](https://discourse.mopidy.com/t/musicbox-extention-not-visible-in-web-gui/3747/1 "2020-02-01T09:02:02Z")

</div>

Hello!

## The webgui extension is visible nowhere within the default mopidy gui or by going to the _musicbox\_webclient/_ url extention directly.

CONTEXT:

**I have just installed the musicbox on ubuntu 19.10 Server (on a raspberry pi 4 device)…**  
_sudo python3 -m pip install Mopidy-MusicBox-Webclient_

**I have made sure that the following…**  
_[musicbox\_webclient]_  
_enabled = true_  
_musicbox = false_  
_websocket\_host =_  
_websocket\_port =_  
_on\_track\_click = PLAY\_ALL_

**… is in the conf files**  
the one under _~/.config/mopidy_  
and the one under _/etc/mopidy_

**I can successfully run _mopidy_ and view it on any device in my local network**  
_/usr/lib/python2.7/dist-packages/mopidy/ext.py:202: PkgResourcesDeprecationWarning: Parameters to load are deprecated. Call .resolve and .require separately._  
_extension\_class = entry\_point.load(require=False)_  
_INFO Starting Mopidy 2.2.3_  
_INFO Loading config from builtin defaults_  
_INFO Loading config from /home/ubuntu/.config/mopidy/mopidy.conf_  
_INFO Loading config from command line options_  
_INFO Enabled extensions: mpd, http, stream, m3u, softwaremixer, file, local, soundcloud_  
_INFO Disabled extensions: none_  
_INFO Starting Mopidy mixer: SoftwareMixer_  
_INFO Starting Mopidy audio_  
_INFO Starting Mopidy backends: StreamBackend, M3UBackend, FileBackend, LocalBackend, SoundCloudBackend_  
_INFO Audio output set to “autoaudiosink”_  
_INFO Loaded 5865 local tracks using json_  
_INFO Logged in to SoundCloud as “Emo No Rio”_  
_INFO Starting Mopidy core_  
_INFO Starting Mopidy frontends: MpdFrontend, HttpFrontend_  
_INFO MPD server running at [::]:6600_  
_INFO HTTP server running at [::]:6680_  
_INFO Starting GLib mainloop_

**However, the webgui extension is visible nowhere within the default mopidy gui or by going to the _musicbox\_webclient/_ url extention directly (as seen below).**

 ![Capture](https://canada1.discourse-cdn.com/flex036/uploads/mopidy/original/2X/3/3c4e1a0fa90339aa63d02eba3ab9c5aa94941a42.jpeg)

Any advice on making this music player work would be very much appreciated. Thank you!

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [February 1, 2020, 9:32am UTC](https://discourse.mopidy.com/t/musicbox-extention-not-visible-in-web-gui/3747/2 "2020-02-01T09:32:57Z")

</div>

Install the latest 3.x version of Mopidy from [apt.mopidy.com](http://apt.mopidy.com) by following the instructions in our document at [https://docs.mopidy.com/en/latest/installation/debian/](https://docs.mopidy.com/en/latest/installation/debian/). That version is a Python 3 compatible release and will work with the Python 3 version of Mopidy-Musicbox-webclient you have installed.

You are currently running Mopidy v2.2.3, that’s an old Python 2 version, perhaps installed from the Ubuntu software repositories? That version only works with Python 2 versions of extensions. None of the Python 2 versions will see any updates. You probably don’t want that.

---

<div class="post-metadata">

**Author:** ![maphouse](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/maphouse/32/1424_2.png) [@maphouse](https://discourse.mopidy.com/u/maphouse)\
**Post date:** [February 1, 2020, 6:29pm UTC](https://discourse.mopidy.com/t/musicbox-extention-not-visible-in-web-gui/3747/3 "2020-02-01T18:29:35Z")

</div>

This is great. I will try this today and confirm. Thanks!

---

<div class="post-metadata">

**Author:** ![maphouse](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/maphouse/32/1424_2.png) [@maphouse](https://discourse.mopidy.com/u/maphouse)\
**Post date:** [March 30, 2020, 3:41am UTC](https://discourse.mopidy.com/t/musicbox-extention-not-visible-in-web-gui/3747/4 "2020-03-30T03:41:14Z")

</div>

Hello!

I have gotten around to installing a mopidy once again with a fresh ubuntu 18.04.4 on raspberry pi 4 following the exact instructions indicated, as you listed above.

I then installed musicbox and soundcloud as indicated in their respective pages.

Any mopidy command, however, brings up the following:  
_ERROR: Mopidy requires Python 2.7, but found 3.6.9._

I have tried what was indicated in these pages, but to no avail

> [@Mopidy Setup Issues - Python version requirement](https://discourse.mopidy.com/t/mopidy-setup-issues-python-version-requirement/2131):
>
> I read through this older post - [Python error when starting Mopidy on Raspberry Pi](https://discourse.mopidy.com/t/python-error-when-starting-mopidy-on-raspberry-pi/869) It refers to ensuring that one use the correct version of pip (one that uses Python 2.7). I’m not sure this is relevant based on the current state of Mopidy in that the installation process does not use pip currently. I flashed a new environment on my RPi3B for my AIY Voice Kit. It is running Linux raspberrypi 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux I went through the Mopidy installat…

> <https://github.com/mopidy/mopidy/issues/1294>
>
> \`mopidy local scan\` gives me \`ERROR: Mopidy requires Python 2.7, but found 3.4.3….\`, but I have both Python 2.7 and 3.4.3 installed.
> 
> Is there a way to make it use the output from \`which python2.7\` instead?

Any idea at all what can be done here? Any advice would be much appreciated. Thanks!

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [March 30, 2020, 7:56am UTC](https://discourse.mopidy.com/t/musicbox-extention-not-visible-in-web-gui/3747/5 "2020-03-30T07:56:58Z")

</div>

Ubuntu 18.04 is too old. From our install docs:

> The packages in the [apt.mopidy.com](http://apt.mopidy.com) archive are built for:
> 
> - **Debian 10 (Buster)** , which also works for Raspbian Buster and Ubuntu 19.10 and newer.

---

<div class="post-metadata">

**Author:** ![maphouse](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/maphouse/32/1424_2.png) [@maphouse](https://discourse.mopidy.com/u/maphouse)\
**Post date:** [March 30, 2020, 4:22pm UTC](https://discourse.mopidy.com/t/musicbox-extention-not-visible-in-web-gui/3747/6 "2020-03-30T16:22:15Z")

</div>

Oops, thanks for pointing this out!

---

<div class="post-metadata">

**Author:** ![maphouse](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/maphouse/32/1424_2.png) [@maphouse](https://discourse.mopidy.com/u/maphouse)\
**Post date:** [April 4, 2020, 7:33am UTC](https://discourse.mopidy.com/t/musicbox-extention-not-visible-in-web-gui/3747/7 "2020-04-04T07:33:25Z")

</div>

I am back at ground zero (ubuntu 19.10)  
However, following the standard instructions outlined [here](https://docs.mopidy.com/en/latest/installation/debian/) installs v2.3.2 by default. I haven’t found a way to install 3.0.2…

Might it have to do with what version of python is being detected? I have 2 and 3 installed:

```
ubuntu@ubuntu:~/.config/mopidy$ ls -la /usr/bin/python
lrwxrwxrwx 1 root root 7 Oct 10 11:32 /usr/bin/python -> python2

ls -la /usr/bin/python2
lrwxrwxrwx 1 root root 9 Oct 10 11:32 /usr/bin/python2 -> python2.7

ls -la /usr/bin/python3
lrwxrwxrwx 1 root root 9 Oct 2 2019 /usr/bin/python3 -> python3.7
```

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [April 4, 2020, 8:37am UTC](https://discourse.mopidy.com/t/musicbox-extention-not-visible-in-web-gui/3747/8 "2020-04-04T08:37:02Z")

</div>

Nope, python 2 and 3 installed is normal, it’s fine. The instructions are definitely correct. You need to make sure you are using [apt.mopidy.com](http://apt.mopidy.com). Installing that old versions is exactly what happens if you do not use [apt.mopidy.com](http://apt.mopidy.com)

---

<div class="post-metadata">

**Author:** ![maphouse](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/maphouse/32/1424_2.png) [@maphouse](https://discourse.mopidy.com/u/maphouse)\
**Post date:** [April 5, 2020, 2:58am UTC](https://discourse.mopidy.com/t/musicbox-extention-not-visible-in-web-gui/3747/9 "2020-04-05T02:58:47Z")

</div>

> [@kingosticks](#):
>
> [apt.mopidy.com](http://apt.mopidy.com)

Hi there and thanks for the quick response(s).  
Excuse me if I am missing something completely obvious here, but I am still unable to figure this out. Please excuse my computational noobness

This is what I’m doing, as instructed in the instructions you cited:

```
ubuntu@ubuntu:~$ wget -q -O - https://apt.mopidy.com/mopidy.gpg | sudo apt-key add -
OK
ubuntu@ubuntu:~$ sudo wget -q -O /etc/apt/sources.list.d/mopidy.list https://apt.mopidy.com/buster.list
ubuntu@ubuntu:~$ sudo apt update
Hit:1 https://apt.mopidy.com buster InRelease
Hit:2 http://ports.ubuntu.com/ubuntu-ports eoan InRelease
Hit:3 http://ports.ubuntu.com/ubuntu-ports eoan-updates InRelease
Hit:4 http://ports.ubuntu.com/ubuntu-ports eoan-backports InRelease
Hit:5 http://ports.ubuntu.com/ubuntu-ports eoan-security InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'https://apt.mopidy.com buster InRelease' doesn't support architecture 'arm64'
N: Skipping acquire of configured file 'contrib/binary-arm64/Packages' as repository 'https://apt.mopidy.com buster InRelease' doesn't support architecture 'arm64'
N: Skipping acquire of configured file 'non-free/binary-arm64/Packages' as repository 'https://apt.mopidy.com buster InRelease' doesn't support architecture 'arm64'

```

There seems to be something going wrong here : `'https://apt.mopidy.com buster InRelease' doesn't support architecture 'arm64'`

Does this have to do with this being a raspberry pi? Anyway, it’s clearly impacting the install i.e. the version that gets installed is still 2.3.2…

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [April 5, 2020, 9:10am UTC](https://discourse.mopidy.com/t/musicbox-extention-not-visible-in-web-gui/3747/10 "2020-04-05T09:10:25Z")

</div>

Ohhh. I am sorry. I lost the details of what you were doing along the way and forgot this was all on a raspberry pi. Even though you said it in a couple of your posts. We don’t provide 64bit arm binaries it seems. Not sure what it would take for us to do that.

You’ll have to go down the installing from source route in the docs, and that should work! Again, apologies for missing that.

---

<div class="post-metadata">

**Author:** ![maphouse](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/maphouse/32/1424_2.png) [@maphouse](https://discourse.mopidy.com/u/maphouse)\
**Post date:** [April 5, 2020, 7:11pm UTC](https://discourse.mopidy.com/t/musicbox-extention-not-visible-in-web-gui/3747/11 "2020-04-05T19:11:52Z")

</div>

Thanks,  
I had already tried this, but just gave it another shot:

I appear to be having the same issue as was brought up here:

> [@Incorrect binary install location](https://discourse.mopidy.com/t/incorrect-binary-install-location/3312):
>
> When I install Mopidy from the deb install, I get this error: bash: /usr/local/bin/mopidy: No such file or directory I can find the binary in /usr/bin though. Any fixes for this?

the `mopidy` command isn’t being found.

```
ubuntu@ubuntu:/bin$ mopidy
-bash: /usr/bin/mopidy: No such file or directory

```

Is there something I should be doing to make this work after install here?

---

<div class="post-metadata">

**Author:** ![maphouse](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/maphouse/32/1424_2.png) [@maphouse](https://discourse.mopidy.com/u/maphouse)\
**Post date:** [April 5, 2020, 8:43pm UTC](https://discourse.mopidy.com/t/musicbox-extention-not-visible-in-web-gui/3747/12 "2020-04-05T20:43:51Z")

</div>

Ok nevermind, running mopidy as `python3 mopidy`

The correct version is finally installed and running!