Trevor is spot on. If you edit the ID3 tags, the actual file data changes, which immediately breaks the torrent hash and causes Deluge to throw an error and stop seeding. The best workflow is just to copy the downloaded MP3s over to your permanent music folder and edit them there, leaving the origin...

I ran into something similar once, and the first thing I'd check is whether the daemon is actually running and if there are any errors in the logs. If this started after an update, it can also help to test with a fresh config or temporarily disable any plugins to rule out a bad setting. That usually...

The Firefox protocol association for magnet links on macOS trips up a lot of people when they first switch clients. Dropping the exact menu path like that is super helpful for anyone else searching the forum with the same issue.

I'd also recommend checking the client logs if anyone else runs into the same issue - they often point to the root cause much faster than trial and error. It's always helpful when people come back and share what ended up fixing it.

One thing that's worth checking is whether the issue is caused by an old config or cache rather than Deluge itself. Backing up your settings, starting with a fresh config, and then reapplying only the necessary changes has fixed a few odd problems for me in the past. It's a quick thing to rule out b...

I've run into similar issues before, and clearing the session or config cache before restarting Deluge has sometimes done the trick. If that doesn't help, creating a fresh profile can also be a quick way to tell if it's a configuration problem rather than a bug.

If the port only fails intermittently, it might be worth checking whether your ISP is changing your public IP or if UPnP/NAT-PMP is fighting with your manual port forwarding rules. I've seen random connectivity issues disappear after disabling one method and sticking with a single port-forwarding se...