In the last revision of transmission, I couldn’t get the user/password for the RPC of transmission work.
To resolve this problem, I decided to use Nginx as reverse proxy to provide an SSL connection and also a way to secure the access to the RPC and the web interface.
I compiled myself transmission and it’s installed in /usr/local/. In case you are using the packaged version of Debian/Ubuntu you need to change the /usr/local/ by /usr/.
Does this config still work? It’s the closest thing to working for me, expect the page doesn’t load properly. The graphics (the menu bar and visuals) do not appear but if I go to the non-ssl link, the graphics load properly.
I’m suspicious of the forward slash inconsistency and wonder if that is the cause?
In fact, you pointed out a mistake in my configuration. For the raspberry pi where I installed transmission, I compiled transmission and didn’t change where to install the package (default /usr/local/) which explain the problem you got.
So this is a bit of a necro post, but this one really helped me figure out how to get my proxy config down perfect. This one has worked for me to solve the tricky 409 conflict as well as allow /transmission and /transmission/ to load to the web interface correctly so I thought I’d share. One note: the t-proxy.conf is just lists the proxy header configs in a separate file, but are the same.
*outside of the server block*
upstream transmission {
server 127.0.0.1:9091;
}
*inside server block*
location /transmission {
include t-proxy.conf;
try_files $uri $uri/;
location /transmission/rpc {
proxy_pass http://transmission;
}
location /transmission/web/ {
proxy_pass http://transmission;
}
location /transmission/upload {
proxy_pass http://transmission;
}
location /transmission/web/style/ {
alias /usr/share/transmission/web/style/;
}
location /transmission/web/javascript/ {
alias /usr/share/transmission/web/javascript/;
}
location /transmission/web/images/ {
alias /usr/share/transmission/web/images/;
}
location /transmission/ {
return 301 https://$server_name/transmission/web;
}
}
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behaviour or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions. Cookies are used for ads personalisation.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
25th October 2015 at 02:33
Does this config still work? It’s the closest thing to working for me, expect the page doesn’t load properly. The graphics (the menu bar and visuals) do not appear but if I go to the non-ssl link, the graphics load properly.
I’m suspicious of the forward slash inconsistency and wonder if that is the cause?
Thanks!
25th October 2015 at 02:44
*shrug* I checked the error log, and it was looking somewhere else for the javascript and style files. I found that the problem was fixed with:
ln -s /usr/share/transmission /usr/local/share/transmission
I guess my transmission build was not configured properly.
25th October 2015 at 03:07
Glad it worked for you.
In fact, you pointed out a mistake in my configuration. For the raspberry pi where I installed transmission, I compiled transmission and didn’t change where to install the package (default /usr/local/) which explain the problem you got.
I’m going to correct this. Thanks for the report.
12th January 2016 at 21:18
So this is a bit of a necro post, but this one really helped me figure out how to get my proxy config down perfect. This one has worked for me to solve the tricky 409 conflict as well as allow /transmission and /transmission/ to load to the web interface correctly so I thought I’d share. One note: the t-proxy.conf is just lists the proxy header configs in a separate file, but are the same.
*outside of the server block*
upstream transmission {
server 127.0.0.1:9091;
}
*inside server block*
location /transmission {
include t-proxy.conf;
try_files $uri $uri/;
location /transmission/rpc {
proxy_pass http://transmission;
}
location /transmission/web/ {
proxy_pass http://transmission;
}
location /transmission/upload {
proxy_pass http://transmission;
}
location /transmission/web/style/ {
alias /usr/share/transmission/web/style/;
}
location /transmission/web/javascript/ {
alias /usr/share/transmission/web/javascript/;
}
location /transmission/web/images/ {
alias /usr/share/transmission/web/images/;
}
location /transmission/ {
return 301 https://$server_name/transmission/web;
}
}