Closed fbartels closed 11 years ago
You mean that you have a lighthttpd that makes a reverse proxy to transmission web ui ?
Hi,
yes this is what I wanted to say. I already did a Google search if there is a way to import such self signed certificates but wasnt very successful with it. It already works with the the normal web ui but not with your extension.
Thanks for your help.
Looking at the libsoup documentation it seems that soup should accept all ssl certificates by default.
To see the actual error you may change the line 242 to:
...
default:
error = message.response_body.data;
break;
...
Hi, I did a Guthub checkout (was using the version from extension.gnome.org before) and changed
error = _("Can't connect to Transmission"); to error = message.response_body.data; in the extension.js file
With this he now stays at "connecting ..."
Ok I don't know what's happening. I'll have to try your setup and see if I can reproduce.
I have fixed this issue, but not commited yet
My test setup is : https://server <- proxy -> http://127.0.0.1:9091 So in the extension configuration my hostname is 'server' and port 443
Is this how you tried to setup the extension ?
Thanks
Hi, thanks for still having this in your mind. Yes this is how I have set it up.
Ok, should work with this commit :)
Hi,
it may be a more general question but I try my luck here anyways. I am using Transmission over Lighttpd as a proxy to have the communication encrypted via ssl. The extension just reports this connection as "cant connect".
Instead there should be a message about the certificate maybe with a howto on how to import the cerfiticate.
Regards