[nathan1]

Hello Staff,
I don't know but I have easybytez account temporarily disabled after that I download (and check) many links with jdownloader using my premium easybytez account

I post LOG, Is there a prevention mechanism when checking and downloading a lot of files for easybytez?



LOG

22.02.21 16.36.44 <--> 22.02.21 03.40.51 jdlog://8825725302851/

[pspzockerscene]

Originally Posted by nathan1

I post LOG, Is there a prevention mechanism when checking and downloading a lot of files for easybytez?

No idea what exactly you mean.
If you're a premium customer you shouldn't run into such limitations anyways so if there is a limit that happens after checking multiple URLs you should consider contacting the easybytez support.
Apart from that, you could temporarily turn off the linkcheck in JD:
Settings -> Advanced Settings -> Search for "linkcollector do link check" -> Disable this & restart JD

I wasn't able to analyze your log properly as it is just too big.
Please post a new log which only contains the account checking failure.
Also, please enable DEBUG logs before creating that new log:
https://support.jdownloader.org/Know...d-session-logs

-psp-

[nathan1]

ok, I enable Debug LOG, restart, check links. Then I disable linkcollector, restart and add links. This is the last log.

22.02.21 17.21.35 <--> 22.02.21 17.21.34 jdlog://9925725302851/

I try to log into my easybytez account from another IP but seems that credentials doesn't work because is disabled.
I written to Easybytez support ticket and I wait an answer.

Before Debug Log I attach another LOG where maybe you can see failure.

22.02.21 16.36.44 <--> 22.02.21 16.27.59 jdlog://3035725302851/

[pspzockerscene]

Both of your logs show timeouts:

----------------ConnectionExceptions-------------------------
0:easybytez.com/128.65.209.18:80|java.net.SocketTimeoutException(connect timed out)|retrySSL:null
----------------Request-------------------------
-------------Not Connected Yet!-----------------

----------------Response Information------------
-------------Not Connected Yet!------------------


	at jd.http.Browser.openRequestConnection(Browser.java:1824)
	at jd.http.Browser.openRequestConnection(Browser.java:1633)
	at org.jdownloader.plugins.components.antiDDoSForHost.sendRequest(antiDDoSForHost.java:285)
	at org.jdownloader.plugins.components.antiDDoSForHost.getPage(antiDDoSForHost.java:151)
	at org.jdownloader.plugins.components.XFileSharingProBasic.getPage(XFileSharingProBasic.java:2445)
	at org.jdownloader.plugins.components.XFileSharingProBasic.getPage(XFileSharingProBasic.java:2441)
	at org.jdownloader.plugins.components.XFileSharingProBasic.loginWebsite(XFileSharingProBasic.java:3406)
	at org.jdownloader.plugins.components.XFileSharingProBasic.fetchAccountInfoWebsite(XFileSharingProBasic.java:2921)
	at jd.plugins.hoster.EasyBytezCom.fetchAccountInfoWebsite(EasyBytezCom.java:144)
	at org.jdownloader.plugins.components.XFileSharingProBasic.fetchAccountInfo(XFileSharingProBasic.java:2914)
	at jd.controlling.AccountController.updateAccountInfo(AccountController.java:323)
	at jd.controlling.accountchecker.AccountChecker$AccountCheckJob.check(AccountChecker.java:47)
	at jd.controlling.accountchecker.AccountChecker$1.run(AccountChecker.java:155)
Caused by: java.net.SocketTimeoutException: connect timed out

Either way this is not a JDownloader issue!

-psp-

[nathan1]

What does it mean "timeouts" ?

If before I was able to use JD to download from easybytez, what kind of problem is it if then connection and downloading fails?
Are you telling me that the LOG is saying that at some point there was an interruption to the connection to easybytez for no clear reason?

[nathan1]

Now I test with another easybytez account and I get this error

Server error 'Error happened when generating Download Link'



LOG

22.02.21 19.20.34 <--> 22.02.21 19.19.19 jdlog://1435725302851/

P.S: Easybytez support answer me now and tell me this

Hello,

checking a high a amount of links in a short time might be recognized as a flooding /brute force hack attenpt and will be blocked by our firewall.
I dont see your account blocked but your IP address was.
I have released the IP address now from the blockage and it should work again.

[nathan1]

I write again to easybytez because I think that is not just a anti-flooding mechanism as they claim but is a very frustrating limitation by service.
I reduce amount of links over a very large time but still problem happens.

You can check complete LOG, you can see that I check links in different time, not in continuous way.

22.02.21 20.48.35 <--> 22.02.21 19.19.19 jdlog://2945725302851/

[pspzockerscene]

Originally Posted by nathan1

What does it mean "timeouts" ?

See my last post.

Originally Posted by nathan1

If before I was able to use JD to download from easybytez, what kind of problem is it if then connection and downloading fails?

The issue is definitely not related to our software.
The last change of our easybytez.com plugin was on 2020-04-24 -> You can verify this yourself: We're open source

Originally Posted by nathan1

Are you telling me that the LOG is saying that at some point there was an interruption to the connection to easybytez for no clear reason?

Yes.

Originally Posted by nathan1

Now I test with another easybytez account and I get this error

Server error 'Error happened when generating Download Link'

This is an error from easybytez - it is again not related to our software!
You can send this to their support:

<tr><td align=center>
<font style="color:#d33;">Error happened when generating Download Link.<br>Please try again or Contact administrator.<br>(ERROR:no_file)</font>
<font class="ok"></font>

I'm unable to check your 2nd log as it is again very big and our log servers are slow at this moment.

Please ALWAYS check the manual download via browser whenever you're experiencing issues in JD.
In most of all cases the issues are caused by the service you're trying to download from and not JDownloader...

-psp-

[nathan1]

yes, you're right.

Error happened when generating Download Link

I read now that it was a server failure.