Transmission

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 ...

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 ...

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

gunzip wrote: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

"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 ...

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 ...