@Ricky: A quick test revealed, that it's broken if "direct downloads" is disabled in the MU account and works otherwise. Before, it worked in both cases.
@kudla, alex_ne: I believe the FS FTPs are limited to 2MB/s.
Your developer's time would have been better spend sending patches to the Jdownloader devs than writing FSM. It isn't open source for nothing and you wouldn't have had to re-invent the wheel.
Just my two cent.
Ricky, since your inbox is full, I'll post this here:
I don't get the 612 at home but while remote uploading to Netload.
Obviously I don't know their servers IPs.
PS: You should request a bigger inbox :P
@explo1515: Ricky probably put you on his ignore list and doesn't see your messages anymore.
@Ricky: I think you should look into his case. It really looks weird and he posted his user name by now.
He said in 5min, not in 15min.
You should stop laughing, btw. :facepalm:
This speed is real. I recently moved 300GB in 1.5h (NL->FS) which is about the same.
I just remote uploaded 90 links (35GB total) from Netload to Fileserve.
After 25min everything was done (~23,9MB/s), with no files failed and no files broken.
Last weekend almost all files failed and before that many, many files were broken.
I hope it stays like this :)
@AppleS:
@Ricky: I assume a file get's moved from FTP to an account once the connection terminates, is that correct?
I'm asking because it's the clients, not the servers, job to decide if a file should be replaced, resumed or overwritten.
Of cause the file has to remain on the FTP for the...
I can't connect to the fileserve.com website at all.
www.downforeveryoneorjustme.com currently says "It's not just you! http://fileserve.com looks down from here."
Strangely it's working normal via TOR.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.