You are not logged in.
- Topics: Active | Unanswered
Pages: 1
Topic closed
#1 2013-08-04 00:58:13
- ritalin
- Member
- Registered: 2013-06-15
- Posts: 32
Transmission daemon "could not connect to server" when using webui?
subject explains it. I have a laptop im trying to use as a server for the transmission daemon (included the transmission-cli) and other services. I was going to use the webui over my lan to add torrents , but i receive an error stating "Connection Failed: Could not connect to the server. You may need to reload the page to reconnect." The strange thing is that if I try this on the machine running the daemon, I get the same error as I do trying to access the ui from a separate computer on the lan. I tried many different configurations and switched the username in the systemctl unit to utilize the settings.json file in /home/(user)/.config/transmission-daemon/ (originally, the username is "transmission" and it uses the settings.json file in /var/lib/transmission/.config/transmission-daemon/) I'm not sure where to go from here, but I found some interesting things in my journalctl that i'm going to post along with other config files and commands, though i'm only going to post the settings.json in my home folder, since the one in /var I believe is redundant and not in use.
the command I used to start the transmission-daemon at boot
# systemctl enable transmission relevant journalctl output (my terminal seemed to cut off the very end for some reason)
Aug 02 01:07:00 cr-48 transmission-daemon[1149]: Transmission 2.81 (14128) started (session.c:738)
Aug 02 01:07:00 cr-48 transmission-daemon[1149]: RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:828)
Aug 02 01:07:00 cr-48 transmission-daemon[1149]: RPC Server Serving RPC and Web requests on port 127.0.0.1:9091/transmission/
Aug 02 01:07:00 cr-48 transmission-daemon[1149]: RPC Server Whitelist enabled (rpc-server.c:1039)
Aug 02 01:07:00 cr-48 transmission-daemon[1149]: UDP Failed to set receive buffer: requested 4194304, got 425984 (tr-udp.c:78)
Aug 02 01:07:00 cr-48 transmission-daemon[1149]: UDP Please add the line "net.core.rmem_max = 4194304" to /etc/sysctl.conf (tr
Aug 02 01:07:00 cr-48 transmission-daemon[1149]: UDP Failed to set send buffer: requested 1048576, got 425984 (tr-udp.c:89)
Aug 02 01:07:00 cr-48 transmission-daemon[1149]: UDP Please add the line "net.core.wmem_max = 1048576" to /etc/sysctl.conf (tr
Aug 02 01:07:00 cr-48 transmission-daemon[1149]: DHT Generating new id (tr-dht.c:310)
Aug 02 01:07:00 cr-48 transmission-daemon[1149]: Using settings from "/home/nickcage/.config/transmission-daemon" (daemon.c:52
Aug 02 01:07:00 cr-48 transmission-daemon[1149]: Saved "/home/nickcage/.config/transmission-daemon/settings.json" (variant.c:1
Aug 02 01:07:00 cr-48 transmission-daemon[1149]: Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:73)
Aug 02 01:07:00 cr-48 transmission-daemon[1149]: Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:73
Aug 02 01:07:08 cr-48 transmission-daemon[1149]: Port Forwarding State changed from "Not forwarded" to "Starting" (port-forwar
Aug 02 01:07:08 cr-48 transmission-daemon[1149]: Port Forwarding State changed from "Starting" to "???" (port-forwarding.c:95)
Aug 02 01:07:58 cr-48 transmission-daemon[1149]: DHT Attempting bootstrap from dht.transmissionbt.com (tr-dht.c:248)
Aug 02 01:17:48 cr-48 transmission-daemon[1149]: Saved "/home/nickcage/.config/transmission-daemon/settings.json" (variant.c:1
-- Reboot --
my systemctl unit file (/etc/systemd/system/multi-user.target.wants/transmission.service)
[Unit]
Description=Transmission BitTorrent Daemon
After=network.target
[Service]
User=nickcage
Type=notify
ExecStart=/usr/bin/transmission-daemon -f --log-error
[Install]
WantedBy=multi-user.target
my /home/nickcage/.config/transmission-daemon/settings.json (I dont really need whitelist or auth settings since im the only user on my network)
{
"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": false,
"blocklist-url": "http://www.example.com/blocklist",
"cache-size-mb": 4,
"dht-enabled": true,
"download-dir": "/mnt/seagate/Downloads",
"download-queue-enabled": true,
"download-queue-size": 5,
"encryption": 1,
"idle-seeding-limit": 30,
"idle-seeding-limit-enabled": false,
"incomplete-dir": "/home/nickcage/Downloads",
"incomplete-dir-enabled": false,
"lpd-enabled": false,
"message-level": 1,
"peer-congestion-algorithm": "",
"peer-id-ttl-hours": 6,
"peer-limit-global": 200,
"peer-limit-per-torrent": 50,
"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": "{d27c5f07d68b4893f122b22ef9f67d12cc536636RqdBZSg3",
"rpc-port": 9091,
"rpc-url": "/transmission/rpc",
"rpc-username": "username",
"rpc-whitelist": "127.0.0.1,192.168.1.8",
"rpc-whitelist-enabled": false,
"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": 100,
"speed-limit-down-enabled": false,
"speed-limit-up": 100,
"speed-limit-up-enabled": false,
"start-added-torrents": true,
"trash-original-torrent-files": false,
"umask": 18,
"upload-slots-per-torrent": 14,
"utp-enabled": true
} Offline
#3 2013-08-04 01:57:59
- ritalin
- Member
- Registered: 2013-06-15
- Posts: 32
Re: Transmission daemon "could not connect to server" when using webui?
Just as a sanity check, what URL are you using to access your server?
on the machine running the daemon, localhost:9091 which redirects to something like localhost:9091/transmission/rpc, and on a different machine 192.168.1.31:9091 which does the same redirect
Last edited by ritalin (2013-08-04 02:59:24)
Offline
#4 2013-08-04 14:39:50
- Stebalien
- Member
- Registered: 2010-04-27
- Posts: 1,239
- Website
Re: Transmission daemon "could not connect to server" when using webui?
That should be `<host>:9091/transmission/web`. Please post a screenshot of the exact error.
Also, is that log complete? It claims that transmission is listening on 127.0.0.1:9091 but it's obviously listening on 0.0.0.0:9091 (as configured).
Last edited by Stebalien (2013-08-04 14:40:18)
Offline
#5 2013-08-04 19:18:39
- ritalin
- Member
- Registered: 2013-06-15
- Posts: 32
Re: Transmission daemon "could not connect to server" when using webui?
That should be `<host>:9091/transmission/web`. Please post a screenshot of the exact error.
Also, is that log complete? It claims that transmission is listening on 127.0.0.1:9091 but it's obviously listening on 0.0.0.0:9091 (as configured).
I have 3 screencaps, the one with the ip 192.168.1.31 is from a computer on the lan, the other two are on the server itself, note that no matter what type in, it always redirects to /rpcweb, even if type in /transmission/web like you suggested.
http://oi41.tinypic.com/o6zn11.jpg
http://oi40.tinypic.com/307yov8.jpg
http://oi39.tinypic.com/f9e42f.jpg
And yeah I mentioned that the log was cut off slightly with my terminal emulator, but I think its good now
the code I used to gather the log (running as root gives what appears to be allot of useless info but ill post it if you like.)
$ journalctl 14:47:13 EDT, end at Sat 2013-08-03 01:30:07 EDT. --
(to nickcage) nickcage on none
pam_unix(su:session): session opened for user root by nickcage(uid=1000)
: pam_unix(sudo:auth): authentication failure; logname=nickcage uid=1000 euid=0 tty=/dev/tty1 ruser=nickcage rhost= user=nick
ion-daemon[1149]: Transmission 2.81 (14128) started (session.c:738)
ion-daemon[1149]: RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:828)
ion-daemon[1149]: RPC Server Serving RPC and Web requests on port 127.0.0.1:9091/transmission/ (rpc-server.c:1035)
ion-daemon[1149]: RPC Server Whitelist enabled (rpc-server.c:1039)
ion-daemon[1149]: UDP Failed to set receive buffer: requested 4194304, got 425984 (tr-udp.c:78)
ion-daemon[1149]: UDP Please add the line "net.core.rmem_max = 4194304" to /etc/sysctl.conf (tr-udp.c:83)
ion-daemon[1149]: UDP Failed to set send buffer: requested 1048576, got 425984 (tr-udp.c:89)
ion-daemon[1149]: UDP Please add the line "net.core.wmem_max = 1048576" to /etc/sysctl.conf (tr-udp.c:94)
ion-daemon[1149]: DHT Generating new id (tr-dht.c:310)
ion-daemon[1149]: Using settings from "/home/nickcage/.config/transmission-daemon" (daemon.c:526)
ion-daemon[1149]: Saved "/home/nickcage/.config/transmission-daemon/settings.json" (variant.c:1217)
ion-daemon[1149]: Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:73)
ion-daemon[1149]: Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:73)
ion-daemon[1149]: Port Forwarding State changed from "Not forwarded" to "Starting" (port-forwarding.c:95)
ion-daemon[1149]: Port Forwarding State changed from "Starting" to "???" (port-forwarding.c:95)
ion-daemon[1149]: DHT Attempting bootstrap from dht.transmissionbt.com (tr-dht.c:248)
ion-daemon[1149]: Saved "/home/nickcage/.config/transmission-daemon/settings.json" (variant.c:1217)
: pam_unix(sudo:auth): authentication failure; logname=nickcage uid=1000 euid=0 tty=/dev/tty1 ruser=nickcage rhost= user=nick
: pam_unix(sudo:auth): authentication failure; logname=nickcage uid=1000 euid=0 tty=/dev/tty1 ruser=nickcage rhost= user=nick
: pam_unix(sudo:auth): conversation failed
: pam_unix(sudo:auth): conversation failed
: pam_unix(sudo:auth): authentication failure; logname=nickcage uid=1000 euid=0 tty=/dev/tty1 ruser=nickcage rhost= user=nick
: pam_unix(sudo:auth): conversation failed
: pam_unix(sudo:auth): authentication failure; logname=nickcage uid=1000 euid=0 tty=/dev/tty1 ruser=nickcage rhost= user=nick
~
~
~
~
~
lines 1-33/33 (END)
Offline
#6 2024-01-08 15:31:43
- fabioamd87
- Member
- Registered: 2008-11-22
- Posts: 128
Re: Transmission daemon "could not connect to server" when using webui?
Hi guys I have the same issue, if I log in with the hostname.local I got the message, if I put the IP address of the remote machine it works.
Offline
#7 2024-01-09 12:24:10
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 25,231
Re: Transmission daemon "could not connect to server" when using webui?
You are bumping an 11 year old thread, please open up a new topic with details on your issue.
Closing.
Offline
Pages: 1
Topic closed