Can someone help me out, I am trying to setup MyMedia in the docker. I have port forwarded the two ports needed but cannot connect. Logs are below. Thanks in advance.

MyMediaForAlexa.log2024-26-22-052641.zip

On 1/22/2024 at 11:43 AM, ACiDiAC said:

Can someone help me out, I am trying to setup MyMedia in the docker. I have port forwarded the two ports needed but cannot connect. Logs are below. Thanks in advance.

MyMediaForAlexa.log2024-26-22-052641.zip 38.48 kB · 1 download

 

Not quite sure what you are saying is not connecting?

 

Some questions:

• Have you successfully installed the MyMedia for Alexa skill into Alexa?
• Can you get the MyMediaForAlexa docker GUI pages up? 
• Have you used the GUI pages to connect the docker to your Amazon account?
• Have you paid for a licence?
• Is the docker correctly configured to point to where your audio files are stored?
• Does the docker container GUI say it has successfully indexed files?
•  

5 hours ago, itimpi said:

 

Not quite sure what you are saying is not connecting?

 

Some questions:

• Have you successfully installed the MyMedia for Alexa skill into Alexa?
• Can you get the MyMediaForAlexa docker GUI pages up? 
• Have you used the GUI pages to connect the docker to your Amazon account?
• Have you paid for a licence?
• Is the docker correctly configured to point to where your audio files are stored?
• Does the docker container GUI say it has successfully indexed files?
•  

Yes on the Alexa skill

yes the GUI pages come up

It is linked to my Amazon account

I have paid for a license

Yes it is pointing to my audio files

No I cannot get it to index anything since it says not connected in the upper left hand corner of the dashboard.

5 minutes ago, ACiDiAC said:

No I cannot get it to index anything since it says not connected in the upper left hand corner of the dashboard.

This should mean that you have not successfully linked the docker container to your Amazon account, but your earlier answer indicates you have connected so there is some contradiction.

For those having issues with the upper left "not connected' problem, it is probably the settings for media path when you set up the app.   I have been playing around with it and the connection only works with the attached screenshot.  My problem is how do you get it off queued after you set up a watch folder 

I had to wait an hour for the scan to start.  I kept trying rescan but it did not help.

8 hours ago, jkwaterman said:

For those having issues with the upper left "not connected' problem, it is probably the settings for media path when you set up the app.   I have been playing around with it and the connection only works with the attached screenshot.  My problem is how do you get it off queued after you set up a watch folder 

 

Mapping the media path to /mnt/user seems more than is needed in most cases as it allows the whole of your Unraid system to be scanned for audio files which is likely to take longer than a more targeted scan and spin up all array disks while doing so.   I personally run two instances of this docker container - one with it mapped to /mnt/user/Music and the other mapped to /mnt/user/AudioBooks so that each instance only scans the subset of media that I want it to handle. This also only ever spins up the one array disk that contains both these shares.

I had the same problem with the "red" not connected.  There were also no servers listed under the servers section. After messing around with different setting for a bit, I finally started over.  This will cause you to lose any custom configuration in MyMediaForAlexa such as playlists, etc.

 

Delete the docker by clicking on the MyMediaForAlexa icon under DOCKER and chose remove.

Delete the MyMediaForAlexa folder by going to SHARES  >> appdata select the folder and select DELETE.

Disassociate the MyMediaForAlexa skill from your Amazon account from the Alexa app on your phone

 

Go to APPS and reinstall MyMediaForAlexa.  I accepted the defaults and added the path to my music files.

After the docker starts, go to a browser and http://IPADDRESS:52051

Log into the Amazon account you want to associate with MyMediaForAlexa using a web browser (this help the next step go smoothly) 

The initial screen should prompt you to associate to your Amazon account which you just logged into previously.

This was the key step for me and then it shows a green "connected" and the servers section was populated again.

Add the MyMediaForAlexa skill back to your Amazon account from the Alexa app on your phone

 

A few other things I learned while testing:

Specifying Network Type Custom:br0 and giving it a different IP Address on your subnet also works.

The appdata share can be configured as Export "No" and Security "Private" and still work.

 

I recently noticed errors playing back music. The error messages in the logs said:

MEDIA_ERROR_SERVICE_UNAVAILABLE. If this happens on every track, please check your computer firewall settings or review our FAQ.

 

In the FAQ under the question "When I ask Alexa to play music from My Media, there is just silence," There is a phrase that says,

"To test that network access is ok, try to access the following URL from a web browser on another computer/mobile/phone on your network: " 

I noticed that the IP address listed in the test URL was incorrect. Since the last time I had used mymediaforalexa I had changed the subnet my Unraid server was using and the old subnet was still showing up. This old IP was despite the fact in the docker configuration I had the correct IP address.

 

I solved the problem by stopping the docker container and then editing the file

/mnt/user/appdata/MyMediaForAlexa/Preferences.xml.
Within the XML tag <UseIP4Address>OLD IP</UseIP4Address> was the old IP address I had previously assigned to MyMediaForAlexa. I edited that file, as well as Preferences.xml.bak which I don't if was necessary but I did it anyway, to the correct IP address.

Then I restarted the docker container and my connectivity problems went away.

 

I was using a custom IP address on a bridged network, if that makes a difference to anyone else.

Edited March 8, 20251 yr by Karl Kowallis

Is this still working for anyone else?

I'm a licensed user for MyMedia for Alexa and have setup the container to point to my audiobooks. Signed in with my Amazon account and enabled the MyMedia for Alexa skill.
The Windows app works fine but the Unraid docker just says "Not Connected" in the top left hand side. I've totally removed the docker and all settings from appdata related and setup from scratch and still have the same issue. Just wondering if anyone else still uses this via Unraid and has it working?

It still works for me.

I have 2 docker instances set up - one for music and one for audiobooks.

I do think it is a shame that they never improved the audiobook support as I find too many quirks to use it regularly. The music side is better although it could also be improved.

Not quite sure what that error message means, but I think it may be something to do with connecting to your Amazon account.