[HELP] The WEBUI Control

[aleale97]

Hi for everyone. I'm italian and i don't write english very well. When i connect a broswere to the ip address of my server i see this:

Code: Select all

403: Forbidden

Unauthorized IP Address.

Either disable the IP address whitelist or add your address to it.

If you're editing settings.json, see the 'rpc-whitelist' and 'rpc-whitelist-enabled' entries.

If you're still using ACLs, use a whitelist instead. See the transmission-daemon manpage for details.

I am not a expert and I do not know how to do. Can you help me? Thx

[rb07]

Like the message says, you have 2 choices:

• Start the daemon using the --allowed parameter (-a is the short form):

  Code: Select all

  transmission-remote -a 192.168.1.*,127.0.0.1

• Or find where the daemon has its settings.json file, and edit the 2 lines mentioned in the message:

  Code: Select all

      "rpc-whitelist": "127.0.0.1,192.168.1.*", 
      "rpc-whitelist-enabled": true, 
  

• A third choice is like the second, but just disable the whitelist; everybody will have access (but authentication can still be used).

In the examples I used 192.168.1.* as the LAN address, usually written as 192.168.1.0/24; you'll have to use your own LAN's address.

Depending on your installation, the parameters for the first choice could be in a parameters file (usually in /etc/conf.d/transmission or transmission-daemon), or in the startup script (usually in /etc/init.d/. . .)

[aleale97]

I have changed the "rpc-whitelist-enabled" from yes to false and i have rebooted the pc. but nothing it's changed, i saw the same screen as before. Help me please

[rb07]

I see one problem: you changed the file when the daemon was running. . . that doesn't work. You have to tell the daemon it was changed (sending a HUP signal) or stop the daemon, change the file, then start the daemon. Rebooting is a bad idea, the daemon writes its current setting to the file when it is stopped (loosing your changes).

Another possibility is if both methods of setting the whitelist feature are used, I think the parameter to the daemon wins. This means that if your installation is using some default parameters for the daemon, whatever you write in settings.json will be overridden.

[aleale97]

How can i stop the deamon of trasmission? THX

[rb07]

That depends on what operating system are you using.

Some examples (from memory, so they are probably not accurate):

Red Hat Linux and probably CentOS -

Code: Select all

service transmission stop

Gentoo Linux and just about any Linux -

Code: Select all

/etc/init.d/transmission stop
or /etc/init.d/transmission-daemon stop

[aleale97]

Oh, thx!
But i have another reques
how can I set the directory to upload torrent?
Another thx! Alessandro

[rb07]

You mean using the Web client?

That could be a 2 step procedure:

• 1. Preferences -> General : Download to: <change to the directory you want to use>
• 2. Upload the .torrent file

The directory will stay as default for all new torrents (doesn't matter if it is upload or download).

With the terminal tool its a little bit easier, one step: transmission-remote --add <whatever>.torrent --download-dir <directory> ... other options like seed ratio limit, speed limits, etc.

[lazybones]

If you are in the same network as the transmission daemon you might just want to look at some of the front end GUI apps like http://code.google.com/p/transmisson-remote-gui/ . They act mostly like a normal torrent client would on your workstations but all the work is done on the box running the daemon.

[aleale97]

No. You misunderstood.
when i don't have a torrent in download, i use a directory by give the torrent(or multiple torrent) to daemon.
HElp please
Alessandro

[rb07]

No. You misunderstood.

Who is "you"?

when i don't have a torrent in download, i use a directory by give the torrent(or multiple torrent) to daemon.

There is no such thing as "giving a torrent to the daemon"... if you are the seeder, you put the files you want to seed wherever you want where the daemon has access, then you load the .torrent file you created to describe your torrent telling the daemon where you placed the actual files (the 2 steps, first I tell the daemon where to look for things, then I load the .torrent).

When the daemon sees that you already have the files, it will only make a verification and start seeding.