Replies: 2 comments
-
ooh, and i doesnt update port in transmission through PIA anymore... |
Beta Was this translation helpful? Give feedback.
0 replies
-
So, to answer my own question, and for others with issues, -i've figured it out.. Something changed a while ago with the placement og transmission-home and config volume. My old setup did'nt use a config dir for transmission (wasnt needed back then) but stored the transmission-home dir and settings.json in data volume location. This apperently have changed :-)... So the fix was to add config volume mapping in docker-compose & move transmission-home/* to that location. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I just noticed i had problems using webproxy and discovered at ton of unauthorized logins plus missing settings.json.
I didn't have the config dir, but thet setup have been working for a long time. I now created the config volume in my compose file, but the issue still persists.
Have also read about password needs to be hashed, could that be the issue??
Running functions for token based port fowarding
Reserved Port: 50158 Tue Dec 6 11:39:51 CET 2022
grep: /config/transmission-home/settings.json: No such file or directory
transmission auth not required
waiting for transmission to become responsive
Unexpected response:
401: Unauthorized
Unauthorized UserXmUUnexpected response:
401: Unauthorized
Unauthorized User�PVUnexpected response:
401: Unauthorized
Unauthorized Userf�UUnexpected response:
401: Unauthorized
Unauthorized User�"VUnexpected response:
401: Unauthorized
Unauthorized UservnUBeta Was this translation helpful? Give feedback.
All reactions