Quote:
Originally Posted by Jiaz
Thanks. The 400 Bad Request is just fine. The update client just probing the server if a feature is supported and because it isn't, the server responds with 400 Bad Request.
Thanks for the log but it does not contain any update issue nor any installation of an update. I need the logs for when it fails, so please close JDownloader. Delete the logs and tmp and update folder, also delete Core.jar and start JDownloader again, wait for error, then zip logs folder and send it to me.
I don't think that the list is the cause of issues. You screenshots show that JDownloader can download the update at ultra high speed (cached/buffered by firewall/av) but then something fails. If vipre would be blocking it, there would be no downloaded update in first place. So please try to create a log that contains the issue, then we can check it.
|
Alright, fresh logs sent.
JD will not show an error in it's own.
It only shows error if I click "skip" while update is in progress, so I did.
The error has shown it's face and JD closed itself.
Ive tested twice closing Vipre and each time the update progress moved far far ahead.