Vous n'êtes pas identifié.


Foot Land

Écrire une réponse

Veuillez écrire votre message et l'envoyer
:) :| :( :D :o ;) :/ :P :lol: :mad: :rolleyes: :cool:

Code de Sécurité


Résumé de la discussion (messages les plus récents en premier)

05-05-2018 06:42:12


It seems that nzbget sometimes goes over the maximum allowed number of connections:
ERROR Authorization for <server> failed (Answer: 400 <server>: Your per-user connection limit reached)
Downloading new posts works great, but on older posts these errors sometimes pop up. It seems to me that these errors start to show as soon as a single part fails to download, and then they keep on coming until nzbget is closed. When nzbget is restarted with the same files in the queue, it almost immediately starts producing more of these errors, but when the queue is emptied and a new (more recent) nzb file is loaded, it works ok again.
Also, when these errors do occur, it would be nice if nzbget was somewhat less aggressive in retrying. At one point I think I may have been banned from the news server temporarily when the error was replaced with "502 Access denied to your node". But that might have been something unrelated.
For what it's worth, the most recent download that caused these errors was The.X.Factor.S05E11.WS.PDTV.XviD-FTP from a.b.multimedia with an nzb file from nzbsearch.info.

Any help will be apprecited.

I didn't find the right solution from the Internet.

Sales Explainer Video

Thank you.