-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Couldn't read '/opt/transmission-ui/flood-for-transmission/config.json': No such file or directory #2761
Comments
I see the same issue here.. |
This commit from @defkev / @johman10 appears to be the cause of the issue - johman10/flood-for-transmission@edb6e11 |
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.:
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: |
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
andlatest
back to5.3.0
;5.2
is the latest unaffected build.Checking the container,
5.2
hasconfig.json
, whereas5.3.0
and onwards haveconfig.json.defaults
.Expected Behavior
config.json
existsHow have you tried to solve the problem?
Manually creating the file resolves the issue, but that's not exactly a great fix.
Log output
HW/SW Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: