Closed Jorman closed 5 months ago
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...
I believe this is resolved with the latest changes. Please re-open and provide detailed logs to indicate if it isn't.
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.
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
Sonarr
I 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.