mirror of
https://github.com/RandomNinjaAtk/arr-scripts.git
synced 2026-03-02 22:57:35 -05:00
[BUG] - arr-scripts - not all scripts work with non-standard ports #152
Labels
No labels
Needs Triage
Not Reproducible
Upstream Issue
User Error
bug
documentation
enhancement
good first issue
help wanted
invalid
lidarr
lidarr
question
radarr
readarr
sabnzbd
sonarr
synology (host)
unraid (host)
waiting for logs
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/arr-scripts#152
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @Jorman on GitHub (May 31, 2024).
Hi, thanks for this collection of scripts!
I would like to point out one thing that only affects some scripts, so not all, if you want you can extend the conversation and create a detailed report.
If applications use a non-standard port then some scripts will not work, this an example log from
SonarrI noticed that in the function file, the port of use is extracted, as well as a lot of other information
arrPort="$(cat /config/config.xml | xq | jq -r .Config.Port)"
However, it is not reported in all scripts that are executed.
@RandomNinjaAtk commented on GitHub (Jun 7, 2024):
Please provide a list of the scripts your having an issue with, most, if not all should work with whatever port you have set.
One culprit of not supporting custom ports is QueueCleaner, but I just pushed changes to that today that resolves that....
So if you cannot provide more detailed logs and which scripts need further investigation, I'm going to close this a resolved...
@RandomNinjaAtk commented on GitHub (Jun 15, 2024):
I believe this is resolved with the latest changes. Please re-open and provide detailed logs to indicate if it isn't.
@Jorman commented on GitHub (Jun 16, 2024):
Hi, sorry for the delay in replying, I'll do some testing these days and let you know if it's ok, I'll go ahead and update the script now.
From what I remember, I had to manually change the ports in multiple files.
I'll let you know as soon as I check, thanks.
Do you have any suggestions for testing all the scripts in one go? Maybe by enabling an extended log.