NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
utorrent for X86 2.2.01
Tested on Ultra and Pro :P
Utorrent for x86 2.2.01
Utorrent for x86 2.0.00
Utorrent for x86 1.8.0
- Super-Poussin changes:
- Now you can access logs in /c/addons-config/utorrent/ :)
- Now you can acces documentation in /c/addons-config/utorrent/docs
- Now you can edit configuration in /c/addons-config/utorrent/utserver.conf (Use interface it's more easy, and do not forget to stop utorrent before doing changes
•HTTPS trackers are unsupportedVersion 3.0 alpha (build 22789)
- Added fields to the About box in the web UI to present the external IP address and UDP/TCP ports assigned by a UPnP router to the server
- Added speculative fix for crash on POSIX platforms occurring when any configurable directories (e.g., active, completed, temporary, autoload, request) contain Unicode characters
- Fixed documentation by changing feed_id to feed-id in two places
µTorrent Server 3.0 alpha build 22708 (for Linux)
- Added daemon argument which directs the server to run in its own
process group- Added usage argument which directs the server to display the set of
valid command-line arguments before exiting - server also prints error
and usage messages before exiting if it detects at least one
unrecognized command-line argument- Added settings finish_cmd and state_cmd to provide a way to invoke
asynchronous processes for torrent lifecycle events- The add torrent dialog in the web UI now allows the user to choose
which download directory to use for the torrent being added- Correct JSON output is now generated for the list-dirs action request
- The name of the directory created by extracting the product archive now
includes utorrent instead of bittorrent- Removed ul_slots_per_torrent setting since it no longer has a function
- Added ut_webui_dir setting in the configuration file, which specifies
the directory containing the webui.zip archive or the unarchived files
to be served for the web UI- Added pidfile argument which permits the specification of a file to be
created by the utserver process which will contain the ID of the
utserver process- Added logmask setting in the configuration file which permits logging
to be configured (and subsequently modified as part of handling a
hangup signal), and removed support for LOGMASK environment variable- The server rereads the configuration file upon receipt of a hangup
signal or when creating or moving a file named rcf.utmr in the
dir_request directory - see the cautions in the user manual about
sending a hangup signal when attempting to change the value of
dir_request- Added settings admin_name and admin_password to allow administrators to
define initial non-default credentials for authenticating to the server
via the HTTP interface- Fixed documentation by changing filter_id to filter-id in one place
- 2010-09-13: Version 3.0 alpha (build 21886)
- Ensure alternative listening port setting persists when changed via web
UI
- Include changes list in docs directory of product archive
- Add mention of configfile and settingspath command-line arguments,
rearrange content of Getting Started section of user manual
- Support configfile argument to specify configuration file location
- Disable BEP22 DNS support on POSIX platforms
- Include plain text version of the user manual in docs directory of
product archive
- Include a EULA file in the docs directory of the archive
- Change default log file for logfile argument to utserver.log
- Fix documentation error saying to use forward slash (/) to precede a
command-line argument keyword - should use a dash (-) on POSIX systems
1.2 solve installation issue and some start issue
gui is on port 8080
user is admin without password
please configure it before adding torrent (where to save files .... (/c/media/BitTorrent/ is a good choice))
also enable ipfilter.dat in advanced option (the addon update ipfilter.dat each day)
243 Replies
Replies have been turned off for this discussion
- Hi -
I installed uTorrent last night. Brought up the GUI, set the username & pwd, set some file locations..and re-logged in with the new username & pwd.
Then I tried to add a torrent, and...nothing. Stopped and restarted and noted that the username & pwd was reset to admin & blank.
None of the new file location directories were created.
I'm guessing this is a permissions thing - do I need to SSH into the nas and do a chmod on something??
thx - Mark - Ah! I was just exchanging emails with S-P on this yesterday...
losgatos_mark wrote:
Then I tried to add a torrent, and...nothing. Stopped and restarted and noted that the username & pwd was reset to admin & blank.
None of the new file location directories were created.
When you say "username & pwd was reset to admin & blank" you mean in the GUI? If so - that's normal, uTorrent never shows the password.
The issue you're hitting is that S-P has configured the server to run as nobody:nogroup - which is the most secure option. But it means that for the server to create and modify files/directories, then the everyone permissions must be set to allow write access to the required location.
To test, you could SSH in and perform a "chmod 777" on the parent folder of where you want your utorrent folders to be, and also on any existing subdirectories you wish to use.
To fix this going forward, I believe S-P is looking at the option of creating a specific user for uTorrent to run as, that way you could add that user to a relevant group and give write access that way. Or even specific access to a share. - The username and password were reset to the default upon adding a torrent.
I'll muck with the permissions on the uTorrent folders this evening and report back.
thanks - Mark losgatos_mark wrote: The username and password were reset to the default upon adding a torrent.
Possible user error? Here's how my settings look and I've changed the password successfully:
All settings get saved in /usr/local/utorrent/settings.dat - you can check permissions just in case; should be owned by "nobody:nogroup"- a quick follow up - logging in via SSH to chmod 777 the directories I specified worked fine...thanks - Mark
- new version is out see top post
- updated to 1.6
- updated
- updated
enjoy - I installed on my ultra 4 and click on launch i get a window saying 404 not found
I also tried the gui access and i am getting the same.
Help please !!!!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
