Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
FunFiler
thanks but my question was different, sorry about that
i mean this
rename downloaded file and continue to seeding it
OR
set names to downloading files at the moment of adding torrent file?
Offline
Hi~
I have a question. 2.04 installed, well done, but private torrent is not work and some open torrent files.
Can you help me out?
Offline
Torres wrote:
Hi~
I have a question. 2.04 installed, well done, but private torrent is not work and some open torrent files.
Can you help me out?
Private torrents works fine for me, just make sure the site actully supports transmission and v2.04.
Offline
Hi, Kylek. Thanks for making Transmission available, and for all the updates and support. I have personally benefited from it for more than year.
I have newly installed Transmission 2.04 from 2.03, of course, always following your guide above. When I restarted Transmission, it won't start... and when I looked into the transmission-daemon.log file, I found only one line:
[21:20:06.824] transmission-daemon Error loading config file -- exiting. (daemon.c:421)
When I went on investigating the .transmission-daemon folder, I found it is missing the "settings.json" configuration file. All the other files and folders, namely: /blocklists, /resume, /torrents, dht.dat, stats.json. Are all present.
Is there a way for me to setup a new settings configuration file?
BTW, all the torrents that were loaded have finished downloading, so there are no pending ones.
Thank you.
Offline
Sounds like it is a permission problem.
Offline
@banquer:
First try changing permission of all the files and folders in .transmission-daemon:
$ chown -R nobody:501 /mnt/HD_a2/.transmission-daemon $ find /mnt/HD_a2/.transmission-daemon -type f -print0 | xargs -0 chmod 600 --
If Transmission still won't start, delete (or better rename) the folder, and start from scratch (i.e. Post #1
Offline
KyleK wrote:
@banquer:
First try changing permission of all the files and folders in .transmission-daemon:Code:
$ chown -R nobody:501 /mnt/HD_a2/.transmission-daemon $ find /mnt/HD_a2/.transmission-daemon -type f -print0 | xargs -0 chmod 600 --If Transmission still won't start, delete (or better rename) the folder, and start from scratch (i.e. Post #1
Hi, Kylek. Thanks again for the help. It worked!!!
Actually, I have to do the second part of your directions, i.e. delete the folder altogether and start from scratch.
Thanks again!!!
Offline
Hi Kylek.
How do I set transmission to ask for user name and password when accessing it via the web gui?
I tried
"rpc-authentication-required": true,
"rpc-enabled": true,
"rpc-password": "yourpass",
"rpc-username": "yourusername",
but it still won't work. It also messed up transmission having me to resort to reinstalling it
Offline
That should be it. Don't forget to adjust the whitelist to include your LANs IP range.
How did it mess up your Transmission?
Offline
On my first try, it asked for authentication but would accept the user/pass I entered when accessed via gui. I then erased and brought the settings to the previous state. I repeated the steps above and after erasing the long password string and putting my own password, this time, transmission wouldn't start.
I had to move the json file and restart from scratch. I'll try again. On my whitelist, i have 192.168.1.*.
should the password start with { ?
Thanks again
Offline
You can write a clear password in settings.json. Next time Transmission starts it'll encipher it.
Offline
It worked now ..for a while.
After working, I stopped transmission and edited the json file again to change to a different password. Now it had a long string and not the password I set initially
Last edited by beefy314 (2010-10-07 01:07:55)
Offline
The 'long string' is your password after it has been encoded. Passwords are originally entered in plain text, but for security, they are encoded and re-saved to the file so that they are not "readable" but they are still valid.
Last edited by FunFiler (2010-10-07 02:48:00)
Offline
Oh I see..
I now disabled the whitelist but left the authentication enabled so i can access it from public places with wifi however, it doesn't seem to connect to transmission.
Am I missing something?
update: Seems to be working now. Thanks for the help
Last edited by beefy314 (2010-10-07 01:29:08)
Offline
Don't disable the whitelist.
Offline
Can I still connect to Transmission using different IPs without disabling the whitelist?
Offline
you have to put all Ip adresses, you want to connect from, in the settings.json -> line : "rpc-whitelist".
After that, even with the rpc-whitelist enables, you will connect to transmission.
Offline
Problem is, I get different IP address whenever I connect so I cant specify everything on the rpc-whitelist. What problem will I encounter if I disable the whitelist, but enable the authentication? Will I get hacked easily?
Offline
I don't think any hacker will try to get your ip + your rpc-port + decrypt your authentication just for personals data like movies or photos. It's not a great challenge for him. Sure, I can be wrong...
Offline
I have a question, I saw earlier in the thread a similar issue but it was not resolved as far as I could tell.
I have transmission 2.04 running and it's working great. The one issue is that in the "downloads" folder an the ".transmission-daemon" folders I cannot delete files.
I can copy files in that folder and move them to another folder..but I cannot delete. The only way to delete torrents is to do it through Transmission.
Normally, that's fine. But today I deleted a torrent and forgot to opt for deleting the torrent AND its data..
So now I have a few downloads and no way of getting rid of them other than through commandline..
Isn't setting the permissions to nobody supposed to allow me to delete files owned by nobody?
Offline
I saw Transmission 2.10 is out. I'm currently running 2.03 since 2.04 didn't seem to be a significant improvement. The new version, however, is very interesting.
Offline
Check it out guys, someone just updated the first post with the brand-new package of Transmission v2.10!
I wonder who that was...
Enjoy.
Disclaimer: Didn't have too much time to test this one, let me know if it reformatted your drives or something
Offline
Thanks KyleK, installing it now.
From the Release Notes:
Transmission 2.10 (2010/10/8)¶
All Platforms¶
•Support for automatically stopping idle seeding torrents
•Small memory cache to reduce disk IO
•gzip compression support added to the RPC server
•Add support for a cookies.txt file
•Minor CPU optimizations
Mac¶
•Display file sizes and speeds in base 10 on Snow Leopard
GTK+¶
•Files and folders can be opened by clicking on them in the files list
•Update the interface when session changes are made via RPC
•Fix the Details dialog to fit on a netbook screen
Qt¶
•Tracker announce list editing
•New filterbar
•Improved display for showing a torrent's tracker announces
•Better DBUS integration
•Support adding torrents via drag-and-drop
•Add Desktop Notification for added/complete torrents
•Other minor improvements
Web Client¶
•Peer list added to the inspector
•Compact view mode
•Support filtering by active and finished
•Support sorting by size
Daemon¶
•Allow the .pidfile location to be set in settings.json
Utils¶
•New command-line utility "transmission-edit" for editing torrent files
•New command-line utility "transmission-show" for viewing torrent files
•New command-line utility "transmission-create" for creating torrent files
Last edited by FunFiler (2010-10-12 01:31:43)
Offline
That was fast, Kylek. Thank you. Installed it and so far so good.
+1 for including in the build the CLIs to create/show/edit torrents.
Offline
does someone know what these new settings below found in setting.json mean ?
"idle-seeding-limit": 30,
"idle-seeding-limit-enabled": false,
thanks
Offline