rapidleech

--(RAGHUL)--, on 15 April 2012 - 04:29 PM, said:

no he's right, i shouldn't have posted in this section. i just saw a previous replies was linking to a premium page and thought now was the time for shameless self-promotion. premium linkages removed free link generators only please

you're trying to save files into a different home directory (/home/a5785809/public_html/leech/files/) from where rapidleech is actually running (/home/rasik/domains/*************************/public_html/leech/)

Either set your RL save path to /home/rasik/domains/*************************/public_html/leech/files/ OR disable open_basedir. i'd strongly recommend you save files directly to where your rapidleech is running.

=> => => why not just create a gateway php file which you send a simple request to from your app, and that formats the request into a POST (with appropriate parameters for rapidleech to download) and sends the request to your rapidleech index.php?

should be a lot simpler than trying to re-invent the wheel, which looks to be what you're doing atm...

for example

#!/usr/bin/php -q
<?php
$link = $_GET['link'] #or however you want to get it
 
echo "goind to download .. \n";
 
 
 
$postfields = array(
link => 'http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dblah'
referer=>'',
iuser=>'' ,
ipass=>'' ,
comment=>'' ,
ytube_mp4 => 'on',
yt_fmt => 'highest',
tor_user =>  '',
tor_pass =>'' ,
mu_cookie =>'' ,
cookie =>'' ,
email =>'' ,
method =>'' ,
partSize =>'' ,
proxy =>'' ,
proxyuser =>'' ,
proxypass =>'' ,
premium_user =>'',
premium_pass =>'' ,
path =>'',
);
$ch = curl_init('/home/rapidleech/public_html/index.php');
curl_setopt ($ch, CURLOPT_POST, true);
curl_setopt ($ch, CURLOPT_POSTFIELDS, $body);
curl_setopt ($ch, CURLOPT_RETURNTRANSFER, true);
$page = curl_exec ($ch);
curl_close ($ch);
 
//did it work?
var_dump($page);
 
//etc...

haven't used curl on a local file before, but you could even change it to a remote server at least the parameter list should help, it's not all of them.

_R_V_T_™, on 10 April 2012 - 11:44 AM, said:

check you don't have a firewall such as csf killing off the php process after a certain time (depends on csf process tracker settings). other firewalls check the docs.

afaik letitbit send new cookies on every page load, which is why you see a lot of 'deleted' cookies. also i think letitbit only allow using consistent cookies on the same ip which logged into the premium account in the first place...

Letitbit are either limiting simultaneous connections to a premium account, and/or banning ips, because it works again if i change ip, but then is stops working shortly after.

http://code.google.c...ech/source/list