Your qbit is firewalled (see the orange flame), you want a vpn that can do port forwarding. Public trackers also lie about seed counts so you can try raising the minimum seed counts in the arrs for that trackers, in this case it looks like there are zero seeders. Public torrents also generally will have many of the trackers fail to connect like in your screenshot, not necessarily bad as long as you address the other two issues.

Check if you have a misconfigured firewall, but that torrent looks like it may just be dead

You can see in the screenshot that you're failing to connect to the trackers.

Try their URLs with curl or in a browser.

If you put qbt behind a VPN, then that's probably the issue.

If your downloads are getting stuck then no, it's not set up properly. Double check your filters and custom format rules. Also, you can use Cleanuparr to automatically remove stalled downloads and trigger a new search.

I don't know how YAMS is set up, but I keep my arr stack and my torrent docker setup completely separate, on separate computers. I use the qbittorrent PIA docker image (since my VPN is PIA) on a separate, dedicated mini PC so it only has Internet if it's connected to the VPN. I just use a static IP for both PCs on my internal network and point the arr stack at the torrent client to handle everything.

Not sure if separating them is the right solution for you, but if all else fails, it might be with a try. I prefer it that way so I can literally just unplug or turn off the torrent box if I need to without disrupting my actual media server.

First thought is VPN port issue. I recall changing from Mullvad to ProtonVPN because Mullvad wasn't' doing the port forwarding correctly... or so says the robot.

Could be a VPN issue. I've had issues like this that I've fixed by changing my exit server. But I'm unsure what the root cause was in those cases.

There are no available seeders on that torrent. Pick a different one.

Downvoted because of the tab with an LLM.