I was just starting to fiddle with the Starr programs so i didn’t realize that the proper way to use it is to sync the torrent clients directly to sonarr and radarr. The issue happened on those programs all the same though. (fixed it already though)
I was just starting to fiddle with the Starr programs so i didn’t realize that the proper way to use it is to sync the torrent clients directly to sonarr and radarr. The issue happened on those programs all the same though. (fixed it already though)
I got it to run, its fairly simple but i am having issues integrating it into the docker compose as it just… stops working… i’ll be looking into it today and tomorrow and if i succeed i’ll report back to you with findings.
yeah, that and other stuff its very hacky. I’ve now done a .env file to keep everything parametrized.
Thats good!! i’m now looking at how to set up caddy to do exactly just just that, then i’ll look at the vpns for outside connections. Thanks gor the advice!
I think you are right! Now that you’ve explained it, it makes sense in my head, as someone else recommended i added hostnames and now i can work with those which makes it nicer, i don´t want to be opening a maze of ports xd
Bingo! This worked. I don’t fully understand why because i expose the ports on the docker containers, i guess i must have something miss-configured. Thanks!!
Version information:
qBit: v4.5.4
prowlarr: 1.7.4.3769
i tried with 127.0.0.1:4666 but i got the same issue
With what money are they supposed to fight the multi billion dollar mega corpo exactly with dozens of lawyers??
Also, if they fight this in court then that would mean less money for development thus making your experience even worse….