[HELP] What should be in ignored.txt #135

New Issue

giteasync · 2025-10-09T16:59:20-05:00

giteasync commented

2025-10-09 16:59:20 -05:00

Originally created by @Neobond on GitHub.

Before submitting a help request, I have:

Reviewed the documentation.
Ensured I am using ghcr.io/flmorg/cleanuperr docker repository.
Ensured I am using the latest version.
Enabled debug logging.

How can we help?

Sorry for being completely thick.

I have setup my docker-compose with an additional folder in /docker/cleanupeer/files/blacklist.txt and linked the path in Sonarr and Radarr to files/blacklist.txt

But when building the project I get

Now, I know I can just create an empty ignored.txt file, but what is supposed to be in it?

I could not find guidance on this one file in the Setup instructions.

Cheers in advance!

Originally created by @Neobond on GitHub. ### Before submitting a help request, I have: - [x] Reviewed the documentation. - [x] Ensured I am using ghcr.io/flmorg/cleanuperr docker repository. - [x] Ensured I am using the latest version. - [x] Enabled debug logging. ### How can we help? Sorry for being completely thick. I have setup my docker-compose with an additional folder in /docker/cleanupeer/files/blacklist.txt and linked the path in Sonarr and Radarr to files/blacklist.txt But when building the project I get ![Image](https://github.com/user-attachments/assets/8d6937b8-7f4d-491b-bde4-15d8d59fe457) Now, I know I can just create an empty ignored.txt file, but what is supposed to be in it? I could not find guidance on this one file in the Setup instructions. Cheers in advance!

giteasync added the question label 2025-10-09 16:59:20 -05:00

giteasync closed this issue

2025-10-09 16:59:21 -05:00

giteasync commented

2025-10-09 16:59:22 -05:00

@Neobond commented on GitHub:

Thanks! I thought using blacklist.txt would be enough.

@Neobond commented on GitHub: Thanks! I thought using blacklist.txt would be enough.

giteasync commented

2025-10-09 16:59:22 -05:00

@Neobond commented on GitHub:

Yes, thanks! I had a bunch of failures with .lnk files so I hope this solves it :D

@Neobond commented on GitHub: Yes, thanks! I had a bunch of failures with .lnk files so I hope this solves it :D

giteasync commented

2025-10-09 16:59:22 -05:00

@Flaminel commented on GitHub:

No worries!

@Flaminel commented on GitHub: No worries!

giteasync commented

2025-10-09 16:59:22 -05:00

@Flaminel commented on GitHub:

The Docker compose from the docs is just an example that includes all settings and should be customized depending on your needs.

The ignored.txt file is used for QUEUECLEANER__IGNORED_DOWNLOADS_PATH, CONTENTBLOCKER__IGNORED_DOWNLOADS_PATH and DOWNLOADCLEANER__IGNORED_DOWNLOADS_PATH variables that are documented here.

If you don't want to ignore certain downloads from processing, you can either unset those variables and remove the volume or just create an empty file to mount.

@Flaminel commented on GitHub: The Docker compose from the docs is just an example that includes all settings and should be customized depending on your needs. The `ignored.txt` file is used for `QUEUECLEANER__IGNORED_DOWNLOADS_PATH`, `CONTENTBLOCKER__IGNORED_DOWNLOADS_PATH` and `DOWNLOADCLEANER__IGNORED_DOWNLOADS_PATH` variables that are documented [here](https://github.com/flmorg/cleanuperr/blob/main/variables.md). If you don't want to ignore certain downloads from processing, you can either unset those variables and remove the volume or just create an empty file to mount.

giteasync commented

2025-10-09 16:59:23 -05:00

@Flaminel commented on GitHub:

Did you succeed in setting it up?

@Flaminel commented on GitHub: Did you succeed in setting it up?

giteasync commented

2025-10-09 16:59:24 -05:00

@Flaminel commented on GitHub:

Bridge is what I was referring to. If they are in a bridged network, then you still can't access a container from another container with localhost. You can access them through their service name or their Docker IP.

Unless maybe your setup is somehow different? Do you access qBittorrent with localhost from the arrs?

@Flaminel commented on GitHub: Bridge is what I was referring to. If they are in a bridged network, then you still can't access a container from another container with `localhost`. You can access them through their service name or their Docker IP. Unless maybe your setup is somehow different? Do you access qBittorrent with `localhost` from the arrs?

giteasync commented

2025-10-09 16:59:24 -05:00

@Neobond commented on GitHub:

Hi, thanks for your patience with me!

In my arrs compose, they are set to synobridge. I am not smart enough to know what that actually means (internal docker network?), but host mode is not mentioned in that compose file.

@Neobond commented on GitHub: Hi, thanks for your patience with me! In my arrs compose, they are set to `synobridge`. I am not smart enough to know what that actually means (internal docker network?), but host mode is not mentioned in that compose file.

giteasync commented

2025-10-09 16:59:24 -05:00

@Neobond commented on GitHub:

Quick follow up. I checked the log of cleanuperr and there were a bunch of messages about http://localhost:7878 and http://localhost:8989 "instance not found" I changed it to the IP address, and the log now seems to show the appropriate access!

Edit: thinking about it, I suppose I could put cleanuperr in the same docker compose as the arrs and qBittorrent, and then http://localhost would work, am I correct in thinking this?

@Neobond commented on GitHub: Quick follow up. I checked the log of cleanuperr and there were a bunch of messages about http://localhost:7878 and http://localhost:8989 "instance not found" I changed it to the IP address, and the log now seems to show the appropriate access! ![Image](https://github.com/user-attachments/assets/6828b5d2-c2cd-487d-9244-3d64f15f8afd) Edit: thinking about it, I suppose I could put cleanuperr in the same docker compose as the arrs and qBittorrent, and then http://localhost would work, am I correct in thinking this?

giteasync commented

2025-10-09 16:59:24 -05:00

@Neobond commented on GitHub:

Ah yeah, I put the LAN addresses in all the arrs and cleanuperr because localhost:port didn't work, would setting the docker IPs be more efficient (the 127.x.x.x address)?

@Neobond commented on GitHub: Ah yeah, I put the LAN addresses in all the arrs and cleanuperr because localhost:port didn't work, would setting the docker IPs be more efficient (the 127.x.x.x address)?

giteasync commented

2025-10-09 16:59:24 -05:00

@Flaminel commented on GitHub:

Sorry, was there a question before the edit?

I could put cleanuperr in the same docker compose as the arrs and qBittorrent, and then http://localhost/ would work, am I correct in thinking this?

It depends. Did you set the network mode to host for them? If that's the case, then yes, localhost will work. If you have an internal Docker network, you should access the services through their service name set in the compose file.

@Flaminel commented on GitHub: Sorry, was there a question before the edit? > I could put cleanuperr in the same docker compose as the arrs and qBittorrent, and then http://localhost/ would work, am I correct in thinking this? It depends. Did you set the network mode to `host` for them? If that's the case, then yes, `localhost` will work. If you have an internal Docker network, you should access the services through their service name set in the compose file.

giteasync commented

2025-10-09 16:59:25 -05:00

@Flaminel commented on GitHub:

Thanks for letting me know!

The blocklists are updated only when starting the app. I might improve this in the future by updating them on a regular basis, but for now it does not make any difference if it's self hosted or not.

@Flaminel commented on GitHub: Thanks for letting me know! The blocklists are updated only when starting the app. I might improve this in the future by updating them on a regular basis, but for now it does not make any difference if it's self hosted or not.

giteasync commented

2025-10-09 16:59:25 -05:00

@Flaminel commented on GitHub:

127.x.x.x is still localhost, so you're probably referring to some other IP range. Docker IPs are not permanent so they can change after restarting. Best way is to use the service name like I did in this test file: https://github.com/flmorg/cleanuperr/blob/main/code/test/docker-compose.yml

services:
  qbittorrent:
    ...
  sonarr:
   ...
  cleanuperr:
    environment:
      - QBITTORRENT__URL=http://qbittorrent:8080
      - SONARR__INSTANCES__0__URL=http://sonarr:8989
      ...

@Flaminel commented on GitHub: `127.x.x.x` is still localhost, so you're probably referring to some other IP range. Docker IPs are not permanent so they can change after restarting. Best way is to use the service name like I did in this test file: https://github.com/flmorg/cleanuperr/blob/main/code/test/docker-compose.yml ``` services: qbittorrent: ... sonarr: ... cleanuperr: environment: - QBITTORRENT__URL=http://qbittorrent:8080 - SONARR__INSTANCES__0__URL=http://sonarr:8989 ... ```

giteasync commented

2025-10-09 16:59:25 -05:00

@Neobond commented on GitHub:

Just wanted to followup and say that it is working as intended. A fake file with .lnk was identified (via locally stored Blacklist.txt) and cleaned up with cleanuperr, thanks!

I saw in the documentation that there was an example to link to a http Blacklist.txt.. but I saved it locally, I just wanted to ask if that file updates enough to warrant linking the external http address instead self hosting it locally?

@Neobond commented on GitHub: Just wanted to followup and say that it is working as intended. A fake file with .lnk was identified (via locally stored Blacklist.txt) and cleaned up with cleanuperr, thanks! I saw in the documentation that there was an example to link to a http Blacklist.txt.. but I saved it locally, I just wanted to ask if that file updates enough to warrant linking the external http address instead self hosting it locally?

giteasync referenced this issue

2025-10-09 17:00:29 -05:00

[PR #135] [MERGED] Add option to set failed import strikes per arr #241

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/Cleanuparr#135