SharpLeech 2.0.0 BETA

Status
Not open for further replies.
[slide]http://img155.imageshack.us/img155/340/75707884.png[/slide]



In window 7.i got this error when i login from forumw and my site and press start leaching after 1 sec its automatic stop.please help me

Edited: Please refrain from using huge fonts. we arent blind :) - jayfella.
 
i dunno whats happens to me , i can't visit warez-bb with my web browser !! its been for a week i think !!

page not found error shows up !
 
i dunno whats happens to me , i can't visit warez-bb with my web browser !! its been for a week i think !!

page not found error shows up !
they are trying to ban SL users, your ip might be flagged so it won't work to surf it, you have to use proxies now.

Hyperz, please we need proxy solution.
 
Restart your modem. You should get a new IP that way. See if you can access the site again then.

they are trying to ban SL users, your ip might be flagged so it won't work to surf it, you have to use proxies now.

Hyperz, please we need proxy solution.

How on earth are they gonna IP ban users when 90+% of the ISP's work with dynamic IP's. Let me tell you, they can't. Well they can but all they will be doing is banning innocent people. I already know you need a proxy solution. But don't generalize. You =/= everyone else.

The simple fact is that I can't add proxy support without recoding the whole Http library in SL. And I really don't feel like going trough the effort of making a new Http lib bassed on the low level TcpClient class rather than the current WebRequest one.
 
The problem is not from the browser ... i tried with many browsers but didn't work !!!
i think our ip is on their .htaccess lol
i tried with web proxies it worked so i am pretty sure i am banned !
and ya they can't just ban ips, except if they are banning ip ranges !!!!
 
They are not gonna ban ranges because doing that for a while will cut their traffic in half. As I said, restart your modem and/or router and try again.
 
He will get an IP if he has a dynamic connection not static and i can confirm that they are trying to ban IP's and today i realized that they are trying to limit max connection for some IP's instead of banning them which makes the surfing on WBB real slow, with mode_security on apache they can write a rule to ban the IP who consume much resources or establish mutiple connections at the same time.

Then why you're talking about proxy issue as if no one in the world use proxy, most of the web apps have proxy option from torrent clients to browsers etc ...., it's not fair to lose proxy support because you ran too fast to use .Net 4.0, you should have waited more to make more studies about it.

You should consider adding proxy option to SL or let it read IE settings correctly or your SL2 will not be popular as SL1 i can assure.
 
First of all, they are not using Apacha. If they put a limit on the maximum number of connections that is no problem because you only need one. And with one connection you won't notice much of a slow down. If you do it'll only be on the 1st page load. After that the cache kicks in.

How did you test the max # of connections btw? Or do you just blindly assume they do? You also don't seem to realize that there are different types of proxies. The one you need to connect to the internet is not the same type of proxy that is generally used to avoid IP bans. So reading the IE proxy settings does not give SL proxy support per sé. Fact is, very little people need proxy support. Another fact is that SL2 is already more popular than SL1. To add to that, I don't care how many people use SL as I don't benefit from the amount of users.
 
Who told you that i need one connection? SL can run multiple instances, you can run like 10 and leech at the same time without pause, so it will open at least 10 connection and i get a lot of forbidden messages from the server.

To reduce the DDoS attacks they must limit the max connections for sure or they won't survive or they must setup a firewall and ban IP's.

I don't care how the proxy will work, all i know that this app needs a proxy support and if you don't like how things going on i suggest that you go now and start working on SL2 Pro and all the features i need and others need and i will be your first buyers for sure but stop saying very little people use proxy.
 
SL2 isn't made to run multiple instances so you should expect problems when running more instances and I have said this many times before. That's why the whole async thing was implemented. One SL instance will use 12 parallel connections with a pause value of 0. And 1 with a pause value that above 1. WBB doesn't support 12 connections (4 to be exact) and they have been rejecting connections since they moved to nginx. That's why I've been saying that a pause value of 1 or greater should be used when leeching from WBB. But people don't read and are surprised when they come across problems.

And who are you to start telling me what I should and shouldn't do? You're the only that is creating a big deal out of the proxy issue.
 
I was talking about SL1, i didn't mention SL2, if SL2 can't establish 12 connections then it's sucks because it will skip tons of threads and maybe pages, and i can tell you that WBB now allows 1 connection only not even 4 and more than that it will give errors and skips threads.

You really should think about Pro version and make a website for it and make a ticket system so you get benefit of your work and enjoy it at the same time.
 
I was talking about SL1, i didn't mention SL2

Erm:
You should consider adding proxy option to SL or let it read IE settings correctly or your SL2 will not be popular as SL1 i can assure.

Did you know this is the SL2 topic? SL1 is old and broken. I no longer support it

if SL2 can't establish 12 connections then it's sucks because it will skip tons of threads and maybe pages, and i can tell you that WBB now allows 1 connection only not even 4 and more than that it will give errors and skips threads.

You have absolutely no clue what you're talking about, no offense. How many connections can be sustained depends completely on the site/server and not on SL. Going over the connection limit is no problem. It happens on every site since no site will allow 12 open connections from a single IP. Either WBB fails at properly setting up nginx or they intentionally spit out errors when to much connections take place. That still has nothing to do with SL but WBB.

Do me a favor and go use a better leecher or build your own. Since you seem to think you know everything better. This was my last reply to you. I'm not gonna waste my time having a pointless discussion.
 
Status
Not open for further replies.
Back
Top