Yagami

Hi @dlandon I hope you doing well. I've updated the container, and now i can't see my players anymore (only a Pi with Volumio is visible) on the GUI I have plenty of DLNA/UPNP endpoints that are visible through control apps, but the server doesn't see them on the web interface. Any troubleshooting to fix it ? Thanks

Bumping this one for visibility

Hey @dlandon I finally got it to work, i followed the steps above (remove container, delete Appdata folder, re-install, launch, watch for Start, stop container, then restart). A note on the container's page on community apps might be helpful for new comers, as this is a bit strange. Thanks again for looking into it and fixing it.

Hi, I been playing around with the VM section for a little while now, and i feel confident enough to use a windows VM as my primary machine in the near future. I've passed an AMD Radeon RX580 GPU to the VM, and after facing the issue of 100% fan blowing (there are a couple of topics here and on reddit ), i found out that the solution is to install the correct drivers within the VM so software will take care of fan management. Which i did, however i'm not able to launch the Radeon software (screen is working, resolution is correct, Fan issue disappeared). Is there something i'm missing ? the Radeon pro software is visible when right clicking on the desktop but clicking it doesn't bring anything up; neither going to program files and launching the software (i also tried run as administrator). I'm not sure what logs or details to attach, so i will wait for the first responses to provide whatever details needed. Thanks

Thanks @dlandon for acknowledging the issue. I updated the container, launched it again, Gui not working, i stopped it and restarted it and still no luck. Do you want me to provide the logs ?

That's the same URL the "WebUi" button takes me to. Ive typed it manually, tried it with https, tried it with the server name, all of these don't load the page.

Thanks. My issue is that i'm not able to get to the GUI, i'm using all default values of the container, When i click on "WebUi" button on the container the page doesn't load. FYI i have a 20ish dockers working, and im pretty decent at managing basic stuff, i checked all allocations and no other docker uses the 9000 nor the 9090. If you can think of anything i should troubleshoot i would be thankful, otherwise i guess no chance to get this container to work. Thanks again for your time.

Yes indeed, when i click on WebUi it doesn't launch and browser says cannot reach website.

Here it is : docker run -d --name='LogitechMediaServer' --net='bridge' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Multiverse" -e HOST_CONTAINERNAME="LogitechMediaServer" -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:9000]/' -l net.unraid.docker.icon='https://github.com/dlandon/docker.templates/raw/master/logitechmediaserver.png' -p '9000:9000/tcp' -p '3483:3483/tcp' -p '3483:3483/udp' -p '9090:9090/tcp' -v '/mnt/user/classical music/':'/music':'rw' -v '/mnt/user/appdata/LogitechMediaServer':'/config':'rw' --log-opt max-size=50m --log-opt max-file=1 'dlandon/logitechmediaserver' 25a9f2bebff38fa026048b9e2019f0147358c9f492ed4992c422ba74e7e70910 The command finished successfully!

I did get it to work again, by going to the file config and change the token after re-authenticating plex and linking it to Trakt. It was pure intuition, but it's bad that the container never tells you what's wrong even in the logs. One more thing, each time you update the container, you have to redo the login on console, so i would suggest to leave it as is if you manage to make it work.

Hi @dlandon I have installed the docker image, and for whatever reason im not able to access the GUI nor find the server through a controller app. I checked if there were any conflicts with other docker allocations which i found (Twonky Server) : - I changed the ports for Twonky (LMS still doesn't load GUI) - I changed the ports on LMS ((LMS still doesn't load GUI)) - I completely removed Twonky, and checked all my allocation, no other docker uses 3483 nor 9000 nor 9090 (LMS still doesn't load GUI) - I used : Host / Bridge / Customer network : (LMS still doesn't load GUI) attached are logs after i started the container. Anything else i should be looking at to make it work ? Thanks Edit 1 : the docker forces a specific TZ which is different from where im based, could that create the issue ? LMS Logs.txt

Hey Steve, No one ever answered, i couldn't find info online neither... The funny thing is : the container still gets updates, but it's not working.

Unfortunately not, i never got help, nor found something online....

Hi, The container just stopped working, i did a re-install in both methods described in Github but nothing. When i start the container and i click on console it gives me the following error : "Error response from daemon: Container 943cde93235b54242f7acccc4276d7dbba31b408da2bcc3439e36d28d9afc048 is not running" These are the logs from the container itslef : nection error: (401) unauthorized; https://192-168-X-XXX.50da8a33f5144102804b184ce28118b2.plex.direct:32400/ <html><head><script>window.location = window.location.href.match(/(^.+\/)[^\/]*$/)[1] + 'web/index.html';</script><title>Unauthorized</title></head><body><h1>401 Unauthorized</h1></body></html>, local url http://172.18.X.X:32400 didn't respond either. Check PLEX_LOCALURL in .env file. I have tried to put both Plex and this docker in the same customer network on docker, both of them as host, one host and one on the custom network, but in vain. Any help would be appreciated.

Thanks Jorge, I ended-up restoring some data from it, and reformatting the drives, i chose Vdisc this time for the cache raid pool, hopefully restoring a Vdisc would be much easier in the future. Thanks