Connection Limit Not Respected(Authorizaiton Failure)

[prikhi]

Is there already an issue for your problem?

• I have checked older issues, open and closed

NZBGet Version

latest-testing (if not listed here)

Platform

Linux/Docker

Environment

OS: Arch
Package: nzbget-git 26.2.r2727.2fb4593f-1
Linux 6.18.28-1-lts #1 SMP PREEMPT_DYNAMIC Fri, 08 May 2026 07:04:32 +0000 x86_64 GNU/Linux

Current Behavior

I have a newserver subscription that allows 100 concurrent connections with no speed limit. In nzbget, I have the server set to 100 connections.

When a download begins, I am able to start downloading from the specified server. After a short amount of time, I start getting 502 errors for the remaining parts of the nzb with a connection limit exceeded error message:

Could not read from TLS-Socket: Connection closed by remote host
Authorization for REDACTED (news.redacted.com) failed: 502 connection limit (100) reached
Blocking REDACTED (news.redacted.com) for 10 sec

The speed graph shows the connections spinning up and then dieing out due to opening too many connections:

I've tried setting the limit to 99 & the issue still occurs.

Expected Behavior

Nzbget respects the connection limit set for each news server.

Steps To Reproduce

No response

Logs

No response

Extra information

No response

[dnzbk]

@prikhi Hi, thanks for the report. Unfortunately I cannot reproduce this.
Could you please clarify:

1. Any specific configuration details of your usenet servers you can share?
2. Do you use one usenet server or multiple?
3. Are you using any extensions that might consume connections, like Extension-Completion?
4. What usenet provider are you using?

You can send the info to denis@nzbget.com if you don't want to share something publicly.

[prikhi]

hmm sorry, let me go poke the provider before bugging ya any more

[prikhi]

Seems like a transient error w/ the newserver, sorry for the noise!

[dnzbk]

Seems like a transient error w/ the newserver, sorry for the noise!

Sure, no worries - thanks for the update.

[prikhi]

Actually, just tested something randomly & was able to reproduce w/ another newserver - seems like it only happens when downloading nzbs where articles have been deleted & the full download fails, I see the X of Y article downloads failed for <path> error right before the 502s.

[dnzbk]

I see. l'll give that a test, thanks.