[SOLVED] Transmission Connection Refused

[jonnypb]

I have a QNAP TS119 NAS

I had a powercut in my house and ever since Transmission won't work. I've updated to 2.22 but that's made no difference.

If I open Transmission Remote GUI I just get connection refused all the time. If I go the http://nas:9091 I get Could not connect to remote server.

This is my Settings.json

{
"alt-speed-down": 50,
"alt-speed-enabled": false,
"alt-speed-time-begin": 540,
"alt-speed-time-day": 127,
"alt-speed-time-enabled": false,
"alt-speed-time-end": 1020,
"alt-speed-up": 50,
"bind-address-ipv4": "0.0.0.0",
"bind-address-ipv6": "::",
"blocklist-enabled": true,
"cache-size-mb": 2,
"dht-enabled": true,
"download-dir": "/share/Qdownload/transmission/completed",
"encryption": 0,
"idle-seeding-limit": 30,
"idle-seeding-limit-enabled": false,
"incomplete-dir": "/share/Qdownload/transmission/incomplete",
"incomplete-dir-enabled": true,
"lazy-bitfield-enabled": true,
"lpd-enabled": true,
"message-level": 2,
"open-file-limit": 32,
"peer-congestion-algorithm": "",
"peer-limit-global": 240,
"peer-limit-per-torrent": 60,
"peer-port": 51413,
"peer-port-random-high": 65535,
"peer-port-random-low": 49152,
"peer-port-random-on-start": false,
"peer-socket-tos": 0,
"pex-enabled": true,
"port-forwarding-enabled": true,
"preallocation": 2,
"proxy": "",
"proxy-auth-enabled": false,
"proxy-auth-password": "",
"proxy-auth-username": "",
"proxy-enabled": false,
"proxy-port": 80,
"proxy-type": 0,
"ratio-limit": 2,
"ratio-limit-enabled": false,
"rename-partial-files": true,
"rpc-authentication-required": false,
"rpc-bind-address": "0.0.0.0",
"rpc-enabled": true,
"rpc-password": "{cffb60b05f66d94b2d136a12c5f5ece8c75e2b76/R/E5KU8",
"rpc-port": 9091,
"rpc-username": "admin",
"rpc-whitelist": "127.0.0.1",
"rpc-whitelist-enabled": true,
"script-torrent-done-enabled": false,
"script-torrent-done-filename": "",
"speed-limit-down": 0,
"speed-limit-down-enabled": false,
"speed-limit-up": 30,
"speed-limit-up-enabled": true,
"start-added-torrents": true,
"trash-original-torrent-files": false,
"umask": 00,
"upload-slots-per-torrent": 15,
"watch-dir": "/share/Qdownload/transmission/watch",
"watch-dir-enabled": true

Please help!

Thanks

[gunzip]

"rpc-whitelist": "127.0.0.1",
"rpc-whitelist-enabled": true,

it seems you have rpc-whitelist enabled but are allowing only localhost 127.0.0.1 access . try adding remote ip address:

"rpc-whitelist": "127.0.0.*,192.168.1.*"

above is what i use but yours could be different. basically you have to whitelist the remote ip address you're connecting from .. wildcards * are acceptable. remember to stop the transmission-daemon before editing settings.json or changes won't stick.

[jonnypb]

"rpc-whitelist": "127.0.0.1",
"rpc-whitelist-enabled": true,

it seems you have rpc-whitelist enabled but are allowing only localhost 127.0.0.1 access . try adding remote ip address:

"rpc-whitelist": "127.0.0.*,192.168.1.*"

above is what i use but yours could be different. basically you have to whitelist the remote ip address you're connecting from .. wildcards * are acceptable. remember to stop the transmission-daemon before editing settings.json or changes won't stick.

Still the same error

I've tried setting the whitelist to false as well but no joy

[gunzip]

did you check that port 9091 is open? that's all i can think of at the moment

[jonnypb]

did you check that port 9091 is open? that's all i can think of at the moment

Do you mean on my router or nas? If nas how would I check that?

Thanks

[gunzip]

sorry i don't have a nas, but is there an admin or firewall control panel you can login to and check settings?

[jonnypb]

Ok I can telnet to port 8080 on my nas which is the general admin site but I can't telnet to 9091 which transmission uses. I'll have a look on my nas for settings.

It worked fine until a powercut the other night!

Cheers

[jonnypb]

Log file

[18:47:41.008] transmission-daemon Error loading config file -- exiting. (daemon.c:458)
[22:35:37.806] transmission-daemon Error loading config file -- exiting. (daemon.c:472)
[22:35:51.474] transmission-daemon Error loading config file -- exiting. (daemon.c:472)
[22:36:41.322] transmission-daemon Error loading config file -- exiting. (daemon.c:472)
[22:50:06.367] transmission-daemon Error loading config file -- exiting. (daemon.c:472)
[23:00:14.636] transmission-daemon Error loading config file -- exiting. (daemon.c:472)
[00:37:38.670] transmission-daemon Error loading config file -- exiting. (daemon.c:472)
[23:00:32.943] transmission-daemon Error loading config file -- exiting. (daemon.c:472)
[23:01:01.833] transmission-daemon Error loading config file -- exiting. (daemon.c:472)

[Jordan]

That reads to me like your settings.json is corrupt.

If you've edited by hand, try running it through an online json parser to see if there are any errors.

One brute-force solution would be to delete the file, let transmission-daemon generate a new one with default values, and then edit that new one as necessary.

[jonnypb]

That reads to me like your settings.json is corrupt.

If you've edited by hand, try running it through an online json parser to see if there are any errors.

One brute-force solution would be to delete the file, let transmission-daemon generate a new one with default values, and then edit that new one as necessary.

THANK YOU SO MUCH

I ran it through a json parser and it found and error with the following

"umask": 0002,

It said to many trailing 0's

It now reads "umask": 2, and I no longer get the connection refused error