Release: rTorrent/ruTorrent for unRAID



Recommended Posts

[...]

 

I had a little more time to test it out this week-end, and I'm back to my first issue : autotools works alright, but CP/SR can't extract anything inside the newly created torrent folders... Their permissions are rwxr-xr-x, so any user other than torrents can't write anything inside (even if they belong to the same group). The permission needs to be rwxrwxr-x at least...

 

I am struggling to find a proper fix for this, I do not fully understand how to set mask settings for a user such that all files/directories created by the user "torrent" have 777 permissions.

 

[...]

 

Thanks

 

You would have to use the "umask" command :

http://askubuntu.com/questions/44542/what-is-umask-and-how-does-it-work

http://unixhelp.ed.ac.uk/examples/umask.html

 

A umask 002 should be enough...

 

Thanks again !!

Link to comment
  • Replies 143
  • Created
  • Last Reply

Top Posters In This Topic

Big Update

 

I have made some major changes to how this container has been put together:

 

The Container Template .xml has been updated to reflect the following changes

(I would advise re-clicking "Save" under the "Docker Repositories" tab to ensure you have the latest template .xml)

 

Changes

 

1. Updated  to latest rTorrent (0.9.4) and libtorrent (0.13.4)

 

2. Added BASIC auth security: (.htaccess file is created in the /config folder)

 

    Default username:password is admin:admin

    To change this edit the .htaccess file, convert username:passwords into encrypted format here:

    http://www.htaccesstools.com/htpasswd-generator/

    Follow the instructions; one username:password per line.

    Save file and Restart container

 

3. Added SSL (default https://SERVERIP:8099)

 

      This port can be changed in the Container settings

      The cert is created on container start and creates a generic server.crt in /config/certs

            All info in this generic cert is set to "unraid"

 

      If you want to swap out this cert with your own (advised) then:

      SSH into your unRAID server, navigate to the certs folder where you have mapped /config

      go to this link and follow instructions:

      http://www.akadia.com/services/ssh_test_certificate.html

      Make sure the output file is named server.crt

      Note: This can be done from unRAID itself not within the container

 

      Restart the container after replacing the server.crt

     

4. (Finally!!) Fixed umask of torrent user. umask torrent = 0002

 

 

I really hope people are happy with the changes and enjoy this container.

 

The Capt.

Link to comment

Big Update

 

I have made some major changes to how this container has been put together:

 

The Container Template .xml has been updated to reflect the following changes

(I would advise re-clicking "Save" under the "Docker Repositories" tab to ensure you have the latest template .xml)

 

Changes

 

1. Updated  to latest rTorrent (0.9.4) and libtorrent (0.13.4)

 

2. Added BASIC auth security: (.htaccess file is created in the /config folder)

 

    Default username:password is admin:admin

    To change this edit the .htaccess file, convert username:passwords into encrypted format here:

    http://www.htaccesstools.com/htpasswd-generator/

    Follow the instructions; one username:password per line.

    Save file and Restart container

 

3. Added SSL (default https://SERVERIP:8099)

 

      This port can be changed in the Container settings

      The cert is created on container start and creates a generic server.crt in /config/certs

            All info in this generic cert is set to "unraid"

 

      If you want to swap out this cert with your own (advised) then:

      SSH into your unRAID server, navigate to the certs folder where you have mapped /config

      go to this link and follow instructions:

      http://www.akadia.com/services/ssh_test_certificate.html

      Make sure the output file is named server.crt

      Note: This can be done from unRAID itself not within the container

 

      Restart the container after replacing the server.crt

     

4. (Finally!!) Fixed umask of torrent user. umask torrent = 0002

 

 

I really hope people are happy with the changes and enjoy this container.

 

The Capt.

 

Wow, big update... I'm going to test it right now !!

 

Thanks a lot :)

Link to comment

I have problem with ruTorrent.

When I enter http://IPAddress:8089/ I get error: "404 Not Found, nginx/1.6.2".

If I enter https://IPAddress:8089/ I get error: "SSL connection error", details: "Unable to make a secure connection to the server. This may be a problem with the server, or it may be requiring a client authentication certificate that you don't have. Error code: ERR_SSL_PROTOCOL_ERROR"

 

unRAID version: 6.0-beta14b

 

I re-installed ruTorrent docker many times, but with no luck.

Ports 8089 and 9527 are free and not used for any other app. If I change them, I get the same error.

 

Suggestions?

Link to comment

I have problem with ruTorrent.

When I enter http://IPAddress:8089/ I get error: "404 Not Found, nginx/1.6.2".

If I enter https://IPAddress:8089/ I get error: "SSL connection error", details: "Unable to make a secure connection to the server. This may be a problem with the server, or it may be requiring a client authentication certificate that you don't have. Error code: ERR_SSL_PROTOCOL_ERROR"

 

unRAID version: 6.0-beta14b

 

I re-installed ruTorrent docker many times, but with no luck.

Ports 8089 and 9527 are free and not used for any other app. If I change them, I get the same error.

 

Suggestions?

 

Your not alone.

I too am getting this since yesterdays update.

Link to comment

@JaY_III & @Vaseer

 

Did you set an EDGE variable (ie EDGE=1 or EDGE=0)?

 

does your /config directory have a rutorrent subdirectory?

 

I found a possible bug in the edge script, new version currently building; please report. (new build should be ready 10 mins from time of post now ready)

 

also: SSL only works on https://xxx.xxx.xxx.xxx:8099 (not port 8089, https very important)

Link to comment

I didn't set EDGE (left it empty).

/config directory has rutorrent folder, which contains folders "certs", ".rtorrentsession"; and files ".htpassword", ".rtorrent.rc".

 

I re-installed ruTorrent with EDGE empty and then with set to 0 and get same error. When I set it to 1, http://IPAddress:8089/ is working, but https://IPAddress:8099/ gives me error: "This webpage is not available".

https://IPAddress:8089/ gives me the same error as before: "SSL connection error".

 

I am just guessing, but I think that in my case, SSL "wants" to work in 8089 port and not on 8099.

Link to comment

@sacretagent

Remove and do a clean install.

I had it working a a previos build, but did a clean , not upgrade, install with clean new paths for the 23rd build to current 25th.

I can not get them working.

 

@Capt.Insano

 

"root@localhost:# /usr/bin/docker run -d --name="ruTorrent" --net="bridge" -e EDGE="0" -e TZ="America/New_York" -p 8089:80/tcp -p 8099:443/tcp -p 45566:45566/tcp -p 9527:9527/udp -v "/mnt/user/Docker/rTorrent/":"/config":rw -v "/mnt/user/Docker/Download/":"/download":rw captinsano/rutorrent

 

401796b24d28555630195e8b34760a1bd3a68bdc56ae74e030bd723896dfdae1

 

The command finished successfully!"

 

 

I see " EDGE=0 "

My /config directory does not have a rutorrent subdirectory

It has

.rtorrentsessions (dir)

certs (dir)

.htpasswd

.rtorrent.rc

 

 

Finally I am getting a 404 when attempting HTTP or HTTPS connection after i input the login details.

 

Link to comment

For all with problems:

 

Sorry about this. I think there must be a problem with the edge script. I think it is deleting the /config/rutorrent folder. Meaning that nginx has nothing to serve either on http or https.

 

I will try and recreate the problem after work and look for a fix.

 

Again, sorry about this.

Link to comment

Update perfect,

And i don't lose any of the downloads in progress.

 

Cap.insano i have a question.

 

I have starssl free cert signed.

but I have private key (.key) certicate(.crt) and intermediate cert (sub.class1.server.ca.pem)

 

how I cant convert this to key, crt,csr?

 

 

The other thing I see,

is that the mover don't move downloads, downloaded by your docker.(yes even though it is not uploading on long time)

 

 

Thanks for your amazing job :P

 

Link to comment

New build up

 

ruTorrent directory was not being created for people with EDGE=0.

 

Sorry for delay

 

Please test and report.

 

Thank you, its looking good.

 

Only 1 thing I see you could tweak.

When clicking the blue port mapping text, it uses HTTP for the ssl port map.

it would be nice if you could have the browser open it up as HTTPS://X.X.X.X:8099

but I do not know if that is in your control or not.

Link to comment

What's the problem? Why are there a lot of errors.

 

WzQro1D.png

 

SlTQ5Tu.png

 

Moving ruTorrent into /config
mv: preserving times for '/config/rutorrent/rutorrent': No such file or directory
EDGE variable found
EDGE=1
no prev GIT version detected, cloning
Cloning into '/config/rutorrent'...
error: index-pack died of signal 11
fatal: index-pack failed
rm: cannot remove '/config/rutorrent/conf/config.php': No such file or directory
cp: cannot create regular file '/config/rutorrent/conf/config.php': No such file or directory
chown: cannot access '/config/rutorrent': No such file or directory
rm: cannot remove '/var/www/rutorrent': No such file or directory
Using existing AUTH file.
Using existing SSL Cert.
Using existing config file.
chown: cannot access '/config/rutorrent': No such file or directory
mkdir: cannot create directory '/config/.rtorrentsession': File exists
+ service nginx start
+ service php5-fpm start
+ cd /config
+ exec gosu torrent /rutorrent.sh
+ export HOME=/config
+ HOME=/config
+ cd /config
+ TMUX_BIN=/usr/bin/tmux
+ LOCK_FILE=/download/.rtorrent.lock
+ flock --nonblock --exclusive 9
+ rm -f /config/.rtorrentsession/rtorrent.lock
+ /usr/bin/tmux new-session -d rtorrent
++ /usr/bin/tmux run-shell 'echo $TMUX'
++ cut -d , -f 2
+ TMUX_SERVER_PID=74
+ set +x

Link to comment

I did clean install, set EDGE=1 and http is working, but https gives me the same error as before.

ruTorrent is working, so it is ok, but if https will get fixed it will be even better  ;D

 

Thanks for help.

 

Do you have a file /config/certs/server.key?

 

Check with other browser, clear your cache?

 

What's the problem? Why are there a lot of errors.

 

Moving ruTorrent into /config
mv: preserving times for '/config/rutorrent/rutorrent': No such file or directory
EDGE variable found
EDGE=1
no prev GIT version detected, cloning
Cloning into '/config/rutorrent'...
error: index-pack died of signal 11
fatal: index-pack failed
rm: cannot remove '/config/rutorrent/conf/config.php': No such file or directory
cp: cannot create regular file '/config/rutorrent/conf/config.php': No such file or directory
chown: cannot access '/config/rutorrent': No such file or directory
rm: cannot remove '/var/www/rutorrent': No such file or directory
Using existing AUTH file.
Using existing SSL Cert.
Using existing config file.
chown: cannot access '/config/rutorrent': No such file or directory
mkdir: cannot create directory '/config/.rtorrentsession': File exists
+ service nginx start
+ service php5-fpm start
+ cd /config
+ exec gosu torrent /rutorrent.sh
+ export HOME=/config
+ HOME=/config
+ cd /config
+ TMUX_BIN=/usr/bin/tmux
+ LOCK_FILE=/download/.rtorrent.lock
+ flock --nonblock --exclusive 9
+ rm -f /config/.rtorrentsession/rtorrent.lock
+ /usr/bin/tmux new-session -d rtorrent
++ /usr/bin/tmux run-shell 'echo $TMUX'
++ cut -d , -f 2
+ TMUX_SERVER_PID=74
+ set +x

 

Have you done a CLEAN install (remove all prev config)? I have never had any of those errors.

 

It looks like git is failing due to a set fault and even mv is giving errors. Are you running docker in a standard btfs docker.IMG?

Link to comment

I have not been able to repeat any of those errors on a completely fresh install (all config files removed) both with EDGE=0 or EDGE=1.

 

Is there anything special about your setup?

Eg: Is /config mounted to non cache/array device eg. SNAP device  ?

 

Anyone else seeing these errors?

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.