[BUG] Confusing behavior around overwriting authentication settings

[azban]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

in the init script, there are some actions that make it hard to debug what is going on.

1. If you do not specify the USER and PASS environment variables, then it automatically sets rpc-authentication-enabled to false.
2. If you do not specify the WHITELIST environment variables, then it automatically set rpc-whitelist-enabled to false.

i have seen other issues in the repo where the maintainers seem to think this is the best approach. i think this is limiting for 2 reasons:

1. it could be preferable to provide the password in the way that transmission allows by setting it directly in settings.json and then is salted on startup. otherwise, plaintext passwords need to be used in docker configuration or initialization. with the current setup, this is impossible.
2. it is a nice experience for a user to be able to use an existing settings.json file that they use in other deployments

this could be done in a backwards-compatible way if we added another environment variable to not automatically override these settings.

either way, it would at least be good to be explicit about what is happening in the documentation, and to add some logging to the init script so that users could see that what values are getting written by inference of environment variables. i'm happy to put up a PR with some guidance on if the option to not override is desirable.

Expected Behavior

No response

Steps To Reproduce

1. stop container
2. modify certain keys in settings.json
3. start container
4. unexpected overrides

Environment

CPU architecture

x86-64

Docker creation

docker-compose

Container logs

no relevant logs

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[pomah86]

This is still active, I would love to get this fixed so that we can use the settings.json file for configuration
.

[azban]

it should be a fairly easy fix, just need to figure out if this is something the maintainers would want to merge in

[muryoh]

Just ran into this myself, indeed confusing as I was reusing an existing settings.json file
Note that you can provide an already salted password to PASS (had to quote the whole definition in my docker-compose.yml file, eg 'PASS={13i3491i4efijqfi')

[pomah86]

Just ran into this myself, indeed confusing as I was reusing an existing settings.json file Note that you can provide an already salted password to PASS (had to quote the whole definition in my docker-compose.yml file, eg 'PASS={13i3491i4efijqfi')

Thank you, I will look into that, still new to this virtual/Docker thing, need to learn a little bit more to get comfortable with where all the configuration should be.

[pomah86]

I just tried the latest release where you can specify "USER=" and "PASS=" as environemental variables and I do get the login promp but it wont accept the user or pass I have selected.

I even tried to create a new instance with a simple password, 5 letters are lower case and it still would not acknoledge the user and/or pass. I could not see any issues in the logs so sadly no more clues to why it does not work :(

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[xX-MrN0b0dy-Xx]

Is

I just tried the latest release where you can specify "USER=" and "PASS=" as environemental variables and I do get the login promp but it wont accept the user or pass I have selected.

I even tried to create a new instance with a simple password, 5 letters are lower case and it still would not acknoledge the user and/or pass. I could not see any issues in the logs so sadly no more clues to why it does not work :(

I was running an old image. I recently pulled the latest to find out there is a bug in which USER setting is completely neglected and fallback to root. Luckily at least the password is the one u can set with PASSWORD.

Reported as bug in #310

[pomah86]

Is

I just tried the latest release where you can specify "USER=" and "PASS=" as environemental variables and I do get the login promp but it wont accept the user or pass I have selected.
I even tried to create a new instance with a simple password, 5 letters are lower case and it still would not acknoledge the user and/or pass. I could not see any issues in the logs so sadly no more clues to why it does not work :(

I was running an old image. I recently pulled the latest to find out there is a bug in which USER setting is completely neglected and fallback to root. Luckily at least the password is the one u can set with PASSWORD.

Reported as bug in #310

Thank I will try that later

EDIT: Tried it now, no luck, set user to "test" and pass to "test", tried with both user: "test" and "root" but no success to login.

Tried not to use "USER=" but just "PASS=" but that did not yield any login prompt.