search

Sevenfourforty / transmission-remote-dotnet

Automatically exported from code.google.com/p/transmission-remote-dotnet
0 stars 0 forks source link

No connection. Error message "The underlying connection was closed : An unexpected error occured on a receive" #149

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
1. Whenever I try to connect, the error message
"The underlying connection was closed : An unexpected error occured on a
receive" appears in a window.

I'm using V3.12 Build 3599 on a Windows7 PC.
I had no problems on a XP machine.

Original issue reported on code.google.com by jlehmb...@gmail.com on 11 Dec 2009 at 11:20

GoogleCodeExporter commented 8 years ago 
I had the same issue and then tried to turn off "Secure (SSL)". It seems like
Transmission does not support that (yet?) or is not configured for it.

Original comment by zzzspamg...@albis.nu on 14 Dec 2009 at 5:32

GoogleCodeExporter commented 8 years ago 
Ah, of course.. No Transmission doesn't support SSL, but it's fairly easy to get
secure communication with Transmission by using stunnel, or I use Apache proxy.

I can see how it could appear as an option whether you've set this up or not, 
though.
I might add some kind of hint ;)

Original comment by AlanF...@googlemail.com on 15 Dec 2009 at 9:46

GoogleCodeExporter commented 8 years ago 
Could you please test with this binary?
http://filebin.ca/yyedym/TransmissionRemote.exe

Original comment by elso.and...@gmail.com on 15 Dec 2009 at 12:06

GoogleCodeExporter commented 8 years ago

Original comment by AlanF...@googlemail.com on 26 Dec 2009 at 11:27

GoogleCodeExporter commented 8 years ago 
Thank you!

Original comment by jlehmb...@gmail.com on 5 Jan 2010 at 1:51

GoogleCodeExporter commented 8 years ago 
I think i not commited this, because i cant fully test.

Original comment by elso.and...@gmail.com on 5 Jan 2010 at 5:15

GoogleCodeExporter commented 8 years ago

Original comment by elso.and...@gmail.com on 23 Jan 2010 at 10:43

GoogleCodeExporter commented 8 years ago 
Ping. Works with that binary?

Original comment by elso.and...@gmail.com on 7 Feb 2010 at 11:46

GoogleCodeExporter commented 8 years ago 
This still is not working.  I have tried with stunnel on the daemon end, and it 
starts 
working but fails.  It actually asks for username+password, which is good and 
means the 
basic ssl channel is open.  But then it immediately fails with:

"The request was aborted.  The request was canceled"

Original comment by reardo...@gmail.com on 16 Mar 2010 at 10:57

GoogleCodeExporter commented 8 years ago 
Do you use apache proxy, or you access to T direct? If apache proxy, have you 
ssl or 
simple http? What do you set "Secure (SSL)" in TRD? What is the port?

Original comment by elso.and...@gmail.com on 16 Mar 2010 at 11:56

GoogleCodeExporter commented 8 years ago 
I use stunnel, but I have also used apache (as proxy).  I can access the 
transmission 
web server perfectly well: 

https://(myserver.address.com):9091/transmission/web/

works fine.  But when I setup TRD to use the same server with SSL over port 
9091 it 
fails.

Original comment by reardo...@gmail.com on 17 Mar 2010 at 3:59

GoogleCodeExporter commented 8 years ago 
I experience the same problem except that I actually can connect initially, 
even do some work with torrents, add-remove-pause, etc, and all of a sudden 
abovementioned problem occurs. 
From this point, nothing helps to get the connection back, even though web 
interface works perfect.
Restarting both device and router helps, so I actually think this is some kind 
of problem at transport level and not a Transmission-Gui bug.

Original comment by megasupe...@gmail.com on 13 Mar 2012 at 3:10