Transmission 3.0
Transmission 3.0
Transmission 3.0 does not support SSL why ? When I have enabled on the Tracker SSL website I get the error Announce error: Could not connect to tracker, transmission installed on qnap TS-231P, I need to disable the torrent SSL page and then the transmission connects to the tracker.
Re: Transmission 3.0
Transmission is using cURL library to make HTTP requests to trackers. As long as that library is built with SSL support (and potentially against an SSL library that supports a particular SSL/TLS version in use by the tracker), Transmission itself supports SSL.
Re: Transmission 3.0
So what should I do ? qnap supports up to TLS version 1.2
Re: Transmission 3.0
Hi @Adis1984,
QNAP forgot to include the SSL CA Certificates in the curl configuration. That is why Transmission (here: the QTransmission 3.0 package) cannot establish an SSL encrypted connection to a BT Tracker.
I added QNAPs local certificate store to the curl configuration and restarted Transmission. Works here now.
How To:
1. Use an SSH/SCP tool and log into your NAS as admin.
2. Find and edit the QNAP qpkg startup script of QTransmission3. It is normally located here:
/share/CACHEDEV[X]_DATA/.qpkg/QTransmission3/QTransmission3.sh
where [X] is the disk volume where you have installed the QNAP App QTransmission3.
3. Add the line: export CURL_CA=/etc/ssl/certs to the other exports and
4. restart QTransmission3.
Regards,
buggy82
QNAP forgot to include the SSL CA Certificates in the curl configuration. That is why Transmission (here: the QTransmission 3.0 package) cannot establish an SSL encrypted connection to a BT Tracker.
I added QNAPs local certificate store to the curl configuration and restarted Transmission. Works here now.
How To:
1. Use an SSH/SCP tool and log into your NAS as admin.
2. Find and edit the QNAP qpkg startup script of QTransmission3. It is normally located here:
/share/CACHEDEV[X]_DATA/.qpkg/QTransmission3/QTransmission3.sh
where [X] is the disk volume where you have installed the QNAP App QTransmission3.
3. Add the line: export CURL_CA=/etc/ssl/certs to the other exports and
4. restart QTransmission3.
Regards,
buggy82
Re: Transmission 3.0
Hi buggy82
Where should I paste this ruler? export CURL_CA=/etc/ssl/certs ?
#!/bin/sh
CONF=/etc/config/qpkg.conf
QPKG_NAME="QTransmission3"
QPKG_ROOT=`/sbin/getcfg $QPKG_NAME Install_Path -f ${CONF}`
export QNAP_QPKG=$QPKG_NAME
export QPKG_ROOT QPKG_NAME
export HOME=$QPKG_ROOT
export SHELL=/bin/sh
export LC_ALL=en_US.UTF-8
export USER=admin
export LANG=en_US.UTF-8
export LC_CTYPE=en_US.UTF-8
export PIDF=/var/run/transmissionbt.pid
killall -9 transmission-daemon
case "$1" in
start)
ENABLED=$(/sbin/getcfg $QPKG_NAME Enable -u -d FALSE -f $CONF)
if [ "$ENABLED" != "TRUE" ]; then
echo "$QPKG_NAME is disabled."
exit 1
fi
/bin/ln -sf $QPKG_ROOT /opt/$QPKG_NAME
cd $QPKG_ROOT/bin
./transmission-daemon --config-dir $QPKG_ROOT/etc &
echo $! > $PIDF
;;
stop)
ID=$(more /var/run/transmissionbt.pid)
if [ -e $PIDF ]; then
kill -9 $ID
rm -f $PIDF
fi
killall -9 transmission-daemon
rm -rf /opt/$QPKG_NAME
;;
restart)
$0 stop
$0 start
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac
exit 0
Where should I paste this ruler? export CURL_CA=/etc/ssl/certs ?
#!/bin/sh
CONF=/etc/config/qpkg.conf
QPKG_NAME="QTransmission3"
QPKG_ROOT=`/sbin/getcfg $QPKG_NAME Install_Path -f ${CONF}`
export QNAP_QPKG=$QPKG_NAME
export QPKG_ROOT QPKG_NAME
export HOME=$QPKG_ROOT
export SHELL=/bin/sh
export LC_ALL=en_US.UTF-8
export USER=admin
export LANG=en_US.UTF-8
export LC_CTYPE=en_US.UTF-8
export PIDF=/var/run/transmissionbt.pid
killall -9 transmission-daemon
case "$1" in
start)
ENABLED=$(/sbin/getcfg $QPKG_NAME Enable -u -d FALSE -f $CONF)
if [ "$ENABLED" != "TRUE" ]; then
echo "$QPKG_NAME is disabled."
exit 1
fi
/bin/ln -sf $QPKG_ROOT /opt/$QPKG_NAME
cd $QPKG_ROOT/bin
./transmission-daemon --config-dir $QPKG_ROOT/etc &
echo $! > $PIDF
;;
stop)
ID=$(more /var/run/transmissionbt.pid)
if [ -e $PIDF ]; then
kill -9 $ID
rm -f $PIDF
fi
killall -9 transmission-daemon
rm -rf /opt/$QPKG_NAME
;;
restart)
$0 stop
$0 start
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac
exit 0
Re: Transmission 3.0
Hi @Adis1984,
guess you have already found out. I always put it somewhere to the other exports.
It is just a configuration that has to be set before the binary is executed.
buggy82
guess you have already found out. I always put it somewhere to the other exports.
It is just a configuration that has to be set before the binary is executed.
buggy82
Re: Transmission 3.0
Hi @buggy82,
Thanks for the guide, but I'm still unable to connect to trackers that require SSL (never had the issue in Transmission 2.92). I added the export to the script and restarted but still no luck. Was there anything else I had to do with the curl config specifically? Any advice would be much appreciated.
TIA, bubbl07
Thanks for the guide, but I'm still unable to connect to trackers that require SSL (never had the issue in Transmission 2.92). I added the export to the script
Code: Select all
export SHELL=/bin/sh
export CURL_CA=/etc/ssl/certs
export LC_ALL=en_US.UTF-8
TIA, bubbl07
Re: Transmission 3.0
Finally I found a solution:
You must install the packages:
https://forum.qnap.com/viewtopic.php?t=117049
You must install the packages:
- Qperl
- CACert
https://forum.qnap.com/viewtopic.php?t=117049
Re: Transmission 3.0
Yes! This did it, thank you!Luiso wrote: ↑Tue Jul 21, 2020 7:11 am Finally I found a solution:
You must install the packages:
- Qperl
- CACert
https://forum.qnap.com/viewtopic.php?t=117049
Re: Transmission 3.0
any suggestions for a fix when you're stuck on a 32-bit OS (Qnap TS-431P-US) and cannot install Qperl (requires 64-bit), and trying the export CURL_CA=/etc/ssl/certs suggestion above, restarting transmission3, doesn't seem to be doing the trick?
edit : updating my post with the solution found here which worked for me : https://forum.qnap.com/viewtopic.php?p=798783#p798783
edit : updating my post with the solution found here which worked for me : https://forum.qnap.com/viewtopic.php?p=798783#p798783
-
- Posts: 1
- Joined: Mon Mar 01, 2021 7:08 pm
Re: Transmission 3.0
Any solution for Mac users using Transmission 3.0? I have a temporary solution that involves setting and overriding `TR_CURL_SSL_NO_VERIFY=1` as an env variable, and this allows me to temporarily connect to trackers using HTTPS. However after a few hours, Transmission seems to forget this env setting and reloads its default (which tries to verify the SSL cert). This seems to occur mostly on trackers using certs from LetsEncrypt.
Is the only recourse to downgrade to Transmission 2.9.2, or is there a release coming up that will fix this?
Is the only recourse to downgrade to Transmission 2.9.2, or is there a release coming up that will fix this?