#1
|
|||
|
|||
Proxies are marked as failed even though they're fine
I'm using some proxies running in some docker containers, but they're being marked as failed by JDownloader after initially working fine.
12.08.21 14.37.07 <--> 12.08.21 14.55.54 jdlog://3636825302851/ From the logs it seems like the proxy is marked as failed around the time JDownloader checks http://ipcheck1.jdownloader.org/. The proxy is a **External links are only visible to Support Staff**gluetun docker container. Last edited by mjolnir870; 12.08.2021 at 22:32. |
#2
|
|||
|
|||
Yes i was fine until update Jdownloader and all my proxies (socks4) thats works excelent, with a huge speed and fastest just fail to
1) Check a premium user 2) Download with the socks4 All was fine until the update. To solve this i just backup the links and socks, unistall, make a clean fresh new install and the problem was nearly solved but not totally solved. |
#3
|
||||
|
||||
@mjolnir870
Seems like your proxy requires authentification or you've blacklisted "ipcheck3.jdownloader.org": Code:
----------------Response------------------------ HTTP/1.1 407 Proxy Authentication Required Proxy-Authenticate: Basic realm="Access to Gluetun over HTTP" Date: Thu, 12 Aug 2021 19:46:10 GMT Content-Length: 0 ------------------------------------------------ @lrmcba We haven't changed the proxy handling in any way. Please post your log-ID here | bitte poste deine Log-ID hier. -psp-
__________________
JD Supporter, Plugin Dev. & Community Manager
Erste Schritte & Tutorials || JDownloader 2 Setup Download |
#4
|
|||
|
|||
Quote:
Code:
root@server:~# curl -m 15 --proxy-user userredacted:passredacted --proxy gluetun ipcheck3.jdownloader.org 138.199.28.249 Code:
2021-08-20 18:37:28.19305661 CDT 2021/08/20 18:37:28 INFO http proxy: 192.168.xx.xx:43730 200 OK GET http://ipcheck3.jdownloader.org/ When a proxy is disabled I can toggle the enabled checkbox to force it active again, and then JDownloader will successfully download using it again. Then it'll fail again after a 2nd or 3rd download. Also, as far as I can tell, this only happens with mega downloads. Last edited by mjolnir870; 21.08.2021 at 02:28. |
#5
|
|||
|
|||
After further testing, it looks like these proxy errors occur if I check "Use SSL?" for mega in Plugins settings in JD. Once I turned that off the proxy errors disappeared for over 600 downloads. As soon as I turned it back on I had 8 proxy errors within a few minutes.
|
#6
|
||||
|
||||
@mjolnir870
at a guess maybe a issue with Java (version) or 3rd party support from bouncy castle. post a log of those sessions? without access to log its very hard or impossible to identify and or fix. alternatively Jiaz would need to install your proxy and trying to reproduce it as you've described. -edit- see you provided a log session previously and psp pulled some info. Maybe issue Jiaz does need to further investigate. but your findings in you last two posts is great. raztoki
__________________
raztoki @ jDownloader reporter/developer http://svn.jdownloader.org/users/170 Don't fight the system, use it to your advantage. :] Last edited by raztoki; 21.08.2021 at 11:51. |
#7
|
||||
|
||||
@mjolnir870:
Log shows that proxy fails to connect to mega via https/port 443. it simply doesn't return anything and fails with Quote:
But thanks to your report I was able to find/fix bug that causes JDownloader to *temp forget* the logins
__________________
JD-Dev & Server-Admin Last edited by Jiaz; 17.09.2021 at 17:03. |
Thread Tools | |
Display Modes | |
|
|