JPDVM2014

@ggfools It looks like soularr doesn't use PUID/PGID. It's been a while since I used soularr, so I'm not sure if it used to have those variables or it was just a mistake on my part. Either way, try deleting PUID and PGID, turn on advanced mode and add "--user 99:100" without the quotes into the "Extra Parameters" field. See if that helps.

Could you post a screenshot of your soularr template? Also, do you happen to have lidarr set to adjust permissions? It's in lidarr settings under Media Management advanced settings.

@Chandler Thanks for letting me know! It should be updated as soon as the CA refreshes.

Thanks for the info! I wonder what caused it. I've got a few hundred books and my /tmp folder is empty. Maybe it's used during conversion or something and it wasn't cleaning up properly. Hopefully a reinstall fixes it up.

Great, glad you got it working!

Looks like there is an open issue about running as a non-root user. https://github.com/therobbiedavis/Listenarr/issues/309 So, you'll either have to remove the "--user 99:100" or pre-create the config directory and set correct permissions. If you want to pre-create the config directory, run the below in your unraid terminal. If your appdata is located somewhere other than the default, make sure to change the command to match where it is. "mkdir /mnt/user/appdata/listenarr/ && chown -R 99:100 /mnt/user/appdata/listenarr/" I think for ease of use for new installs, I'm going to remove setting the user as part of the template. Anyone who wants/needs to change that should know how.

Yea, I'd try getting it at least to load to the WebUI before adding in the VPN. Then get the VPN sorted out before adding any indexers. Whenever you get a chance, if you want to post a screenshot of your template, I can see if anything stands out. I get that same npm error, but it doesn't seem to cause any issues. Only related error I see is that it can't write npm logs. My guess is it is because of the container running as "--user 99:100". You could turn on advanced view and remove that from the Extra Parameters section to see if it helps anything. If you do remove that, I'd delete your listenarr appdata folder to make sure you are restarting from scratch. FWIW, I am running with "--user 99:100", and everything seems to be running fine.

No problem! Let me know if you run into any issues with it. I've got it up and running on my system with the changes.

My template changes don't actually update the container, so it wouldn't be caught by the auto-update plugin. You'll have to install it again from the CA store.

Good idea. I just committed the changes. Will be in the CA store next time it updates.

Thanks, I'll update it!

Yea, looks like it is gone. That's a shame, it was more reliable for me than CWABD. Guess I'll go back too and give it a try again.

You can run "docker run --network=host --rm -it cooldockerizer93/spotizerr-auth" to get the auth tool.

Did you run this in your terminal before starting? You need to adjust this command to wherever your appdata folder is, if it is different. And change the 99:100 part to match whatever you are running spotizerr as. If you left the template default, then this command should work as-is. "mkdir -p /mnt/user/appdata/spotizerr-phoenix && touch /mnt/user/appdata/spotizerr-phoenix/.cache && chown -R 99:100 /mnt/user/appdata/spotizerr-phoenix" You might have to delete a .cache directory if it exists. If you run the container without creating the .config file, it usually creates it as a directory instead.

You don't actually need those variables set to run the container. You can set them in the WebUI. The log confused me the first time too. There is no indication that it has finished starting up, but if you go to the WebUI, it should be there.

@snoopy86 Just an FYI, your Lyrion template has an incorrect tag for the ghcr.io image. It should be ghcr.io/lms-community/lyrionmusicserver:rc instead of :latest.

Ugh, I was hoping there would be a PUID/PGID option instead. I'll update the template. Thanks!

Got it. I'll add that into the description. Thanks!

Only thing I can think of is maybe a permission issue. If you are comfortable in the command line, navigate to your spotizerr appdata folder and run "ls -la". Everything should show as "nobody users". For the debugging, it might be worth asking at the creator's code repo. I can't add anything unfortunately since I don't have the skill. I just created the template. https://lavaforge.org/spotizerrphoenix/spotizerr-phoenix

Hmm, I'm not sure then. Is there anything in your logs at all? Maybe there is something in the logs during startup that can help?

For your REDIS_HOST, try removing the "redis://" and just leaving the IP address.

Could you post a screenshot of your template? Also, did you go through all the steps to add your Spotify account using the other docker container and Spotify connect?

Yea, I ran into that problem too. It should have popped up as an instruction when installing, but glad you figured it out.

I changed the spotizerr template to work with this fork instead. Should be in the Community App store in a couple hours.

You have to make a config directory in your appdata folder. Then make a main.json that has { "version": "3.3.0" } That seems to get me up and running. Source: https://lavaforge.org/spotizerr/spotizerr/issues/2