search

digitie / transmission-remote-dotnet

Automatically exported from code.google.com/p/transmission-remote-dotnet
GNU General Public License v3.0
1 stars 0 forks source link

An exception occurred during Webclient request #269

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Just run transmission-remote-dotnet

What is the expected output? What do you see instead?
This message "An exception occurred during webclient request" appears at
the bottom where the speed is reported

What version of the products are you using?
OS: XP SP3
Transmission: 1.92
Remote: 3.22.1

Version 3.21 does have a similar issue.
Version 3.22 (11 May) did not have an issue.
Night build r591 did not have an issue.

Original issue reported on code.google.com by zyx...@gmail.com on 15 May 2010 at 9:56

GoogleCodeExporter commented 8 years ago 
I am have mistyped the version 3.20 (not 3.21) has a similar issue.

If an error occurs - the only way is to stop transmission-remote-dotnet and 
start it
again. Connecting/disconnecting does not help!

Original comment by zyx...@gmail.com on 15 May 2010 at 10:00

GoogleCodeExporter commented 8 years ago 
Do you still have this problem?

Original comment by 0obeanon...@gmail.com on 13 Jun 2010 at 10:35

GoogleCodeExporter commented 8 years ago 
It happens very rarely. AFAIR I had not this issue for more then 2 weeks with 
transmission 1.93 and a night build r614.

I cannot say for sure, but the last time the issue happened when I was watching 
movie from my NAS running transmission. Everything is ok with my LAN(ethernet, 
static ip both on desktop and NAS) and the cpu load of NAS.

Original comment by zyx...@gmail.com on 14 Jun 2010 at 7:19

GoogleCodeExporter commented 8 years ago 
Ok, i close this issue. If you got this error, pls reopen it, and give some 
debug info (with logrpc version)

Original comment by elso.and...@gmail.com on 15 Jun 2010 at 6:06

GoogleCodeExporter commented 8 years ago 
Happens all the time. Please reopen. Daemon is 2.12.

Original comment by andrebr...@gmail.com on 8 Dec 2010 at 1:52

GoogleCodeExporter commented 8 years ago 
need more info!

Original comment by elso.and...@gmail.com on 15 Dec 2010 at 6:23

GoogleCodeExporter commented 8 years ago 
A friend of mine hit this problem on his XP sp3 machine just today.

The issue turned out to be the setting in transmission for proxy was set to 
enabled by default. He had to manually set it to auto so he could connect as he 
does not have a proxy. I'm sure setting disabled would have also worked by auto 
seems to be the default  normally.

Maybe the wrong default setting only happens on XP machines?

Original comment by kickb...@gmail.com on 20 Dec 2011 at 12:04