I'm a newbie to Raspberry Pi & Linux and am following the guide posted here (http://www.htpcguides.com/install-transm...untu-15-x/) on how to setup Transmission on a Raspberry Pi. After I have followed the guide I can login to transmission by the IP:9091 but when I reboot the Pi, it tells me I cannot connect.
[Not Solved]Mar 12, 2016, 07:07 PM (This post was last modified: Mar 12, 2016, 08:10 PM by grunt101.
Edit Reason: More detail
)
(Mar 12, 2016, 05:59 PM)Mike Wrote: Looks like I may need to update the guide. Do me a favor and reboot then find all the settings.json files
Code:
find / -iname settings.json
Then have a look in both files, they should be the same, if they aren't then stop the service and modify the other one and restart the Pi.
Thanks for the reply. I just tried and when I type it in the first time, nothing shows. However, when I issue the command again it either gives me a lot of "No such file or directory" or "Permission denied" on various folders, even if I execute with sudo.
Just checked and the above json files. The settings are both the same before and after I restart the service. As I mentioned, once I restart the service, I can access the web interface.
[Not Solved]Mar 13, 2016, 07:01 AM (This post was last modified: Mar 13, 2016, 07:17 AM by grunt101.)
I saw someone mention using a netstat command, which I done (See attached).
Before I restart the service, there is nothing listening on port 9091, but after the restart the transmission daemon is listening on that port and I can access the web interface
Edit: I'm using a Raspberry Pi 3 with the Wifi and I see that this post they seemed to solve the error, but not sure how it relates to what I'm doing
[Not Solved]Mar 13, 2016, 10:56 AM (This post was last modified: Mar 13, 2016, 11:33 AM by Mike.)
If you are using wireless then that is the issue, for some reason even with the specified network.target for the systemd file it doesn't help Transmission start late enough. To get rid of this inconvenience you can use monit
Are you using official Raspbian? I do not get this issue on my Minibian image.