haugene / docker-transmission-openvpn

Docker container running Transmission torrent client with WebUI over an OpenVPN tunnel
GNU General Public License v3.0
4.03k stars 1.2k forks source link

Couldn't read '/opt/transmission-ui/flood-for-transmission/config.json': No such file or directory #2761

Open ilike2burnthing opened 7 months ago

ilike2burnthing commented 7 months ago

Is there a pinned issue for this?

Is there an existing or similar issue/discussion for this?

Is there any comment in the documentation for this?

Is this related to a provider?

Are you using the latest release?

Have you tried using the dev branch latest?

Docker run config used

If you can't replicate this issue I can provide Portainer screenshots.

Current Behavior

Open Transmission in browser when using Flood UI, or refresh page, and error appears in log. Affects dev and latest back to 5.3.0; 5.2 is the latest unaffected build.

Checking the container, 5.2 has config.json, whereas 5.3.0 and onwards have config.json.defaults.

Expected Behavior

config.json exists

How have you tried to solve the problem?

Manually creating the file resolves the issue, but that's not exactly a great fix.

Log output

[2023-12-12 07:31:26.476] ERR utils.cc:105 Couldn't read '/opt/transmission-ui/flood-for-transmission/config.json': No such file or directory (2) (utils.cc:105)

HW/SW Environment

- OS: Asustor ADM x86_64
- Docker: 23.06

Anything else?

No response

pkishino commented 7 months ago

I see the same issue here.. nothing regarding flood has changed what I see, only transmission version up.. no time to dig into this for a while now though

ilike2burnthing commented 6 months ago

This commit from @defkev / @johman10 appears to be the cause of the issue - https://github.com/johman10/flood-for-transmission/commit/edb6e11a9d3368a6d7dd7a24ebee99927e15017c

defkev commented 6 months ago

If my memory serves me right the final verdict here was to hardcode the defaults in an exportable module and load any customization from config.json (if present) and soft fail if that doesn't work (e.g. not present as in your case)

config.json.defaults mever gets loaded and only serves as a skeleton/template/starting point, e.g.: mv config.json.defaults config.json

[2023-12-12 07:31:26.476] ERR utils.cc:105 Couldn't read '/opt/transmission-ui/flood-for-transmission/config.json': No such file or directory (2) (utils.cc:105)

Assuming this is logged by transmission-daemon (utls.cc) the error makes no sense as flood's config.json is loaded by your browser when accessing the frontend (http://host:9091) not transmission.

Edit: I just pulled a fresh copy of johman10/flood-for-transmission on my seed box, copied my custom config.json and everything is working as expected.