[Support] Linuxserver.io - Transmission


340 posts in this topic Last Reply

Recommended Posts

trasmission decided to stop working right so i uninstalled and deleted the appdata  reinstalled..  and i noticed its not  really updating the settings file  when i save it.. it reverts back to an older setting...  i also edited the settings.json  file so i could manually get the settings i had back.

 

but which of the settings   forces  all the downloads to start once Transmission loads..  it used to always save it  so  when i loaded transmission  start/stop etc  it would automaticlly put all files in  resume now mode...  but now everytime i load it up  its queed for download..  how you force it in the settings to "resume now" mode  when transmission loads up

 

Link to post
  • 2 weeks later...
  • Replies 339
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Application Name: Transmission Application Site: http://www.transmissionbt.com/ Docker Hub: https://hub.docker.com/r/linuxserver/transmission/ Github: https://github.com/linuxserver/doc

Possibly the path is incorrect. To what path is the docker trying to save the torrent when you get the message? Does that path correspond to something in the docker volume mappings?

Sounds like you aren't getting what jonathanm said. You said you had mapped /download, but then you said you expected to find them in /downloads. /download is not the same as /downloads.  

Posted Images

I have noticed that Transmission makes a "complete" and "incomplete" folder in the specified "/downloads" folder on startup (new or restarted).

 

I have "Host Path 2" set as "/mnt/user/media_downloads/" and in settings.json I have the following set:

 

    "download-dir": "/downloads/03 Download Complete/",

    "incomplete-dir": "/downloads/02 Download Incomplete/",

 

I have confirmed the configuration is correct and this should override the need for "complete" and "incomplete" to be created.

 

Ask: Can this be investigated? For now I just made a cronjob that deletes these folders as they are redundant and unnecessary.

unraid_variables.png

settings_json.png

folders_created.png

Edited by xaositek
Added Screenshots
Link to post
  • 3 weeks later...
On 8/8/2020 at 5:56 AM, xaositek said:

I have noticed that Transmission makes a "complete" and "incomplete" folder in the specified "/downloads" folder on startup (new or restarted).

 

I have "Host Path 2" set as "/mnt/user/media_downloads/" and in settings.json I have the following set:

 

    "download-dir": "/downloads/03 Download Complete/",

    "incomplete-dir": "/downloads/02 Download Incomplete/",

 

I have confirmed the configuration is correct and this should override the need for "complete" and "incomplete" to be created.

 

Ask: Can this be investigated? For now I just made a cronjob that deletes these folders as they are redundant and unnecessary.

unraid_variables.png

settings_json.png

folders_created.png

Same here. 

 

idk why this 2 folders are recreated every time that the dorcker starts.

Link to post

Has anyone else noticed resource issues with large torrents in 3.00?

Loading up a big torrent (latest MAME CHD in this instance) causes transmission to use 100% CPU which lags web/remote interface and also causes download speeds to drop (getting 40mbit).

 

Roll back to 2.94 (linuxserver/transmission:2.94-r3-ls53) load up the same torrent and CPU sits around 40%, UI stays responsive and speeds use my full 250mbit.

Link to post
  • 4 weeks later...

Hello! My transmission is showing port 51413 as closed, and I'm unable to seed any torrents...
Been reading through this thread and have not yet found something that worked. :/

 

I've tried running in host mode, bridge mode, and now br0 mode with a set static IP. Port forwarding for port 51413 has been configured on my router. I did initially have UPnP on and saw it as active for my docker's static IP, but I believe I read in this thread that this container does not actually support UPnP, so it's since been disabled. Still no luck... The port forwarding is currently configured as TCP/UDP, but I've also tried just using TCP and still no dice. I've also tried forwarding different ports to 51413 on the container. Afaik, nothing else is using port 51413 on my network. https://www.canyouseeme.org/ shows port 51413 as open...

 

Here's some of the container's startup logs when I last restarted it:

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[2020-09-20 14:15:59.789] Transmission 3.00 (bb6b5a062e) started (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/session.c:769)
[2020-09-20 14:15:59.790] RPC Server Adding address to whitelist: 127.0.0.1 (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/rpc-server.c:956)
[2020-09-20 14:15:59.790] RPC Server Serving RPC and Web requests on 0.0.0.0:9091/transmission/ (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/rpc-server.c:1243)
[2020-09-20 14:15:59.790] DHT Reusing old id (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/tr-dht.c:383)
[2020-09-20 14:15:59.790] DHT Bootstrapping from 112 IPv4 nodes (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/tr-dht.c:172)
[2020-09-20 14:15:59.790] Using settings from "/config" (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:646)
[2020-09-20 14:15:59.790] Saved "/config/settings.json" (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/variant.c:1221)
[2020-09-20 14:15:59.790] Watching "/watch" for new .torrent files (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:698)
[2020-09-20 14:15:59.790] Loaded 13 torrents (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/session.c:2170)
[2020-09-20 14:15:59.790] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/natpmp.c:73)
[2020-09-20 14:15:59.790] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/natpmp.c:73)
[2020-09-20 14:16:01.788] Port Forwarding (UPnP) Found Internet Gateway Device "http://192.168.0.1:5000/Public_UPNP_C3" (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/upnp.c:200)
[2020-09-20 14:16:01.788] Port Forwarding (UPnP) Local Address is "192.168.0.2" (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/upnp.c:201)
[2020-09-20 14:16:01.788] Port Forwarding (UPnP) Port forwarding through "http://192.168.0.1:5000/Public_UPNP_C3", service "urn:schemas-upnp-org:service:WANIPConnection:1". (local address: 192.168.0.2:51413) (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/upnp.c:275)
[2020-09-20 14:16:01.788] Port Forwarding State changed from "Not forwarded" to "Starting" (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/port-forwarding.c:106)
[2020-09-20 14:16:01.788] Changed open file limit from 40960 to 1024 (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/fdlimit.c:408)
[2020-09-20 14:16:01.788] web will verify tracker certs using envvar CURL_CA_BUNDLE: none (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/web.c:455)
[2020-09-20 14:16:01.788] web NB: this only works if you built against libcurl with openssl or gnutls, NOT nss (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/web.c:457)
[2020-09-20 14:16:01.788] web NB: invalid certs will show up as 'Could not connect to tracker' like many other errors (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/web.c:458)
[2020-09-20 14:16:06.790] Port Forwarding State changed from "Starting" to "???" (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/port-forwarding.c:106)
[2020-09-20 14:16:14.788] Searching for web interface file "/root/.local/share/transmission/web/index.html" (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/platform.c:472)
[2020-09-20 14:16:14.788] Searching for web interface file "/usr/share/transmission/web/index.html" (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/platform.c:472)
Caught SIGTERM signal!
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
localhost:9091/transmission/rpc/ responded: "success"
[s6-finish] sending all processes the TERM signal.
[2020-09-20 14:18:07.851] Reloading settings from "/config" (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:592)
[2020-09-20 14:18:07.851] RPC Server Adding address to whitelist: 127.0.0.1 (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/rpc-server.c:956)
[2020-09-20 14:18:07.851] RPC Server Serving RPC and Web requests on 0.0.0.0:9091/transmission/ (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/rpc-server.c:1243)
[2020-09-20 14:18:07.851] Saved "/config/settings.json" (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/variant.c:1221)
[2020-09-20 14:18:07.851] DHT Not saving nodes, DHT not ready (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/tr-dht.c:445)
[2020-09-20 14:18:07.851] Port Forwarding Stopped (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/port-forwarding.c:196)

I've attached some screenshots of my docker/routes configs and some other hopefully helpful tidbits.

 

I'm stumped. Any ideas on what else I need to try?

 

Port Closed message.png

Docker config.png

Port Forwarding Config.png

UPnP.png

canyouseeme.png

Docker overview.png

Edited by jcatfour
Link to post

Okay... I have been banging my head against the wall with the same issue on the same day you posted this. Ports forwarded on the firewall/router and canyouseeme reports yes. There could be a few avenues that could be causing this. I got a new pfSense firewall/router the same time I noticed this but now I'm thinking that's a coincidence.

Checking the git issues page there looks to be a couple of threads on this over the years and it looks like an ipv6 dns entry on their end could be causing this.
https://github.com/transmission/transmission/issues/381
https://github.com/transmission/transmission/issues/407
https://github.com/transmission/transmission/issues/1190

https://forum.transmissionbt.com/viewtopic.php?t=14274

However... both of those threads point to performing a curl against portcheck.transmissionbt.com... well... I am getting an http timeout messages when I do that, so maybe the portcheck site the transmission team has is down right now and that's all it is? isitdownrightnow is also reporting it as down? Maybe it only responds to http post requests? but the git issues threads above are just hitting it with GET requests without issue... https://www.isitdownrightnow.com/portcheck.transmissionbt.com.html


I have my container setup in bridge mode but that shouldn't cause any issues as it wasn't before. 

 

One of the git issues threads mentioned that the dev team said it was cosmetic only? 

I can't figure out if the site is truly down or there's something more at play, I have dns host overrides configured on pfSense to set that portcheck hostname to ipv4 so there's no way it could be the ipv6 vs ipv4 issue in this instance. 

I hope this helps and at the very least we can figure out why this is happening. 

Edited by Steve0Kinev0
Link to post
13 hours ago, Steve0Kinev0 said:

Okay... I have been banging my head against the wall with the same issue on the same day you posted this. Ports forwarded on the firewall/router and canyouseeme reports yes. There could be a few avenues that could be causing this. I got a new pfSense firewall/router the same time I noticed this but now I'm thinking that's a coincidence.

Checking the git issues page there looks to be a couple of threads on this over the years and it looks like an ipv6 dns entry on their end could be causing this.
https://github.com/transmission/transmission/issues/381
https://github.com/transmission/transmission/issues/407
https://github.com/transmission/transmission/issues/1190

https://forum.transmissionbt.com/viewtopic.php?t=14274

However... both of those threads point to performing a curl against portcheck.transmissionbt.com... well... I am getting an http timeout messages when I do that, so maybe the portcheck site the transmission team has is down right now and that's all it is? isitdownrightnow is also reporting it as down? Maybe it only responds to http post requests? but the git issues threads above are just hitting it with GET requests without issue... https://www.isitdownrightnow.com/portcheck.transmissionbt.com.html


I have my container setup in bridge mode but that shouldn't cause any issues as it wasn't before. 

 

One of the git issues threads mentioned that the dev team said it was cosmetic only? 

I can't figure out if the site is truly down or there's something more at play, I have dns host overrides configured on pfSense to set that portcheck hostname to ipv4 so there's no way it could be the ipv6 vs ipv4 issue in this instance. 

I hope this helps and at the very least we can figure out why this is happening. 

Hmm, I'll need to read over these in more detail after work.

I did just take a quick look at the web GUI, and it does look like the POST call comes back with status 200 eventually (once it resolved from "Unknown" to "Closed").

 

It's making a POST request to http://your_transmission_ip_and_port/transmission/rpc with a payload of :

{method: "port-test"}


After about 30 seconds, it came back as status 200, response:

{"arguments":{},"result":"portTested: http error 0: No Response"}


I don't know if that response means there was no response on the remote host hitting my network, or if their service was not getting a response from their own port checking service. 🤷‍♂️ I doubt they'd pass a 200 back if the latter were the case...

Link to post
9 hours ago, jcatfour said:

Hmm, I'll need to read over these in more detail after work.

I did just take a quick look at the web GUI, and it does look like the POST call comes back with status 200 eventually (once it resolved from "Unknown" to "Closed").

 

It's making a POST request to http://your_transmission_ip_and_port/transmission/rpc with a payload of :


{method: "port-test"}


After about 30 seconds, it came back as status 200, response:


{"arguments":{},"result":"portTested: http error 0: No Response"}


I don't know if that response means there was no response on the remote host hitting my network, or if their service was not getting a response from their own port checking service. 🤷‍♂️ I doubt they'd pass a 200 back if the latter were the case...

I dug into transmission's source code, and it does look like it's still using https://portcheck.transmissionbt.com/:your_port to test if the port is open.

 

I'm consistently getting timeouts CURLing http://portcheck.transmissionbt.com/51432, both with POST and GET, and forcing IPV4 since those git issues suggest the DNS can't resolve IPV6.

 

nslookup is working as well, so the DNS _is_ resolving just fine, it's just not responding to web requests. I couldn't ping the IP behind it either... Maybe it is down? 😕

Link to post

I'm kinda stuck, same exact scenario/results as you. Not sure if this makes you feel better, but on one of those threads I posted earlier, someone mentioned how the transmission team mentioned that it was "just cosmetic", so as long as you have the correct ports forwarded the program SHOULD function and allow you to seed. I'm going to keep an eye on it though.

Link to post
3 hours ago, Steve0Kinev0 said:

I'm kinda stuck, same exact scenario/results as you. Not sure if this makes you feel better, but on one of those threads I posted earlier, someone mentioned how the transmission team mentioned that it was "just cosmetic", so as long as you have the correct ports forwarded the program SHOULD function and allow you to seed. I'm going to keep an eye on it though.

Admittedly, I HAVE been able to seed since noticing this; however, I wanna say that you can still technically seed without having any ports forwarded, but it complicates the process of establishing a connection with peers.

 

So it's hard for me to tell if I'm able to seed as much as I should be. Based on everything else I've tested, I'm honestly just operating under the assumption that my network configuration is correct and that I should be able to seed just fine unless I see something that suggests otherwise. Some of my Linux ISOs were able to get 1+ ratios within a day or so. 😬

Link to post

Any clue on how to get RPC connection to transmission from other docker containers (Radarr, Sonarr etc.)?

This is my transmission settings.json

    "rpc-authentication-required": false,
    "rpc-bind-address": "0.0.0.0",
    "rpc-enabled": true,
    "rpc-host-whitelist": "",
    "rpc-host-whitelist-enabled": false,
    "rpc-password": "{3b46cf1a32c36234d53a361bce15946e9ecfd7e91RLaWffw",
    "rpc-port": 9091,
    "rpc-url": "/transmission/",
    "rpc-username": "user11",
    "rpc-whitelist": "127.0.0.1,192.*.*.*",
    "rpc-whitelist-enabled": false,

Sonarr just says "Unable to connect". I can get to the webinterface.

If I'm going to http://ip:9091/transmission/rpc/ I get a website showing 409: Conflict. "Your request had an invalid session-id header"

Anyone knows how to fix this?

Link to post
On 9/20/2020 at 4:25 PM, jcatfour said:

Hello! My transmission is showing port 51413 as closed, and I'm unable to seed any torrents...
Been reading through this thread and have not yet found something that worked. :/

 

I've tried running in host mode, bridge mode, and now br0 mode with a set static IP. Port forwarding for port 51413 has been configured on my router. I did initially have UPnP on and saw it as active for my docker's static IP, but I believe I read in this thread that this container does not actually support UPnP, so it's since been disabled. Still no luck... The port forwarding is currently configured as TCP/UDP, but I've also tried just using TCP and still no dice. I've also tried forwarding different ports to 51413 on the container. Afaik, nothing else is using port 51413 on my network. https://www.canyouseeme.org/ shows port 51413 as open...

 

Here's some of the container's startup logs when I last restarted it:


[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[2020-09-20 14:15:59.789] Transmission 3.00 (bb6b5a062e) started (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/session.c:769)
[2020-09-20 14:15:59.790] RPC Server Adding address to whitelist: 127.0.0.1 (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/rpc-server.c:956)
[2020-09-20 14:15:59.790] RPC Server Serving RPC and Web requests on 0.0.0.0:9091/transmission/ (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/rpc-server.c:1243)
[2020-09-20 14:15:59.790] DHT Reusing old id (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/tr-dht.c:383)
[2020-09-20 14:15:59.790] DHT Bootstrapping from 112 IPv4 nodes (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/tr-dht.c:172)
[2020-09-20 14:15:59.790] Using settings from "/config" (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:646)
[2020-09-20 14:15:59.790] Saved "/config/settings.json" (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/variant.c:1221)
[2020-09-20 14:15:59.790] Watching "/watch" for new .torrent files (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:698)
[2020-09-20 14:15:59.790] Loaded 13 torrents (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/session.c:2170)
[2020-09-20 14:15:59.790] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/natpmp.c:73)
[2020-09-20 14:15:59.790] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/natpmp.c:73)
[2020-09-20 14:16:01.788] Port Forwarding (UPnP) Found Internet Gateway Device "http://192.168.0.1:5000/Public_UPNP_C3" (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/upnp.c:200)
[2020-09-20 14:16:01.788] Port Forwarding (UPnP) Local Address is "192.168.0.2" (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/upnp.c:201)
[2020-09-20 14:16:01.788] Port Forwarding (UPnP) Port forwarding through "http://192.168.0.1:5000/Public_UPNP_C3", service "urn:schemas-upnp-org:service:WANIPConnection:1". (local address: 192.168.0.2:51413) (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/upnp.c:275)
[2020-09-20 14:16:01.788] Port Forwarding State changed from "Not forwarded" to "Starting" (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/port-forwarding.c:106)
[2020-09-20 14:16:01.788] Changed open file limit from 40960 to 1024 (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/fdlimit.c:408)
[2020-09-20 14:16:01.788] web will verify tracker certs using envvar CURL_CA_BUNDLE: none (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/web.c:455)
[2020-09-20 14:16:01.788] web NB: this only works if you built against libcurl with openssl or gnutls, NOT nss (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/web.c:457)
[2020-09-20 14:16:01.788] web NB: invalid certs will show up as 'Could not connect to tracker' like many other errors (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/web.c:458)
[2020-09-20 14:16:06.790] Port Forwarding State changed from "Starting" to "???" (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/port-forwarding.c:106)
[2020-09-20 14:16:14.788] Searching for web interface file "/root/.local/share/transmission/web/index.html" (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/platform.c:472)
[2020-09-20 14:16:14.788] Searching for web interface file "/usr/share/transmission/web/index.html" (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/platform.c:472)
Caught SIGTERM signal!
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
localhost:9091/transmission/rpc/ responded: "success"
[s6-finish] sending all processes the TERM signal.
[2020-09-20 14:18:07.851] Reloading settings from "/config" (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:592)
[2020-09-20 14:18:07.851] RPC Server Adding address to whitelist: 127.0.0.1 (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/rpc-server.c:956)
[2020-09-20 14:18:07.851] RPC Server Serving RPC and Web requests on 0.0.0.0:9091/transmission/ (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/rpc-server.c:1243)
[2020-09-20 14:18:07.851] Saved "/config/settings.json" (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/variant.c:1221)
[2020-09-20 14:18:07.851] DHT Not saving nodes, DHT not ready (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/tr-dht.c:445)
[2020-09-20 14:18:07.851] Port Forwarding Stopped (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/port-forwarding.c:196)

I've attached some screenshots of my docker/routes configs and some other hopefully helpful tidbits.

 

I'm stumped. Any ideas on what else I need to try?

 

Port Closed message.png

Docker config.png

Port Forwarding Config.png

UPnP.png

canyouseeme.png

Docker overview.png

I just updated to the latest version and am still getting the same errors and you are here. I'm still able to seed, however when checking from other sites, I'm not shown as connectable.

Link to post
  • 1 month later...

having issues with moving files after files are downloaded

isnt this right 

Key 1: PUID 99

Key 2: PGID 100

 

or is PGID to be 99 and PUID 100

 

as i get Unix/1000  persmission error in windows  when trying to move files

some files i can move some i cant.. how is it possible some files get different permisions?

 

Edited by comet424
Link to post

PUID is supposed to be the user id and PGID is supposed to be the group id of the user transmission is running as. Check out the "User / Group Identifiers" section on the docker page https://hub.docker.com/r/linuxserver/transmission.

After that you'd want to make sure the user you're using with windows has read/write access to those files/folders that the transmission user is modifying.

Link to post
On 10/12/2020 at 11:46 AM, notpedro said:

I just updated to the latest version and am still getting the same errors and you are here. I'm still able to seed, however when checking from other sites, I'm not shown as connectable.

You mean other sites are not seeing your service on the port? Were these sites seeing your service on the port prior to the update?

From my experience, I think so long as you're hosting the service on port xxxxx and have your router configured to forward port xxxxx (I used TCP/UDP) on your server's internal IP address (or the address of your docker if you configured it to have its own), it should work.

One thing I'd make sure of is setting a static IP for your server on your router, else that could eventually cause some issues. For example, you configure your router to forward port 51413 for IP 192.168.0.10, the IP address your server was using at the time, but then at some point in the future you restart your server and your router issues your server a new IP of 192.168.0.25, so now the router is forwarding that port on the wrong IP address.

Link to post
  • 1 month later...

So I use this to download asian shows that I need to reseed... I've got it downloading to an unassigned devices share right now but I was wondering - if I have it download to a share...any pros/cons to this idea?  I like that its protected vs. unassigned devices just in case that fails.   

Edited by cbr600ds2
Link to post
  • 2 weeks later...
On 12/23/2020 at 9:00 AM, rallos_hoo said:

looks like transmission 3.0 would increase cpu usage? how to fix it?


I had this same problem too. I reverted to the latest previous release by setting the repository to the following:

linuxserver/transmission:2.94-r3-ls53


Not sure what the deal is, but it has something to do with the 3.0 release.

Link to post
  • 2 weeks later...
On 11/18/2020 at 12:24 PM, jcatfour said:

You mean other sites are not seeing your service on the port? Were these sites seeing your service on the port prior to the update?

From my experience, I think so long as you're hosting the service on port xxxxx and have your router configured to forward port xxxxx (I used TCP/UDP) on your server's internal IP address (or the address of your docker if you configured it to have its own), it should work.

One thing I'd make sure of is setting a static IP for your server on your router, else that could eventually cause some issues. For example, you configure your router to forward port 51413 for IP 192.168.0.10, the IP address your server was using at the time, but then at some point in the future you restart your server and your router issues your server a new IP of 192.168.0.25, so now the router is forwarding that port on the wrong IP address.

Thanks for responding. I figured out the issue and I think it was a failed/corrupted file when I updated from 2.x to 3.x. I ended up uninstalling the image and installing fresh/clean and everything connected. Thanks again!

Link to post

After today's update I get this notification:

 

421: Misdirected RequestTransmission received your request, but the hostname was unrecognized.To fix this, choose one of the following options:Enable password authentication, then any hostname is allowed.Add the hostname you want to use to the whitelist in settings.If you're editing settings.json, see the 'rpc-host-whitelist' and 'rpc-host-whitelist-enabled' entries.This requirement has been added to help prevent DNS Rebinding attacks.

 

Password authentication was enabled before the update.

I know I should change something in settings.json but not really sure what. Any suggestions?

Link to post
3 hours ago, yogy said:

After today's update I get this notification:

 

421: Misdirected RequestTransmission received your request, but the hostname was unrecognized.To fix this, choose one of the following options:Enable password authentication, then any hostname is allowed.Add the hostname you want to use to the whitelist in settings.If you're editing settings.json, see the 'rpc-host-whitelist' and 'rpc-host-whitelist-enabled' entries.This requirement has been added to help prevent DNS Rebinding attacks.

 

Password authentication was enabled before the update.

I know I should change something in settings.json but not really sure what. Any suggestions?

I have same problem, was trying to change settings, but saw that after container restart, new settings.json file is generated.

Link to post

I have everything working before the update. Now I cannot enable my password and have no clue how to whitelist hosts.

I shutdown the Transmission container, tried to edit settings.json (/mnt/user/appdata/transmission) with no luck on enabling password again. It keeps going back to false. I can change rpc-host-whitelist entries but nothing I enter there works.

Link to post
15 minutes ago, yogy said:

I have everything working before the update. Now I cannot enable my password and have no clue how to whitelist hosts.

I shutdown the Transmission container, tried to edit settings.json (/mnt/user/appdata/transmission) with no luck on enabling password again. It keeps going back to false. I can change rpc-host-whitelist entries but nothing I enter there works.

I too am experiencing the same issue after updating (authentication/password settings will not stay enabled/true).

Link to post
2 hours ago, Mathew R. said:

I too am experiencing the same issue after updating (authentication/password settings will not stay enabled/true).

You have to stop the container before editing settings. Otherwise, transmission will overwrite any settings when it shuts down and potentially while it's running.

 

I've also experienced rpc issues with the latest update. Been trying to downgrade, but now I can't get authenticated when it was previously enabled and working fine.

Link to post

Ok, for anyone having issues with the latest update

 

- I downgraded by changing repository to "linuxserver/transmission:3.00-r0-ls71"

- stopped the transmission container

- then I had to re-enter my username/password in settings.json. you may not have to do this, i think i had to because i was trying to get the latest version to work and was messing around with settings

- start the container

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.