YAMS Forum

It works! I did have to do one thing differently: I already had a network "yams_default" declared (I wonder where?) with the subnet 172.18.0.0/16. So, the network declaration in the compose file caused a conflict and I removed it. Also, I chose to start with higher IP's to avoid address co...

Okay, so, some very unexpected things happen. First, I realized that the internal docker IP's assigned are not static???? They change each time I make these changes to the .yaml and restart. Second, each time I restart yams, SOME services don't even get an internal IP! Last time, it was prowlarr, bu...

Oh, wait, now Prowlarr can't see ANY other apps. The hostnames aren't resolving: "Unable to complete application test, cannot connect to Radarr. Name does not resolve (radarr:7878)" Here's my prowlarr config: prowlarr: image: lscr.io/linuxserver/prowlarr container_name: prowlarr environmen...

I can install Flaresolverr and access its JSON page, but for some reason I can't make it visible to Prowlarr (which is going through my VPN via Gluetun). Here's the Flaresolverr section in my docker-compose.custom.yaml: flaresolverr: image: ghcr.io/flaresolverr/flaresolverr:latest container_name: fl...

I suspect my problem stems from a mistake during setup: I set the download location for qBittorrent incorrectly, so Radarr and Sonarr were both failing to import media. I think the error was "path not accessible by Radarr" or something similar. I fixed that in qBittorrent manually; it's no...