connection error (socketexception:unexpected end of file from server)

[pocketlama]

This is one of 2 errors I'm getting. All my torrents that are seeding and one that I'm trying to download are having one or the other of these problems:

-connection error (socketexception:unexpected end of file from server)
-scrap error: unexpected end of file from server(IO)

Here's from my Help>About:
Java 1.7.0_10
 Oracle Corporation
SWT v4233, win32
Windows 7 v6.1, x86
V5.3.0.0/4 az3

Centurylink wireless connection

I downloaded uTorrent and had no problem downloading a file from the same web site.
 

[GaryE]

Well if you are using a torrent program you are not downloading data from a website you are downloading it from a peer (or more usually many peers).  But that is neither here nor there.

What kind of site is it?

Is it a private site or is it a public site (like The Pirate Bay)?

If the site is a true private site the fact that you can download with another torrent client is usefull information.  Just to be clear sites like demonoid are not private sites Demonoid is an invite only public site.  If the site is a public site .  . . it is compeletly irravelent that you can download with another client.

The reason I ask is that those errors usually indicate a problem with the tracker.  However, since public sites allow any number of trackers in their .torrent files . . . it might just be one tracker which is experiening problems which for some random reason all of your other torrents are using.  But the .torrent file you downloaded and opened with uTorrent might have a differnet tracker or set of trackers or is might just not have the problem tracker in it.

Once you sucessfully downloaded the data using uTorrent did you check if you were still getting those errors in Vuze?  It is possible (but unlikely) that the torrent-tracker problem was solved while you were downloading uTorrent and grabbing the .torrent file which worked correctly.

It could be a wierd traffic shaping problem.  Have you checked to see which port Vuze is using and which port(s) uTorrent are using?  If for example you are using a standard port for Vuze which your ISP is blocking it is vaguly possible that could cause that error (but I seriousl doubt it) it only takes a few minutes to check.  You should be using a port in the range of roughly 50,000 - 65,000.  If the port you are using is different . . . try changing it to a port in that range . . . it is not going to hurt anything.  If you have manually forwarded your torrenting ports of course you will need to change your port forwarding.  But if you have done it once it is pretty easy to change it to a different port.

If chaning the port helps . . . you might be being traffic shaped . . . so take a look at this:

first check here and locate your ISP.

then read this for suggestions on how to avoid your ISP's efforts (if necessary)

The words here and this are links ;-)

Hmm that is all I can think of for now.  Give all that a try and let us know a little more info!

[pocketlama]

Thanks for all the info, I didn't make it clear that this is happening to about 15 seeds and 1 download so they were all from different sites. I don't know if they are public or private. And it's still happening after downloading and seeding a game on uTorrent. I'll go to the links you gave me.

'GaryE' pid='281' dateline='1408401137'
Well if you are using a torrent program you are not downloading data from a website you are downloading it from a peer (or more usually many peers).  But that is neither here nor there.

What kind of site is it?

Is it a private site or is it a public site (like The Pirate Bay)?

If the site is a true private site the fact that you can download with another torrent client is usefull information.  Just to be clear sites like demonoid are not private sites Demonoid is an invite only public site.  If the site is a public site .  . . it is compeletly irravelent that you can download with another client.

The reason I ask is that those errors usually indicate a problem with the tracker.  However, since public sites allow any number of trackers in their .torrent files . . . it might just be one tracker which is experiening problems which for some random reason all of your other torrents are using.  But the .torrent file you downloaded and opened with uTorrent might have a differnet tracker or set of trackers or is might just not have the problem tracker in it.

Once you sucessfully downloaded the data using uTorrent did you check if you were still getting those errors in Vuze?  It is possible (but unlikely) that the torrent-tracker problem was solved while you were downloading uTorrent and grabbing the .torrent file which worked correctly.

It could be a wierd traffic shaping problem.  Have you checked to see which port Vuze is using and which port(s) uTorrent are using?  If for example you are using a standard port for Vuze which your ISP is blocking it is vaguly possible that could cause that error (but I seriousl doubt it) it only takes a few minutes to check.  You should be using a port in the range of roughly 50,000 - 65,000.  If the port you are using is different . . . try changing it to a port in that range . . . it is not going to hurt anything.  If you have manually forwarded your torrenting ports of course you will need to change your port forwarding.  But if you have done it once it is pretty easy to change it to a different port.

If chaning the port helps . . . you might be being traffic shaped . . . so take a look at this:

first check here and locate your ISP.

then read this for suggestions on how to avoid your ISP's efforts (if necessary)

The words here and this are links ;-)

Hmm that is all I can think of for now.  Give all that a try and let us know a little more info!

 

 

 

[pocketlama]

Wow, that was wierd. I did Tools>Options>Mode and set it to beginner mode. A little later I went back to the program and it's working again. I have no idea why that might have worked.
.
.

'pocketlama' pid='283' dateline='1408404758'
Thanks for all the info, I didn't make it clear that this is happening to about 15 seeds and 1 download so they were all from different sites. I don't know if they are public or private. And it's still happening after downloading and seeding a game on uTorrent. I'll go to the links you gave me.

'GaryE' pid='281' dateline='1408401137'
Well if you are using a torrent program you are not downloading data from a website you are downloading it from a peer (or more usually many peers).  But that is neither here nor there.

What kind of site is it?

Is it a private site or is it a public site (like The Pirate Bay)?

If the site is a true private site the fact that you can download with another torrent client is usefull information.  Just to be clear sites like demonoid are not private sites Demonoid is an invite only public site.  If the site is a public site .  . . it is compeletly irravelent that you can download with another client.

The reason I ask is that those errors usually indicate a problem with the tracker.  However, since public sites allow any number of trackers in their .torrent files . . . it might just be one tracker which is experiening problems which for some random reason all of your other torrents are using.  But the .torrent file you downloaded and opened with uTorrent might have a differnet tracker or set of trackers or is might just not have the problem tracker in it.

Once you sucessfully downloaded the data using uTorrent did you check if you were still getting those errors in Vuze?  It is possible (but unlikely) that the torrent-tracker problem was solved while you were downloading uTorrent and grabbing the .torrent file which worked correctly.

It could be a wierd traffic shaping problem.  Have you checked to see which port Vuze is using and which port(s) uTorrent are using?  If for example you are using a standard port for Vuze which your ISP is blocking it is vaguly possible that could cause that error (but I seriousl doubt it) it only takes a few minutes to check.  You should be using a port in the range of roughly 50,000 - 65,000.  If the port you are using is different . . . try changing it to a port in that range . . . it is not going to hurt anything.  If you have manually forwarded your torrenting ports of course you will need to change your port forwarding.  But if you have done it once it is pretty easy to change it to a different port.

If chaning the port helps . . . you might be being traffic shaped . . . so take a look at this:

first check here and locate your ISP.

then read this for suggestions on how to avoid your ISP's efforts (if necessary)

The words here and this are links ;-)

Hmm that is all I can think of for now.  Give all that a try and let us know a little more info!

 

 

 
 

 

 

 

[GaryE]

You might have gotten the security settings changed.  Like if for some reason you were only accepting peers who had the same level of encryption as you had selected.  I am not 100% sure . . . but I think beginner mode changes that to accepting connections from all.  That is at least one possible explanation . . . I am sure there are others.   However, since you got it working . . . the exact explanation hardly matters.

Glad it is working for you!

Just so you know.  If you need an account to access a torrent site it is (in general) a private site.  If you can just visit their web-page and download to your hearts content . . . it is a public site.  ThePirateBay would be a very well known example of a public site.  Demonoid is an exception because you must have an account but under the hood it functions like a public site.  A good well known example of a private site would be something like What.cd.  Some private sites require you to get invited to the site by a current member.  These are called invite-only private sites.  Other private sites have open sign-ups and anyone can signup whenever they want.  Those are called open-invite private sites.

The main technical difference between the two is that private sites only allow peers who have a membership to the site.  If you are not a member you can not leech the torrent.  Private sites also track your upload and download amounts and require you to have a certain ratio (upload to download) to maintain your membership.  Public sites either do not keep track of upload and download amounts at all for individual users . . . or ratios are not enforced.

Again I am glad you sorted out your problem!

[pocketlama]

It's one of those wierd ones I guess. I didn't change the settings myself but I remember now it started after using Malwarebytes. I actually had to do a system restore because it messed up something else also so it could have messed up this as well.

Thanks for the info on public/private. I didn't know that and I appreciate your sharing the knowledge with me.
.
.

You might have gotten the security settings changed.  Like if for some reason you were only accepting peers who had the same level of encryption as you had selected.  I am not 100% sure . . . but I think beginner mode changes that to accepting connections from all.  That is at least one possible explanation . . . I am sure there are others.   However, since you got it working . . . the exact explanation hardly matters.

Glad it is working for you!

Just so you know.  If you need an account to access a torrent site it is (in general) a private site.  If you can just visit their web-page and download to your hearts content . . . it is a public site.  ThePirateBay would be a very well known example of a public site.  Demonoid is an exception because you must have an account but under the hood it functions like a public site.  A good well known example of a private site would be something like What.cd.  Some private sites require you to get invited to the site by a current member.  These are called invite-only private sites.  Other private sites have open sign-ups and anyone can signup whenever they want.  Those are called open-invite private sites.

The main technical difference between the two is that private sites only allow peers who have a membership to the site.  If you are not a member you can not leech the torrent.  Private sites also track your upload and download amounts and require you to have a certain ratio (upload to download) to maintain your membership.  Public sites either do not keep track of upload and download amounts at all for individual users . . . or ratios are not enforced.

Again I am glad you sorted out your problem!
 

 

[cuban_cigar]

> but I think beginner mode changes that to accepting connections from all.  That is at least one possible explanatio


That would be a vast violation of trust. It will litterally get people bankrupted, and thrown in jail

[GaryE]

If you think that enabling encryption somehow stops people from seeing what you are downloading and uploading . . . you do not understand how anti-filesharing people gather data.

They just sit in the swarm and collect IP addresses.  Enabling or disabling encryption does nothing at all to prevent that.  As long as the peer has the same encryption setting as you do and they have the .torrent file from the same source as you do . . . they can see your ip address no problem at all.  If you want protection from that you need a VPN . . . not encryption.

The only thing that encryption does is to hide the data which is actually in the torrent stream from an outside party.  However, since that is not how anti-file sharing nazi's gather data . . . it does not do what you seem to think it does.  It protects you from your ISP know exactly what kind of data you are passing/receiving (without deep packet inspection) and it protects you from some man in the middle attack where by someone in the middle of the data stream can access the information -- but that is it mate.  It was designed as a method (for the most part) to avoid some ISP's efforts at traffic shaping.

So no it would not be a "vast violation of trust".  Nor would it "litterally get people bankrupted, and thrown in jail".  That is just not how it works.