Transmission authentication not working when using Docker Secrets

[Mahir007]

Hi, I am having an issue whereby I cannot login to Web UI when setting a username/password via docker secrets.
I created a container using the following compose file:

version: '3.3'
services:
    transmission-openvpn:
        image: haugene/transmission-openvpn
        container_name: transmission-openvpn
        cap_add:
            - NET_ADMIN
        volumes:
            - /volume1/docker/transmission-openvpn:/config
            - /volume1/docker/openvpn/provider:/etc/openvpn/custom/
            - /volume1/MagZ Plus/Media Apps/downloads:/data/downloads
        environment:
            - PUID=1030
            - PGID=100
            - TZ=Europe/London
            - OPENVPN_PROVIDER=custom
            - OPENVPN_CONFIG=london_GB
            - LOCAL_NETWORK=192.168.1.0/24
            - GLOBAL_APPLY_PERMISSIONS=false
            - TRANSMISSION_WEB_UI=transmission-web-control
            - TRANSMISSION_SCRAPE_PAUSED_TORRENTS_ENABLED=false
            - TRANSMISSION_RPC_AUTHENTICATION_REQUIRED=true
            - TRANSMISSION_DOWNLOAD_DIR=/data/downloads
            - TRANSMISSION_WATCH_DIR=/data/downloads/watch
            - TRANSMISSION_INCOMPLETE_DIR=/data/downloads/incomplete
        secrets:
            - openvpn_creds
            - rpc_creds
        ports:
            - '9091:9091'
        restart: always
secrets:
    openvpn_creds:
        file: /volume1/docker/openvpn/secrets/openvpn_creds
    rpc_creds:
        file: /volume1/docker/openvpn/secrets/rpc_creds

I can successfully navigate to the web ui, however, I just can't seem to be able to login even though I am literally copy/pasting my login info. Here is what my rpc_creds file looks like at the moment:

naim
test$password123

In addition, when checking the transmission config file, I can see that it added a "\r" to the end of my username for some reason ("rpc-username": "naim\r",). Attempting to login with "naim\r" as my username doesn't seem to do anything though.

So, other than resorting back to using env variables to set my user/pass, is there anything I'm missing as to why this is not working or is there a bug with this feature at the moment?

Lastly, my log file:
transmission-openvpn.csv

[ilike2burnthing]

Not sure this will necessarily make a difference, but I noticed that you're missing volume mapping for /data. You could change to /volume1/MagZ Plus/Media Apps:/data and it shouldn't affect anything else.

Looking at the relevant FAQ section, I don't see any obvious issues with your compose file.

[edgd1er]

I guess the problem lies with the special character not being handled here, may be elsewhere.
For the time being, you may tray to replace any sign that is interpreted by the bash like $ or !
you may try to escape special characters with a .

docker-transmission-openvpn/openvpn/start.sh

Lines 225 to 226 in 2cf661c

	echo "${TRANSMISSION_RPC_USERNAME}" > /config/transmission-credentials.txt
	echo "${TRANSMISSION_RPC_PASSWORD}" >> /config/transmission-credentials.txt

you current password might be test123 or even just test

[Mahir007]

Okay, I've tried just "test" as my password and there's no change in behaviour, I am still not able to login.

[edgd1er]

and/or have a look to the content of /config/transmission-credentials.txt

[Mahir007]

Contents of "transmission-credentials.txt":

naim
test

(and yes, the third empty line is present within the file but isn't present in "openvpn-credentials.txt")

[edgd1er]

As I was looking into the code, the env variable are written to the settings.json file before launching transmission daemon.
echoing ${TRANSMISSION_RPC_USERNAME} and ${TRANSMISSION_RPC_PASSWORD} would inform you about the values written to the json.
I expect the password to be different.