NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
super_poussin
May 17, 2010Virtuoso
New Transmission add-on thread
The previous thread was very long
time to open a new one and prepare the 2.0 :)
time to open a new one and prepare the 2.0 :)
920 Replies
Replies have been turned off for this discussion
- veehexxAspirantwhich link has been updated S-P... 2.01 final or 2.01 beta? (dates against your 'updated' posts arent as new as your response above :))
i'd like to update to 2.01 final, but dont want to face the issues others have experienced recently - super_poussinVirtuosoUse the link in 2.0.1 official
- losgatos_markAspirantHi SP,
last week, for version 1.93, I use the information in the thread
http://readynas.com/forum/viewtopic.php?f=60&t=30580
to manage transmission securely.
This morning I installed 2.01, and I am unable to use the secure connection to log in.
I can log in with:
http://192.168.2.46:8181/transmission/web/
but when I try to use:
https://192.168.3.46/transmission/web/
that was working before the upgrade, I get the user/pwd box and my (same) user / pwd is not accepted...
any clue?
can I roll back to 1.93 for my NVX??
thanks - Mark - gothiAspirant
losgatos_mark wrote:
but when I try to use:
https://192.168.3.46/transmission/web/
that was working before the upgrade, I get the user/pwd box and my (same) user / pwd is not accepted...
any clue?
can I roll back to 1.93 for my NVX??
No need to roll back, it's simply that the new Torrent creation super-poussin added is conflicting with the "securely access anywhere" hack, they both use the alias "Transmission" in Apache.
The easiest fix is to SSH in and edit /etc/frontview/apache/addons/transmissionweb.conf
original (doesn't work with "securely access anywhere" hack):
Alias "/transmission" "/c/webroot/transmission"
<Location "/transmission">
Options Indexes
Order allow,deny
Allow from all
Require user admin
AuthType Basic
AuthName "Transmission"
</Location>
modified (DOES work with "securely access anywhere" hack):
Alias "/createtorrent" "/c/webroot/transmission"
<Location "/createtorrent">
Options Indexes
Order allow,deny
Allow from all
Require user admin
AuthType Basic
AuthName "Torrent creation GUI"
</Location>
After changing the contents of the file save it and restart your Readynas (or restart Apache). Once it's back up and running you should once again be able to access the web interface over HTTPS and the torrent creation gui can now be accessed by going to http://yourNAS/createtorrent/
super-poussin, any chance you could use a different alias for the torrent creation gui? Something like http://yourNAS/createtorrent/ or http://yourNAS/ctransmission/ ?
[edit]
Incidently the username/password required by the torrent creation gui is the same as you use to access the Readynas Frontview admin interface not the username/password you use to access the Transmission web interface. - losgatos_markAspirantThanks Gothi - that did the trick.
- mark - super_poussinVirtuoso
gothi wrote: losgatos_mark wrote:
but when I try to use:
https://192.168.3.46/transmission/web/
that was working before the upgrade, I get the user/pwd box and my (same) user / pwd is not accepted...
any clue?
can I roll back to 1.93 for my NVX??
No need to roll back, it's simply that the new Torrent creation super-poussin added is conflicting with the "securely access anywhere" hack, they both use the alias "Transmission" in Apache.
The easiest fix is to SSH in and edit /etc/frontview/apache/addons/transmissionweb.conf
original (doesn't work with "securely access anywhere" hack):
Alias "/transmission" "/c/webroot/transmission"
<Location "/transmission">
Options Indexes
Order allow,deny
Allow from all
Require user admin
AuthType Basic
AuthName "Transmission"
</Location>
modified (DOES work with "securely access anywhere" hack):
Alias "/createtorrent" "/c/webroot/transmission"
<Location "/createtorrent">
Options Indexes
Order allow,deny
Allow from all
Require user admin
AuthType Basic
AuthName "Torrent creation GUI"
</Location>
After changing the contents of the file save it and restart your Readynas (or restart Apache). Once it's back up and running you should once again be able to access the web interface over HTTPS and the torrent creation gui can now be accessed by going to http://yourNAS/createtorrent/
super-poussin, any chance you could use a different alias for the torrent creation gui? Something like http://yourNAS/createtorrent/ or http://yourNAS/ctransmission/ ?
[edit]
Incidently the username/password required by the torrent creation gui is the same as you use to access the Readynas Frontview admin interface not the username/password you use to access the Transmission web interface.
will do in next version :) - shadow75AspirantHi all, I have some Transmission version discrepancy, and just wondering if this is normal.
On the ReadyNAS frontview, it shows Transmission as v2.01, but when you look under preferences of the Transmission web interface, is shows up as 2.00+ (10809).
Any thoughts?
Thanks,
Glenn - super_poussinVirtuosothey perhaps forget to change the build , let me check when back at home
- veehexxAspirant
shadow75 wrote: Hi all, I have some Transmission version discrepancy, and just wondering if this is normal.
On the ReadyNAS frontview, it shows Transmission as v2.01, but when you look under preferences of the Transmission web interface, is shows up as 2.00+ (10809).
Any thoughts?
Thanks,
Glenn
same as me. (running 2.01 final) - super_poussinVirtuosowill republish the 2.01 today
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!