hotshot05
Posts: 5
Joined: Fri Mar 27, 2015 6:43 pm

Unable to access Transmission remote Web UI on system boot

Sat Jun 25, 2016 8:16 pm

I have set up transmission-daemon. I have tried to get it to run at system boot.

After my RPi 2 boots up, I run

Code: Select all

systemctl status transmission-daemon
It gives me the response

Code: Select all

● transmission-daemon.service - Transmission BitTorrent Daemon
   Loaded: loaded (/lib/systemd/system/transmission-daemon.service; enabled)
   Active: active (running) since Sat 2016-06-25 19:43:24 UTC; 1min 6s ago
 Main PID: 545 (transmission-da)
   Status: "Uploading 72.98 KBps, Downloading 23.87 KBps."
   CGroup: /system.slice/transmission-daemon.service
           └─545 /usr/bin/transmission-daemon -f --log-error
This tells me that the transmission-daemon is running.

But when I try to access the Web UI from another machine, it always says Unable to access address

Then I run

Code: Select all

sudo service transmission-service reload
After this when I try to access the Web UI, it works fine.

I tried creating a script by running the following commands -

Code: Select all

sudo nano /etc/init.d/transmissionboot.sh

sleep 15s && sudo service transmission-daemon reload &

Ctrl + O & Ctrl + X

sudo chmod +x /etc/init.d/transmissionboot.sh 
sudo update-rc.d transmissionboot.sh defaults
I tried running the above script manually using

Code: Select all

cd /etc/init.d
./transmissionboot.sh
It executed correctly (I was able to access Web UI after running the script manually after system boot)

But this thing does not work on its own. It never reloads on system boot. Please help.
I installed Raspbian Jessie today and while setting up Transmission, got these issues. In Raspbian Wheezy, I did not get such issues.

Threads that I have looked at -
viewtopic.php?f=63&t=135320
viewtopic.php?t=149850&p=987535
viewtopic.php?f=63&t=135209&p=899926&hi ... ui#p899926
And many more posts. These are the ones which are still open in my browser.

hotshot05
Posts: 5
Joined: Fri Mar 27, 2015 6:43 pm

Re: Unable to access Transmission remote Web UI on system bo

Sun Jun 26, 2016 4:05 am

Solved my problem.

Added the service transmission-daemon reload command to the rc.local file
Edit the file rc.local using the following command -

Code: Select all

sudo nano /etc/rc.local
This is how my rc.local file looks right now -

Code: Select all

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

# Print the IP address
service transmission-daemon start
#wait for sometime to let everything get loaded by the OS
sleep 10
#without doing reload, remote Web UI does not work
service transmission-daemon reload
sleep 3
#start the vnc server
su - pi -c '/usr/bin/tightvncserver :1 -geometry 1366x768 -depth 24'

_IP=$(hostname -I) || true
if [ "$_IP" ]; then
  printf "My IP address is %s\n" "$_IP"
fi

exit 0
P.S - Solved the autostart problem of VNC Server also.

Links from where I got these codes -
https://pimylifeup.com/raspberry-pi-torrentbox/ (Got it from a comment on this post)
http://raspberrypi.stackexchange.com/qu ... berry-pi-2
https://www.raspberrypi.org/documentati ... c-local.md

Note - Thread can be marked as fixed

User avatar
davidcoton
Posts: 3946
Joined: Mon Sep 01, 2014 2:37 pm
Location: Cambridge, UK

Re: Unable to access Transmission remote Web UI on system bo

Sun Jun 26, 2016 8:06 am

hotshot05 wrote:Solved my problem.
Note - Thread can be marked as fixed
You can do that. Edit the title of the first post in the thread.
Signature retired

Pochikun
Posts: 1
Joined: Sat Jul 02, 2016 9:34 am

Re: Unable to access Transmission remote Web UI on system bo

Sat Jul 02, 2016 10:34 am

Just in case someone is interested:
I also had this problem and managed to solve it following the example above (thank you hotshot05!) However, before finding the solution I did

Code: Select all

sudo netstat -lntp ps aux | grep transmission
and got

Code: Select all

tcp        0      0 0.0.0.0:51413           0.0.0.0:*               LISTEN      607/transmission-da
tcp6       0      0 :::51413                :::*                    LISTEN      607/transmission-da
and after manually entering

Code: Select all

sudo service transmission-daemon reload
I got

Code: Select all

tcp        0      0 0.0.0.0:9091            0.0.0.0:*               LISTEN      607/transmission-da
tcp        0      0 0.0.0.0:51413           0.0.0.0:*               LISTEN      607/transmission-da
tcp6       0      0 :::51413                :::*                    LISTEN      607/transmission-da
so port 9091 (used to access the web interface) was not being listened to by transmission unless the daemon was reloaded after boot.

hotshot05
Posts: 5
Joined: Fri Mar 27, 2015 6:43 pm

Re: Unable to access Transmission remote Web UI on system bo

Tue Aug 02, 2016 6:11 pm

Apparently Transmission daemon still has to be reloaded manually even after this. It worked for a few days after I posted. But after that I again have to reload the daemon to open the Web UI.
Still trying to understand what is happening.

User avatar
nerdykit
Posts: 12
Joined: Tue Jan 15, 2013 5:30 pm
Location: Vancouver, BC

Re: Unable to access Transmission remote Web UI on system bo

Tue Aug 09, 2016 4:41 pm

I'm no expert but the following seems to have fixed the problem for me. The issue is with the startup process and the establishment of networking before transmission-daemon is started which is why manually starting transmission after the boot seems to provide a working transmission whereas starting transmission as part of boot is leaving transmission running but unreachable by the web interface or remote GUI.

Run raspi-config (sudo raspi-config)

Go to item 4 "Wait for Network at Boot", select it and choose "Would you like to wait until a network connection is established?", select "Yes" and then "Ok" to the confirmation question (what would I select if it's not Ok ?) and Finish raspi-config and reboot your pi (sudo reboot) and (at least in my case), problem solved. Transmission can now be reached by web interface and remote GUI after the boot is complete.
What me...?

dasomoli
Posts: 1
Joined: Fri Oct 06, 2017 2:05 pm

Re: Unable to access Transmission remote Web UI on system bo

Fri Oct 06, 2017 2:10 pm

nerdykit wrote:
Tue Aug 09, 2016 4:41 pm
I'm no expert but the following seems to have fixed the problem for me. The issue is with the startup process and the establishment of networking before transmission-daemon is started which is why manually starting transmission after the boot seems to provide a working transmission whereas starting transmission as part of boot is leaving transmission running but unreachable by the web interface or remote GUI.

Run raspi-config (sudo raspi-config)

Go to item 4 "Wait for Network at Boot", select it and choose "Would you like to wait until a network connection is established?", select "Yes" and then "Ok" to the confirmation question (what would I select if it's not Ok ?) and Finish raspi-config and reboot your pi (sudo reboot) and (at least in my case), problem solved. Transmission can now be reached by web interface and remote GUI after the boot is complete.
That's the simplest working solution.
Thank you.

Return to “General discussion”