Closed svasek closed 7 years ago
how to reproduce this problem? what exactly you have been looking for? Just tried it now and everything is working well. But I noticed that ulozto is having some problems with their servers, many times it shows webpage "server busy..."
I don't know yet. After approx. 30 downloads from ulozto it started to failing on every request to download. Restart didn't help. Only uninstall and install solved/workaround the problem.
Could you please add a line as in following code in api.js ? So we can see what server responded with
myRequest(mainurl, function(body) {
console.log(body); // <-------- ADD THIS LINE
body = body.split("\r").join("").split("\n").join("#");
keepCookie = body.match("(ULOSESSID=.*?);")[1];
keepCookie += "; "+body.match("(uloztoid=.*?);")[1];
//keepCookie += "; maturity=adult";
var newLocation = body.match("#Location: (.*?)#");
mainurl = newLocation[1];
doMainRequest(doCaptcha);
});
}
Attaching the log file: ulozto-log.txt
the url it tries to download is not valid, in the response you can find "Stranka nenalezena" message. When did you try to download the file? Probably the URL is not valid anymore, maybe its validity is just few hours
I downloaded it by clicking in the search results. Anyway we should fix the stopping of the service once this occur.
But did you start the download process right after adding the URL to download list? For me it seems like the download URL was queued in list for few hours (maybe you wanted to download more files at once). I don't know how to fix this problem... Maybe when it will happen to me I will investigate it more deeply. But we need to keep in mind that the "file-tracking" urls are valid for short period of time, they just redirect you to the right URL. Maybe it would be good idea to obtain the redirection link right after you add the url to download queue. But I think the synology download station plugins does not offer this option...
Ok, I will fix the crash at least, probably during weekend
I tried to fix the issue in latest commit, please let me know if the issue will happen again. It was caused by downloading outdated URL as I suggested in previous comment, I was able to reproduce the problem quite easily, validity of the URL is probably just 15 minutes
Log contains lines bellow: