Transmission

https://trac.transmissionbt.com/ticket/5737

I don't know if similar to this bug report.

Anyway, transmission-daemon works seamlessly, starts fine. WebUI doesn't work initially, fails to connect.

If I quit transmission and restart, or restart transmission via terminal, or even simply opening the transmission-GUI and going to preferences>remote to uncheck "allow remote access" and recheck it, WebUI starts to work seamlessly!

Weird bug but would be grateful for a workaround.

Thanks!

Any news on this?
I'm experiencing the same problem on Raspian with Raspberry 1 rev B.
I read on the net that many users are experiencing the same problem, and after a while no one replies anymore.
I don't know if the users are finding solutions without posting them, or what.

I found that it was probably related to the DHCP taking too long to obtain an IP address, I tried to switch to static IP but nothing changes.
I also tried to modify the script in init.d adding a sleep of 20sec but it doesn't seems to change anything.

Any advice?
Thank you

PS: to confirm the that the problem is the same, after reboot the WebUI doesn't work but the service status is running, if I do service restart or stop/start from terminal everything work correctly.

Hi any updates?
I have exactly the same problem. I installed transmission on my raspberry pi2.
The transmission-daemon starts on boot but I just can't get access through web.
I can confirm daemon start by getting pid number using "pidof transmission-daemon" command.
Login to my pi2 and restart trasmission-daemon will bring web back.

I tried put
" sleep 30
sudo /etc/init.d/transmission-daemon stop
sleep 5
sudo /etc/init.d/trasnmission-daemon start
"
at /etc/rc.local
it doesn't work.

I also tried create local.conf as below

sudo mkdir -p /etc/systemd/system/transmission-daemon.service.d
sudo nano /etc/systemd/system/transmission-daemon.service.d/local.conf

and then add
[Unit]
After=network.target

[Service]
ExecStart=
ExecStart=/usr/bin/transmission-daemon -f --log-error -g /etc/transmission-daemon

It doesn't work either.

Does anyone know how to fix this?

Thanks in advance!

Thank you so much x190

The raspi-config solution didn't work, I don't know why. However writing reload script in /etc/init.d/ works like a charm!
My guess was right that it is something with ip address and/or port. I just wonder why my solution: sleep 30, stop, sleep 5, start in rc.local didn't work.

Anyway I am glad that it works now!

Thanks again!!

fantast_xu wrote:Hi any updates?

If you saw release notes for 2.90, there's an item saying "Retry if RPC server fails to bind to specified address", which is exactly what this thread is about. See also #5737.

Has anyone with this issue tried 2.90 (or later)?