lrstanley/deluge-remove-after

daemon for removing torrents from deluge after a specified timeframe

👋, I'm @lrstanley, and this is my GitHub profile, where I frequently publish my open-source projects. I hope some of them can be beneficial to you or others. If you like any projects, please give some of them a ⭐, it would be much appreciated!

• 🌎 Originally from Michigan, US, I am currently located in North Carolina, US.
• 🚀 I am working on many projects, primarily revolving around tools to help improve the experience for other developers.
• 🔗 Take a look at my personal website, https://liam.sh.
• 📝 Browse some of the blog posts I have written here.
• 🙋‍♂️ Want to chat? Check out the Bytecord discord server, we talk programming, technology, 3d printers, games, etc.
• ❤️ Feeling generous? Sponsor me!
• 🗝️ Security concern with one of my repositories? Every repo has a SECURITY.md (example).

---

📌 A note on archived repositories

I have a lot of repositories that have been developed over the years, many of them are related to something I would be working on at the time, and I have transitioned to another tool or similar, or simply there wasn't enough desire from others to allow me to continue working on the projects/keeping it active. As such, I mark repositories as archived to make it obvious that there is a lack of attention being put in place on that project. This does not mean it's abandoned forever. If the need to maintain it resurges or I start working on the project again, I will unarchive it.

deluge-remove-after's Issues

Cannot authenticate to deluge

🌧 Describe the problem

I am trying to see if you have suggestions on how to debug this error, I see lots online about the deluge-console needing the right auth files, but since this is a container that is self-contained, im struggling to understand what to try

`deluge-remove-after-deluge-remove-after-1 | {"fields":{"arch":"amd64","commit":"latest","go_version":"go1.21.5","name":"deluge-remove-after","os":"linux","version":"master"},"level":"debug","timestamp":"2024-07-06T00:17:36.384874977Z","message":"logger initialized"}
deluge-remove-after-deluge-remove-after-1 | {"fields":{"error":"RPC error BadLoginError('Password does not match')\nTraceback: Traceback (most recent call last):\n File "/usr/lib/python3.12/site-packages/deluge/core/rpcserver.py", line 275, in dispatch\n ret = component.get('AuthManager').authorize(*args, **kwargs)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File "/usr/lib/python3.12/site-packages/deluge/core/authmanager.py", line 121, in authorize\n raise BadLoginError('Password does not match', username)\ndeluge.error.BadLoginError: Password does not match\n"},"level":"fatal","timestamp":"2024-07-06T00:17:36.435863022Z","message":"unable to connect to deluge daemon"}

`

⛅ Expected behavior

Unsure, never gotten it to wokr

🔄 Minimal reproduction

No response

💠 Version: deluge-remove-after

latest

🖥 Version: Operating system

linux/other

⚙ Additional context

No response

🤝 Requirements

• I believe the problem I'm facing is a bug, and is not intended behavior. Post here if you're not sure.
• I have confirmed that someone else has not submitted a similar bug report.