FAQ

Q: There is a typo in the project name "transmisson-remote-gui". It should be "transmission-remote-gui". Was it made for purpose?

A: Unfortunately, the typo was made during creation of the project on Google Code. The only way to fix it is to delete the current project and create a new project. The typo was noticed too late.

Q: Is it possible to run transgui directly from a USB stick?

A: Yes. Just create a folder on your USB stick and copy there the transgui executable file (and, optionally, the lang folder). Then create empty transgui.ini file in that folder. Now you can run the transgui executable directly from the USB stick. All settings will be stored at the stick as well.

Q: Is it possible to run several instances of the program?

A: Yes. By default, transgui stores all it's settings in the user's profile. To run an extra instance of the program, you need to explicitly specify some other folder to store the program's settings. To do that, pass the --home=<home_dir> parameter. Where <home_dir> is some folder where the program's settings of the new instance will be stored.

Q: What mean numbers like 4/28 in the Seeds column?

A: Seeds: 4/28:

• 4 - number of peers, from which we are downloading now (connected seeders).
• 28 - total number of available peers, which have this torrent (available seeders).

Q: What mean numbers like 2/7 in the Peers column?

A: Peers: 2/7:

• 2 - number of peers, which are downloading from us (connected leechers).
• 7 - total number of downloading peers on the tracker (total number of leechers).

Q: What's the meaning of an icon with red arrow (up or down) in the names column?

A: A red icon indicates a error. To find out the error message, look at the "Error" in the General page at the bottom of the main window.

Q: What is path mapping?

A: Path mappings are used to convert a remote path (on a computer where a Transmission daemon is running) to a local path (local computer where Transmission Remote GUI is running). And vice versa. The mappings are used to open remote files and folders. The path mappings are configured in the Connection options on the Paths page.

For example, your torrents are downloaded into the /var/pub/downloads folder by a Transmission daemon running on a NAS. You access the daemon from a Windows PC using Transmission Remote GUI. You have network access to the /var/pub folder on the NAS as network drive K:. In that case you should specify the following path mapping:

/var/pub/downloads=K:\downloads

If you can access the /var/pub folder using a UNC path such as \\nas\pub, then use the following path mapping:

/var/pub/downloads=\\nas\pub\downloads

[Anonymous]

Originally posted by: ASamarts...@gmail.com

Hi adding files are not on a magnet link, and on hash?

[Anonymous]

Originally posted by: jerry...@speakeasy.net

USING REMOTE GUI LOCALLY

Installing Transmission and its Remote GUI on the same Linux (Kubuntu/Ubuntu) box.

You can access over a Web browser at <code>http://localhost:9091/transmission/web </code>

or you can run the Remote GUI directly as another Ubuntu installed program.

Get the Kubunt/Ubuntu APPLICATION LAUNCHER MENU icon onto a panel or your desktop, start it, see if INTERNET / TRANSMISSION (BitTorrent Client) is listed. If not, install it.

sudo apt-get install transmission

Next problem: getting transgui to make a connection to machine running transmission:

The Remote GUI is not remote, both are on a machine which you can ping on a terminal running on that machine as

--Wilbur or

--192.168.1.142 (its reserved address on LAN)

--127.0.0.1

If the Remote GUI TOOLS / APPLICATION OPTIONS / TRANSMISSION / Remote host says "Connection refused" (or maybe "Host not found" ) for all of these valid "remote" host names, then perhaps you forgot to install the daemon that services connection requests:

sudo apt-get install transmission-daemon

Sometimes you have to be sure the service is started:

sudo service transmission-daemon start (or stop)

(tips on other commands to work with daemons would be appreciated)

If the daemon is runing, your connection is accepted and listed in the drop-down menu of valid "remote" connections in the upper extreme left of GUI ("New connection" "Manage connections")

After connecting comes the password challenge "Unauthorized user".

Remote GUI TOOLS / APPLICATION OPTIONS / TRANSMISSION / Authentication required.

If the correct user and password on your very own machine are not accepted, its because transmission GUI is entirely setup by its own configuration file "transmission.json" and knows nothing about the machine it has been installed into. Use the default user/pwd,

--transmission

--transmission or change it:

Edit transmission.json as usual:

sudo service transmission-daemon stop

do your edits, typing user and pwd in plain text

sudo service transmission-daemon start (daemon converts plaintext pwd to a hashcode)

To make a spare safety copy before editing:

_sudo cp /etc/transmission-daemon/settings.json /etc/transmission-daemon/settings.json.backup_

(Thank you papibe on this 2010 forum: http://ubuntuforums.org/archive/index.php/t-1605096.html)

I hardly know what I'm doing and other commands and tips are welcome.

Can anyone figure out why <b>Wiki syntax</b> is not working ?

--jerry

[Anonymous]

Originally posted by: jerry...@speakeasy.net

[size=5]FIGHTING "CONNECTION REFUSED" in the REMOTE GUI[/size]

Maybe these commands will help you get the Remote GUI admin page connected to a Linux-based Transmission pgm, and get past "Host not found" and "connection refused" problems

b?sudo service transmission-daemon startb?

No harm to try this command; will say "already running" if it is. This is the software on the Linux host of Tranmission Rev 2.8x that fields the connection to the remote GUI and gets answers to the GUI's rpc's (Remote Procedure Calls).

LONGER SET OF COMMANDS TO CHECK VITALS

sudo service transmission-daemon stop

transmission-daemon -d

Dump the parameters; Everything you could ever screw up by directly editing the .json file is here. Note the user ("transmission") and a few of the final chars of his hashed password. People who edit "the" .json file sometimes find they massaged the right filename in the wrong folder. That cannot happen to you if you ask the daemon to edit itself.

transmission-daemon -u transTEST -v transTEST transmission-daemon -d

Trust but verify -- look at the dump and be sure the user name and the hash of his pwd have both changed.

transmission-daemon -u transmission -v transmission

Once we connect, there will be no doubt about the verification (user, pwd) needed by the program. Note that this is **not the user/pwd you use to log onto the PC where the transmission torrent pgm runs. **

Now let's fix the connection.

transmission-daemon -a "127.0.0., 192.168.1."

Allow a connection to the transmission client by the remoteGUI running on the same PC, or running on any other PC of the home LAN.

Now click the GUI's upper left-most signals, get dropdown MANAGE CONNECTIONS and add a connection using something in the allowed IP range. Leave TOOLS / APPLICATION (i.e., the gui) / TRANSMISSION alone for now.

I hope this lowers the frustration out there. :

Unlike little appliances like the ReadNAS NV+, Transmission is native to Ubuntu/Kubuntu, so you can get a manual page man transmission-daemon

Repeating some things others have said; A "deeper" way to see that the daemon is really running: ps aux | grep transmission-daemon

ps = process snapshot; aux lists everything; grep filters out the impt data

In order to see if transmission-daemon is receiving commands, you can check for the list of torrents: transmission-remote -n transmission:transmission -l

transmission-remote -h for help above, -n set user name and password; list torrents

--end

[Anonymous]

Originally posted by: jerry...@speakeasy.net

<size=5>FIGHTING "CONNECTION REFUSED" in the REMOTE GUI</size>

Maybe these commands will help you get the Remote GUI admin page connected to a Linux-based Transmission pgm, and get past "Host not found" and "connection refused" problems

sudo service transmission-daemon startb?

No harm to try this command; will say "already running" if it is. This is the software on the Linux host of Tranmission Rev 2.8x that fields the connection to the remote GUI and gets answers to the GUI's rpc's (Remote Procedure Calls).

LONGER SET OF COMMANDS TO CHECK VITALS

sudo service transmission-daemon stop

transmission-daemon -d

Dump the parameters; Everything you could ever screw up by directly editing the .json file is here. Note the user ("transmission") and a few of the final chars of his hashed password. People who edit "the" .json file sometimes find they massaged the right filename in the wrong folder. That cannot happen to you if you ask the daemon to edit itself.

transmission-daemon -u transTEST -v transTEST transmission-daemon -d

Trust but verify -- look at the dump and be sure the user name and the hash of his pwd have both changed.

transmission-daemon -u transmission -v transmission

Once we connect, there will be no doubt about the verification (user, pwd) needed by the program. Note that this is **not the user/pwd you use to log onto the PC where the transmission torrent pgm runs. **

Now let's fix the connection.

transmission-daemon -a "127.0.0., 192.168.1."

Allow a connection to the transmission client by the remoteGUI running on the same PC, or running on any other PC of the home LAN.

Now click the GUI's upper left-most signals, get dropdown MANAGE CONNECTIONS and add a connection using something in the allowed IP range. Leave TOOLS / APPLICATION (i.e., the gui) / TRANSMISSION alone for now.

I hope this lowers the frustration out there. :

Unlike little appliances like the ReadNAS NV+, Transmission is native to Ubuntu/Kubuntu, so you can get a manual page man transmission-daemon

Repeating some things others have said; A "deeper" way to see that the daemon is really running: ps aux | grep transmission-daemon

ps = process snapshot; aux lists everything; grep filters out the impt data

In order to see if transmission-daemon is receiving commands, you can check for the list of torrents: transmission-remote -n transmission:transmission -l

transmission-remote -h for help above, -n set user name and password; list torrents

--end