Jump to content

GeeMusic docker


Recommended Posts


I'm running Docker on my UnRaid server and would like to run a GeeMusic server on it so that I can access Google Play Music on my Amazon Echo. There are instructions here:




But I don't have the first clue where to start. I can get to the console on my server using PuTTY but don't know what to do next.


Would anyone be able to tell me how to create a docker for geemusic (or is anyone already working one something?)


Many thanks.

Link to comment

Hi Furtive,


Creating stuff to work with Alexa is not a simple matter. While it can be simple to install a Docker and have it run what is needed, it get complicated when you get to the Amazon side of things. You need certificates in order to connect to your server to/from Alexa. You need to create the skill in your own Amazon account. I have tried many times to get Sonos, and Kodi Alexa skills to work with very little success. I am not a pro, but also not a newb either.


I do hope for more unRAID community interest for Alexa fans. I would love Couchpotato, Sonarr, Raddar, Medusa, Sickrage, Kodi, etc. Alexa connect dockers. Something that perhaps integrates LetsEncrypt certificates...


So.... +1 from me.


This is part of the Amazon side of the skill setup:






Link to comment

It is there, but there is a big missing issue... creating the SSL certificate in your server/docker/reverse proxy, and tie it to the skill. You may know more about the subject than I do, but just from experience, it has never been as straight forward as the guides suggest.


Using the Heroku may be slightly easier, but then there is no docker needed as Heroku is hosting your skill. I believe it costs $$. You can also have Amazon Lambda host the code for you (free for a ton of requests per month). But I saw nothing on the git on how to do that.


He talks about ngrock, I have never tried or seen that. Perhaps that is the answer.


I'll take a look and see how easy it would be to create a template for their Docker, but after that, I am positive I will not know how to actually make it work w/ Amazon. I dont have Google Music either.





Link to comment

Try this xml... Create a file in /flash/config/plugins/dockerMan/templates-user/ and call it my-geemusic. Paste the below contents into the file and save. Then install it and fill out the info.


My docker was able to log into my google account. Beyond this, I cannot help.


<?xml version="1.0"?>
<Container version="2">
  <Overview>A bridge between Google Music and Amazon's Alexa

[b]Converted By Community Applications[/b]</Overview>
  <Description>A bridge between Google Music and Amazon's Alexa

[b]Converted By Community Applications[/b]</Description>



Link to comment

Many thanks. I've created the file, added my google username and an application password in the value fields, but when it runs I get this error:


10:08:29 web.1 | started with pid 10
10:08:31 web.1 | Traceback (most recent call last):
10:08:31 web.1 | File "server.py", line 1, in <module>
10:08:31 web.1 | from geemusic import app
10:08:31 web.1 | File "/geemusic/geemusic/__init__.py", line 13, in <module>
10:08:31 web.1 | api = GMusicWrapper.generate_api(logger=app.logger)
10:08:31 web.1 | File "/geemusic/geemusic/utils/music.py", line 256, in generate_api
10:08:31 web.1 | return cls(environ['GOOGLE_EMAIL'], environ['GOOGLE_PASSWORD'],
10:08:31 web.1 | File "/usr/lib/python3.6/os.py", line 669, in __getitem__
10:08:31 web.1 | raise KeyError(key) from None
10:08:31 web.1 | KeyError: 'GOOGLE_EMAIL'
10:08:31 web.1 | exited with code 1

Any ideas?

Link to comment

Not sure how to resolve your issue.


You could try to run this command from your unRAID CLI. Switch out the username/password with the correct ones.


docker run -d -e [email protected] -e GOOGLE_PASSWORD=[password] -e APP_URL=http://alexa-geemusic.stevegattuso.me -p 4000:4000 geemusic

Remeber that the APP-URL has to be a valid internet URL to your server from outside your network. If you do not have that, there is no chance this will work. Plenty of tutorials out there how to do this.

Link to comment

Thanks. I tried to run the command from the CLI but get this:


Unable to find image 'geemusic:latest' locally
Pulling repository docker.io/library/geemusic
docker: Error: image library/geemusic:latest not found.
See 'docker run --help'.

EDIT: Ran it with kuroshi/geemusic at the end and it's now running fine!


But I'm stuck again because the instructions for setting up the Amazon skill aren't working - I'm getting a JSON error. I give up.


Thanks for your help though.

Link to comment
  • 9 months later...
  • 11 months later...

This post was a long, long time ago... but I managed to get this working and I can try and answer some questions if anyone wants.  Can't tell you best practice or anything like that.  I've got the geemusic docker running, and the API it exposes (local only) is exposed to the internet by nginx as https://mydomainname.com/alexa - this then goes in the Alexa Dev Console with the certificate option as "My development endpoint is a sub-domain of a domain that has a wildcard certificate from a certificate authority".


The SSL / certificates part was all managed by the letsencrypt docker, which is pretty well documented online... it requests the certificate itself and applies it so geemusic doesn't need to know about SSL, it just exposes the API locally and nginx (in the letsencrypt docker) handles the encryption.  The letsencrypt docker is awesome and I would recommend it - it 8/10 easy to get everything working but 25/10 for the security I needed.  So the overall process for a request on my setup is:

  1. Alexa device sends request to Alexa servers (and a whole bunch of other stuff)
  2. Alexa things happen using the custom skill that I copy/pasted in there according to the instructions, then it calls the endpoint https://mydomainname.com/alexa
  3. nginx is exposing that endpoint to the internet (in my case nginx is in the letsencrypt docker)
  4. nginx passes that request to an endpoint on the geemusic docker, i.e. 'for the /alexa path on https://mydomainname.com, send the requests on to localhost:5000', which happens to be where the geemusic docker is exposing an endpoint
  5. geemusic docker gets the request and does geemusic stuff and returns a response back to Alexa (a URL for the track / whatever)
  6. Sweet sweet music
Link to comment


This topic is now archived and is closed to further replies.

  • Create New...