Transmission remote keenetic ошибка подключения

Прошу прощения как новичок, если тема заезжена, но чесслово, не нашел ответа. Итак, проблема (помогаю дочке): медиаплеер ASUS O!Play HDP-3R, подключен по Wi-Fi к интернету через роутер Netgear N150. В домашней сети имеет адрес 192.168.1.4. На плеер установил пакет MoServices как описано здесь на сайте через ноутбук, в свою очередь, на котором я установил прогу Transmission Remote GUI. В составе пакета запущен бит-торрент клиент Transmission. Так вот, проблема в управлении Transmission с помощью Transmission GUI Remote. Нифига не подключается. В инструкции написаны логин и пароль веб-интерфейса login: torrent, pwd: 1234. Создаю соединение в программе Transmission Remote GUI с адресом

http://192.168.1.4

, логином и паролем — отказ в соединении. Причем если адрес указать именно как

http://

<…>, то сообщение host not found, если же просто 192.168.1.4, то connection refused. Попытки обнулить логин и пароль ничего не дают. В то же время если в интернет-эксплорере тупо вбить 192.168.1.4, то ноут отлично соединяется с медиаплеером, появляется некий графический интерфейс, в котором есть пункт меню bittorrent client, тыкая в который вызывается некая управлялка к нему, позволяющая создавать закачки. И все работает. Но управлялка бедноватая, опять-таки она отлична по виду от привычного uTorrent клиента, что для дочки очень критично (мне-то наплевать). Хотелось бы прикрутить Transmission Remote GUI. Что я делаю не так? Я в общем-то знаю, что Transmission имеет ограничения по удаленному управлению, но штука в том, что обычные описания 127.0.01, 192.168.*.* должно вполне устраивать — ноут именно адрес такого вида имеет в домашней сети (192.168.1.2 или .3 — сейчас точно не помню). Т.е. по идее стандартная маска вполне должна подходить. Насчет проброски портов — пока порт 9091 в роутере не пробрасывал, но ПМСМ это не особо и нужно — обычным-то веб-интерфейсом от интернет-эксплорера Transmission управляется, причем по умолчанию именно через порт 9091. Еще раз прошу извинить, если тема знакомая.

первый раз такое услышал. Если из браузера

http://192.168.1.4:9091

доступен, то и Remote GUI должен работать.
На всякий случай скиньте конфиг трансмишена сюда.

Если честно, я официальную прошивку снёс последний раз полтора года назад По поводу вайфай — имхо баловство это — драйвера под реалтековский чип, который стоит у вас зело кривые и выпрямлять их никто не собирается.
Да и скорости по вафле не хватает для более-менее серьёзных потоков. Мой вам совет — не поленитесь, прокиньте провод.
тема moServices3 —

viewtopic.php?f=16&t=694

тема альтернативных прошивок —

viewtopic.php?f=8&t=1029

ФАК по прошивке плеера —

viewforum.php?f=21

I’m getting connection refused with the Remote GUI although my Transmission settings file has not changed from earlier, when it worked fine.

Here output of ps aux | grep transmission-daemon:

pi       15534  0.0  0.4   3548  1836 pts/0    S+   16:40   0:00 grep --color=to transmission-daemon

To confirm the daemon should be running fine on the RPi.

settings.json file:

{
    "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": 5,
    "bind-address-ipv4": "0.0.0.0",
    "bind-address-ipv6": "::",
    "blocklist-enabled": true,
    "blocklist-url": "http://url"
    "cache-size-mb": 4,
    "dht-enabled": true,
    "download-dir": "/mnt/usbdrive/torrent/done",
    "download-limit": 100,
    "download-limit-enabled": 0,
    "download-queue-enabled": true,
    "download-queue-size": 15,
    "encryption": 1,
    "idle-seeding-limit": 30,
    "idle-seeding-limit-enabled": false,
    "incomplete-dir": "/mnt/usbdrive/torrent/temp",
    "incomplete-dir-enabled": true,
    "lpd-enabled": false,
    "max-peers-global": 200,
    "message-level": 2,
    "peer-congestion-algorithm": "",
    "peer-limit-global": 240,
    "peer-limit-per-torrent": 30,
    "peer-port": 51413,
    "peer-port-random-high": 65535,
    "peer-port-random-low": 49152,
    "peer-port-random-on-start": false,
    "peer-socket-tos": "default",
    "pex-enabled": true,
    "port-forwarding-enabled": true,
    "preallocation": 1,
    "prefetch-enabled": 1,
    "queue-stalled-enabled": true,
    "queue-stalled-minutes": 30,
    "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": "password",
    "rpc-port": 9091,
    "rpc-url": "/transmission/",
    "rpc-username": "admin",
    "rpc-whitelist": "127.0.0.1,192.168.2.*",
    "rpc-whitelist-enabled": false,
    "scrape-paused-torrents-enabled": false,
    "script-torrent-done-enabled": false,
    "script-torrent-done-filename": "",
    "seed-queue-enabled": true,
    "seed-queue-size": 2,
    "speed-limit-down": 100,
    "speed-limit-down-enabled": false,
    "speed-limit-up": 100,
    "speed-limit-up-enabled": false,
    "start-added-torrents": false,
    "trash-original-torrent-files": false,
    "umask": 18,
    "upload-limit": 100,
    "upload-limit-enabled": 0,
    "upload-slots-per-torrent": 2,
  "utp-enabled": true,
    "watch-dir": "/mnt/usbdrive/torrent/watch",
    "watch-dir-enabled": true
}

I used to require RPC authentication and use an RPC whitelist, but I disabled both for testing, but that doesn’t help with the connection issue.

After research and googling, I’m suspecting it is due to folder permissions: I detached my USB drive on Raspberry Pi which is running Transmission Daemon as a service, and after reattaching the Remote GUI can’t connect. Could this be it?

Here permissions on the torrent temp folder:

drwxrwxrwx  37 root debian-transmission   4096 Jan  1 13:50 temp

This is the output of sudo netstat -tanp:

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:49632           0.0.0.0:*               LISTEN      2842/btsync-daemon
tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN      5945/smbd
tcp        0      0 0.0.0.0:6000            0.0.0.0:*               LISTEN      3372/X
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      4321/sshd
tcp        0      0 0.0.0.0:8888            0.0.0.0:*               LISTEN      2842/btsync-daemon
tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN      5945/smbd
tcp        0      0 192.168.2.48:445        192.168.2.18:40300      ESTABLISHED 6816/smbd
tcp        0      0 192.168.2.48:139        192.168.2.18:42347      ESTABLISHED 6298/smbd
tcp        0      0 192.168.2.48:22         192.168.2.18:44234      ESTABLISHED 12845/sshd: pi [pri

If I understand correctly, Transmission Daemon should be on this list as listening on 9091, but it’s not. So something is wrong.

My settings.json states that it should be listening on 9091, so not sure how to proceed with troubleshooting?

I re-installed the daemon, but I still get connection refused

I noticed that the two bind address fields below are both 0.0.0.0. Is this an issue? I tried changing them to the IP of the Raspberry Pi Transmission is running on, but I still can’t connect.

    "bind-address-ipv4": "0.0.0.0",
    "rpc-bind-address": "0.0.0.0",

The new install settings.json had «port-forwarding-enabled» set as false, and when I set it as true now I was finally able to connect, and everything is working fine!

the bind addresses are both 0.0.0.0 in the working settings.json file, so that wasn’t it.

So re-installing fixed it, and still don’t know what went wrong with the initial install.

And back, still talking to myself.

I’m unable to reconnect again, with the same settings.json file (below) which worked just a while ago

So there’s something outside Transmission which is intermittently messing things up. I’m able to connect to the RPi using samba file transfer, PuTTY and rsync, but Transmission Remote GUI gives Connection Refused error even when I have RPC whitelist and authentication disabled.

I’m at my wit’s end. Anyone have any ideas?

{
    "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": 5,
    "bind-address-ipv4": "0.0.0.0",
    "bind-address-ipv6": "::",
    "blocklist-enabled": true,
    "blocklist-url": "http://[url]",
    "cache-size-mb": 4,
    "dht-enabled": true,
    "download-dir": "[location]",
    "download-limit": 100,
    "download-limit-enabled": 0,
    "download-queue-enabled": true,
    "download-queue-size": 15,
    "encryption": 1,
    "idle-seeding-limit": 30,
    "idle-seeding-limit-enabled": false,
    "incomplete-dir": "[location]",
    "incomplete-dir-enabled": true,
    "lpd-enabled": false,
    "max-peers-global": 200,
    "message-level": 2,
    "peer-congestion-algorithm": "",
    "peer-limit-global": 240,
    "peer-limit-per-torrent": 30,
    "peer-port": 51413,
    "peer-port-random-high": 65535,
    "peer-port-random-low": 49152,
    "peer-port-random-on-start": false,
    "peer-socket-tos": "default",
    "pex-enabled": true,
    "port-forwarding-enabled": true,
    "preallocation": 1,
    "prefetch-enabled": 1,
    "queue-stalled-enabled": true,
    "queue-stalled-minutes": 30,
    "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": "[password]",
    "rpc-port": 9091,
    "rpc-url": "/transmission/",
    "rpc-username": "admin",
    "rpc-whitelist": "*.*.*.*",
    "rpc-whitelist-enabled": false,
    "scrape-paused-torrents-enabled": false,
    "script-torrent-done-enabled": false,
    "script-torrent-done-filename": "",
    "seed-queue-enabled": true,
    "seed-queue-size": 2,
    "speed-limit-down": 100,
    "speed-limit-down-enabled": false,
    "speed-limit-up": 100,
    "speed-limit-up-enabled": false,
    "start-added-torrents": false,
    "trash-original-torrent-files": false,
    "umask": 18,
    "upload-limit": 100,
    "upload-limit-enabled": 0,
    "upload-slots-per-torrent": 2,
    "utp-enabled": true,
    "watch-dir": "[location]",
    "watch-dir-enabled": true
}

By almost an accident I noticed that the daemon shuts down or crashes shortly after starting it. After I run sudo service transmission-daemon reload/restart pair of commands, or just start it with start it reports OK. Running the same command with status shortly afterwards says OK as well. I can also confirm the service is running with ps ax.

But only a minute later, status says FAIL (Transmission not running) and ps ax doesn’t report anything on transmission!

Yet another round of uninstalling and re-installing from scratch. I went through each step to catch where everything breaks apart. RPC whitelist and authentication disabled, was able to connect with remote and web GUI. Enabled and set whitelist, and enabled authentication, reload and restart, still works. Then I copied my old torrents files from my previous installation, still working.

Finally, I copy my resume folder as well. And now it stops working! After I reload and restart the daemon, I’m unable to connect, and running ps ax confirms the daemon has shut down or has crashed. Testing it again, it crashes after roughly 10 seconds.

I delete the resume folder again, and remote access is back to functional. So something in the resume folder is messing things up!

Thought it was a permissions or file or group ownership issue, but that wasn’t it — at least changing them to pi:debian-transmission didn’t help.

Long story long: as I couldn’t figure out what in the resume folder was breaking things, I ended up deleting the resume folder. It turns out Transmission will create that folder with entries for all the torrents loaded. I’m currently running verification on the incomplete torrents and it recognizes the existence of previous incomplete files, and everything seems to be fine.

Took only several hours over several days… What a mess.

TLDR: in my case the original issue of being unable to connect is still unresolved. My suspicion is that apt-get upgrade broke something.

After reinstalling transmission-daemon, I could add earlier torrents to it, but adding the old resume folder broke Transmission. Therefore I deleted the resume folder, and ran verify on all existing torrents, ensuring that the temp folder location points to the location of the temp files. Now I’m getting all my previous incomplete torrents to resume, and all my earlier unstarted torrents to run.