starred/Cleanuparr
1
0
Fork 0
mirror of https://github.com/Cleanuparr/Cleanuparr.git synced 2026-04-13 15:16:50 -05:00
Code Issues 38 Packages Projects Releases 10 Wiki Activity

[BUG] BASE_PATH is ignored by icon URLs #8

New Issue
Closed
opened 2025-10-09 16:56:27 -05:00 by giteasync · 1 comment
giteasync commented 2025-10-09 16:56:27 -05:00
Owner
Copy Link

Originally created by @Racle 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?

When setting BASE_PATH=/cleanuparr, icons are still loaded from root and not from BASE_PATH and they are not found by web server (nginx, reverse proxy).

They are loaded from https://domain.com/icons/ext/lidarr-light.svg
Instead of https://domain.com/cleanuparr/icons/ext/lidarr-light.svg
Same thing for cleanuparr logo etc.

Solution:
Make UI element URLs also respect BASE_PATH when loading assets

Which operating system do you use?

Linux

What type of deployment do you use?

Docker container

Relevant log output

Anything else?

No response

Originally created by @Racle 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? When setting `BASE_PATH=/cleanuparr`, icons are still loaded from root and not from `BASE_PATH` and they are not found by web server (nginx, reverse proxy). They are loaded from `https://domain.com/icons/ext/lidarr-light.svg` Instead of `https://domain.com/cleanuparr/icons/ext/lidarr-light.svg` Same thing for cleanuparr logo etc. Solution: Make UI element URLs also respect `BASE_PATH` when loading assets ### Which operating system do you use? Linux ### What type of deployment do you use? Docker container ### Relevant log output ```shell ``` ### Anything else? _No response_
giteasync added the bug label 2025-10-09 16:56:27 -05:00
giteasync commented 2025-10-09 16:56:28 -05:00
Author
Owner
Copy Link

@Flaminel commented on GitHub:

Thank you for reporting the issue! It's fixed in v2.3.3.

@Flaminel commented on GitHub: Thank you for reporting the issue! It's fixed in `v2.3.3`.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
enhancement
planned
pull-request
Mirrored from GitHub Pull Request
 question
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
giteasync
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Cleanuparr#8
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?