Transmission

Ah! Solved it. :)

I had for some reason changed the script to run using my user instead of the debian-transmission user. I had also changed the owner/group of the settings.json file. I changed the user and permissions back to the debian-transmission user, and voila, password hashed.

I must have ...

Well, the problem here is that I start the transmission-daemon as a service. If I use your command, a settings.json file is created in .config/transmission-daemon in my home folder. But this is not the correct settings file.

The settings.json file I'd like to edit is located in /etc/transmission ...

For example here.

What exactly do I do to "restart using the command line to enter your rpc username and password combo"? Could you give me an example command?

Yes, entered directly in settings.json file in quotes. That was the procedure as far as I read everywhere?

I have entered the password of the rpc in the settings.json file, but when Transmission is restarted the password is still in plain text. Everyone says the password is supposed to be hashed automatically in other threads I've looked at.

The new user and password works fine in the WebUI, and ...