[BUG] BASE_PATH inconsistencies #34

New Issue

giteasync · 2025-10-09T16:56:52-05:00

giteasync commented

2025-10-09 16:56:52 -05:00

Originally created by @Chinoman10 on GitHub.

Before submitting a bug report, I have:

Reviewed the documentation.
Ensured I am using ghcr.io/cleanuparr/cleanuparr docker repository.
Ensured I am using the latest version.
Enabled verbose logging.

What is the behavior?

Changed the BASE_PATH to cleanuparr, and all pages work except Radarr and Sonarr.
Upon further looking at the network requests, it seems those pages are making requests to the root host instead of host+base_path for /login?

I did notice something odd though; if I use a "clean" domain that has nothing on the root (such as cleanuparr.domain.tld), everything works normally, but if I have a website (such as Homarr) under the root domain, then that causes 404 errors with: Not connected to server: Check your network connection or try reloading the page.

Opening Lidarr, Readarr, etc. all works fine though; it's just Radarr and Sonarr that are causing issues.

Which operating system do you use?

Windows with WSLv2 (Ubuntu)

What type of deployment do you use?

Docker (Desktop) container (Compose)

Relevant log output

Anything else?

No response

Originally created by @Chinoman10 on GitHub. ### Before submitting a bug report, I have: - [x] Reviewed the documentation. - [x] Ensured I am using ghcr.io/cleanuparr/cleanuparr docker repository. - [x] Ensured I am using the latest version. - [x] Enabled verbose logging. ### What is the behavior? Changed the `BASE_PATH` to `cleanuparr`, and all pages work except Radarr and Sonarr. Upon further looking at the network requests, it seems those pages are making requests to the root host instead of host+base_path for `/login`? I did notice something odd though; if I use a "clean" domain that has nothing on the root (such as `cleanuparr.domain.tld`), everything works normally, but if I have a website (such as `Homarr`) under the root domain, then that causes 404 errors with: `Not connected to server`: `Check your network connection or try reloading the page`. <img width="1020" height="504" alt="Image" src="https://github.com/user-attachments/assets/7e638e39-64ab-4d3b-ba63-59182f2c6303" /> Opening Lidarr, Readarr, etc. all works fine though; it's just Radarr and Sonarr that are causing issues. ### Which operating system do you use? Windows with WSLv2 (Ubuntu) ### What type of deployment do you use? Docker (Desktop) container (Compose) ### Relevant log output ```shell ``` ### Anything else? _No response_

giteasync added the

bug

label 2025-10-09 16:56:52 -05:00

giteasync closed this issue

2025-10-09 16:56:53 -05:00

giteasync commented

2025-10-09 16:56:54 -05:00

@Flaminel commented on GitHub:

For your test/reproduction, did you try with a Homarr instance on the root path?

I did not, as I don't even know what Homarr is, but it seems like that might be the source of your problem. As mentioned before, there's no login route for Cleanuparr, and I suspect something is not sent to Homarr which fails the subsequent request to the actual API. Care to join Discord to discuss?

Is there some env var I can set for 'debug' log levels? On the console, I mean, so I can check if these 404 requests are hitting the container at all or not?

Log level is available in general settings, but I doubt it's going to log every request made to the API, as that would fill up the logs pretty fast.

@Flaminel commented on GitHub: > For your test/reproduction, did you try with a Homarr instance on the root path? I did not, as I don't even know what Homarr is, but it seems like that might be the source of your problem. As mentioned before, there's no login route for Cleanuparr, and I suspect something is not sent to Homarr which fails the subsequent request to the actual API. Care to join Discord to discuss? > Is there some env var I can set for 'debug' log levels? On the console, I mean, so I can check if these 404 requests are hitting the container at all or not? Log level is available in general settings, but I doubt it's going to log every request made to the API, as that would fill up the logs pretty fast.

giteasync commented

2025-10-09 16:56:54 -05:00

@Chinoman10 commented on GitHub:

Sorry!, haven't been able to dedicate some time to my home stack, work's been crazy lately...
Going on holidays soon, so hopefully I'll be able to test things out and get to the bottom of this.

@Chinoman10 commented on GitHub: Sorry!, haven't been able to dedicate some time to my home stack, work's been crazy lately... Going on holidays soon, so hopefully I'll be able to test things out and get to the bottom of this.

giteasync commented

2025-10-09 16:56:54 -05:00

@Flaminel commented on GitHub:

So I am currently trying to reproduce it and I'm failing. Are you sure it's not from something being cached on your end? Does trying the same configuration in an incognito tab have the same result?

those pages are making requests to the root host instead of host+base_path for /login?

Are you sure this is Cleanuparr related? The login route does not exist yet.

@Flaminel commented on GitHub: So I am currently trying to reproduce it and I'm failing. Are you sure it's not from something being cached on your end? Does trying the same configuration in an incognito tab have the same result? <img width="2544" height="1320" alt="Image" src="https://github.com/user-attachments/assets/abc13602-1021-4424-b7f6-6c1f36e074ef" /> > those pages are making requests to the root host instead of host+base_path for /login? Are you sure this is Cleanuparr related? The `login` route does not exist yet.

giteasync commented

2025-10-09 16:56:54 -05:00

@Flaminel commented on GitHub:

@Chinoman10 ?

@Flaminel commented on GitHub: @Chinoman10 ?

giteasync commented

2025-10-09 16:56:54 -05:00

@Chinoman10 commented on GitHub:

I dunno... maybe it's something funky with Homarr... But not sure how that would be related, since everything under /cleanuparr is meant to be delivered to this container.
For your test/reproduction, did you try with a Homarr instance on the root path?

It's odd that everything else except the /sonarr and /radarr sub-paths work...

Is there some env var I can set for 'debug' log levels? On the console, I mean, so I can check if these 404 requests are hitting the container at all or not?

@Chinoman10 commented on GitHub: <img width="1053" height="307" alt="Image" src="https://github.com/user-attachments/assets/71d945f8-c212-4a91-b907-bac5f70fc527" /> I dunno... maybe it's something funky with Homarr... But not sure how that would be related, since everything under `/cleanuparr` is meant to be delivered to this container. For your test/reproduction, did you try with a Homarr instance on the root path? It's odd that everything else except the `/sonarr` and `/radarr` sub-paths work... Is there some env var I can set for 'debug' log levels? On the console, I mean, so I can check if these 404 requests are hitting the container at all or not?

giteasync commented

2025-10-09 16:56:54 -05:00

@Flaminel commented on GitHub:

@Chinoman10 I'm going to close this soon.

@Flaminel commented on GitHub: @Chinoman10 I'm going to close this soon.

giteasync referenced this issue

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

[PR #34] [MERGED] Increase trigger interval limit #293

Sign in to join this conversation.