I followed again and again the trac https://trac.transmissionbt.com/wiki/WebProxy and the forum viewtopic.php?f=8&t=6133&start=15
But I must be seriously retarded I cannot figure out how to make the web interface working on https.
Seems transmission webinterface only work with http is there any way to be able to access the webinterface and encrypte the password session with https ?
Could be usefull when using transmission from cybercafe/macdo/school/work.
If you got idea I thank you very much.
Connect webinterface via https
Re: Connect webinterface via https
Looking at the other thread, and the Wiki, I see something missing: the https configuration is in a different file.
In other words, if you already have a http proxy working, you have to do the same changes in configuration to the https configuration. How do you know which one is http/https? Easy, the one that has "<VirtualHost *:80>" is http, the one that has "<VirtualHost *:443>" is https.
In other words, if you already have a http proxy working, you have to do the same changes in configuration to the https configuration. How do you know which one is http/https? Easy, the one that has "<VirtualHost *:80>" is http, the one that has "<VirtualHost *:443>" is https.
Re: Connect webinterface via https
Gosh thanks. Seems 2.02 fixed the problem for me 
Yea I was using the default-ssl site
Between
<IfModule mod_ssl.c>
<VirtualHost _default_:443>
# Redirect requests to /transmission to /transmission/web
RewriteRule /transmission[/]?$ /transmission/web [R=permanent]
# Forward all requests for /transmission to transmission-daemon
ProxyPass /transmission https://127.0.0.1:9091/transmission
ProxyPassReverse /transmission https://127.0.0.1:9091/transmission
<Location /transmission>
Order Allow,Deny
Allow from All
</Location>
</VirtualHost>
</IfModule>
By the way since the website was using
<VirtualHost *:80>
RewriteEngine on
RewriteCond %{SERVER_PORT} ^80$
RewriteRule ^(.*)$ https://%{SERVER_NAME}$1 [L,R]
RewriteLog "/var/log/apache2/rewrite.log"
RewriteLogLevel 2
...
Maybe it was that making trouble too. Don't know how or why but it works with version 2.02 Great job the dev team.
Yea I was using the default-ssl site
Between
<IfModule mod_ssl.c>
<VirtualHost _default_:443>
# Redirect requests to /transmission to /transmission/web
RewriteRule /transmission[/]?$ /transmission/web [R=permanent]
# Forward all requests for /transmission to transmission-daemon
ProxyPass /transmission https://127.0.0.1:9091/transmission
ProxyPassReverse /transmission https://127.0.0.1:9091/transmission
<Location /transmission>
Order Allow,Deny
Allow from All
</Location>
</VirtualHost>
</IfModule>
By the way since the website was using
<VirtualHost *:80>
RewriteEngine on
RewriteCond %{SERVER_PORT} ^80$
RewriteRule ^(.*)$ https://%{SERVER_NAME}$1 [L,R]
RewriteLog "/var/log/apache2/rewrite.log"
RewriteLogLevel 2
...
Maybe it was that making trouble too. Don't know how or why but it works with version 2.02
Great job the dev team.Re: Connect webinterface via https
Dam infact no.
I may have enter the pass used with transmission-rpc just before on port :9091 that's why it worked.
But now if I don't have already entered the password on port :9091 it won't let me enter saying :
409: Conflict
Your request had an invalid session-id header.
To fix this, follow these steps:
1. When reading a response, get its X-Transmission-Session-Id header and remember it
2. Add the updated header to your outgoing requests
3. When you get this 409 error message, resend your request with the updated header
This requirement has been added to help prevent CSRF attacks.
X-Transmission-Session-Id: otWwqNDL12uUJN5j71gXnJDcLdJVxVOyF3TOwEjWANTR2RMZ
I may have enter the pass used with transmission-rpc just before on port :9091 that's why it worked.
But now if I don't have already entered the password on port :9091 it won't let me enter saying :
409: Conflict
Your request had an invalid session-id header.
To fix this, follow these steps:
1. When reading a response, get its X-Transmission-Session-Id header and remember it
2. Add the updated header to your outgoing requests
3. When you get this 409 error message, resend your request with the updated header
This requirement has been added to help prevent CSRF attacks.
X-Transmission-Session-Id: otWwqNDL12uUJN5j71gXnJDcLdJVxVOyF3TOwEjWANTR2RMZ