+- Forum (http://forum.xbian.org)
+-- Forum: Software (/forum-6.html)
+--- Forum: Additional Packages (/forum-22.html)
+--- Thread: Transmission installed, but no web ui access (/thread-2102.html)
Transmission installed, but no web ui access - agent5150 - 10th Feb, 2014 12:57 PM
HI, I installed transmission using xbian-config via ssh.
I can start and stop transmission daemon, but if I try to browse to its web-ui, browser says this page cannot be loaded. Nor can I connect it via transmission-qt windows client.
also /var/log/daemon.log is empty no lines in it.
how do I verify its even running? is web-ui part of transmission package for xbian?
This is my settings.json:
{
"alt-speed-down": 1500,
"alt-speed-enabled": false,
"alt-speed-time-begin": 75,
"alt-speed-time-day": 127,
"alt-speed-time-enabled": true,
"alt-speed-time-end": 420,
"alt-speed-up": 100,
"bind-address-ipv4": "0.0.0.0",
"bind-address-ipv6": "::",
"blocklist-enabled": false,
"blocklist-url": "http://www.example.com/blocklist",
"cache-size-mb": 2,
"dht-enabled": true,
"download-dir": "/media/BKUP1/torrents/downloads",
"download-queue-enabled": true,
"download-queue-size": 5,
"encryption": 1,
"idle-seeding-limit": 30,
"idle-seeding-limit-enabled": false,
"incomplete-dir": "/media/BKUP1/torrents/downloads",
"incomplete-dir-enabled": false,
"lazy-bitfield-enabled": true,
"lpd-enabled": true,
"max-peers-global": 500,
"message-level": 2,
"open-file-limit": 32,
"peer-congestion-algorithm": "",
"peer-limit-global": 500,
"peer-limit-per-torrent": 150,
"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,
"proxy": "",
"proxy-auth-enabled": false,
"proxy-auth-password": "",
"proxy-auth-username": "",
"proxy-enabled": false,
"proxy-port": 80,
"proxy-type": 0,
"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": "mypassword",
"rpc-port": 9091,
"rpc-url": "/transmission/",
"rpc-username": "",
"rpc-whitelist": "127.0.0.1,192.168.1.*",
"rpc-whitelist-enabled": true,
"scrape-paused-torrents-enabled": true,
"script-torrent-done-enabled": false,
"script-torrent-done-filename": "",
"seed-queue-enabled": false,
"seed-queue-size": 10,
"speed-limit-down": 500,
"speed-limit-down-enabled": true,
"speed-limit-up": 10,
"speed-limit-up-enabled": true,
"start-added-torrents": true,
"trash-original-torrent-files": false,
"umask": 18,
"upload-slots-per-torrent": 14,
"utp-enabled": true,
"watch-dir": "/media/BKUP1/torrents/watch",
"watch-dir-enabled": true
}
RE: Transmission installed, but no web ui access - agent5150 - 10th Feb, 2014 11:10 PM
19 views... no suggestions? . Appreciate some help here.
RE: Transmission installed, but no web ui access - xraxor - 10th Feb, 2014 11:13 PM
Hi, to check if service is running login via SSH, on the xbian-config goto services will tell if transmission is running. from there you also restart the service, enable autostart and so on.
RE: Transmission installed, but no web ui access - palswim - 11th Mar, 2014 03:31 PM
(10th Feb, 2014 12:57 PM)agent5150 Wrote: HI, I installed transmission using xbian-config via ssh.
I can start and stop transmission daemon, but if I try to browse to its web-ui, browser says this page cannot be loaded. Nor can I connect it via transmission-qt windows client.
also /var/log/daemon.log is empty no lines in it.
how do I verify its even running? is web-ui part of transmission package for xbian?
This is my settings.json:
{
"rpc-authentication-required": false,
"rpc-bind-address": "0.0.0.0",
"rpc-enabled": true,
"rpc-password": "mypassword",
"rpc-port": 9091,
"rpc-url": "/transmission/",
"rpc-username": "",
"rpc-whitelist": "127.0.0.1,192.168.1.*",
"rpc-whitelist-enabled": true,
}
I'm taking some shots in the dark, but can you get it running by disabling the RPC Whitelist ("rpc-whitelist-enabled": false,)?
Also, try having a username, even with "rpc-authentication-required": false.