Back-end Server At Capacity 20250227

[mattcargile]

Checklist

• I confirm there are no unresolved issues reported on the Chocolatey Status page.
• I have verified this is the correct repository for opening this issue.
• I have verified no other issues exist related to my problem.
• I have verified this is not an issue for a specific package.
• I have verified this issue is not security related.
• I confirm I am using official, and not unofficial, or modified, Chocolatey products.

What You Are Seeing?

Nuget error Back-end Server At Capacity

What is Expected?

Upgrade To happen.

How Did You Get This To Happen?

gsudo choco upgrade all -y

System Details

• Operating System: Windows 11
• Windows PowerShell version: PowerShell 7
• Chocolatey CLI Version: 2.4.2
• Chocolatey Licensed Extension version: 1.4.0
• Chocolatey License type: Community
• Terminal/Emulator: Windows Terminal

Installed Packages

chocolatey 2.4.3
chocolatey-compatibility.extension 1.0.0
chocolatey-core.extension 1.4.0
chocolatey-dotnetfx.extension 1.0.1
chocolatey-font-helpers.extension 0.0.4
chocolatey-visualstudio.extension 1.11.1
chocolatey-windowsupdate.extension 1.0.5
dbeaver 24.3.5
discord 1.0.9166
discord.install 1.0.9166
DotNet4.6 4.6.81.20150925
DotNet4.6-TargetPack 4.6.81.20150925
dotnet-6.0-aspnetruntime 6.0.36
dotnet-6.0-desktopruntime 6.0.36
dotnet-6.0-runtime 6.0.36
dotnet-6.0-sdk 6.0.428
dotnet-6.0-sdk-4xx 6.0.428
dotnet-8.0-desktopruntime 8.0.13
dotnet-8.0-sdk 8.0.406
dotnet-8.0-sdk-3xx 8.0.309
dotnet-8.0-sdk-4xx 8.0.406
dotnet-9.0-desktopruntime 9.0.2
dotnet-desktopruntime 9.0.2
dotnetfx 4.8.0.20220524
KB2919355 1.0.20160915
KB2919442 1.0.20160915
KB2999226 1.0.20181019
KB3033929 1.0.5
KB3035131 1.0.3
KB3063858 1.0.0
KB3118401 1.0.5
keepass.install 2.57.1
logparser 2.2.0.1
lua 5.1.5.52
mitmproxy 11.1.3
nerd-fonts-CascadiaCode 3.2.1
nerd-fonts-iA-Writer 3.2.1
nerd-fonts-Meslo 3.2.1
nerd-fonts-Terminus 3.2.1
nerd-fonts-UbuntuMono 3.2.1
netfx-4.7.2 4.7.2
netfx-4.7.2-devpack 4.7.2.20210903
openssh 9.5.0-beta1
pdftk-java 3.3.3
PDFXchangeEditor 10.5.2.395
perfview 3.1.19
powershell-core 7.5.0
powertoys 0.88.0
shutup10 1.9.1439
slack 4.42.120
sql-server-management-studio 20.2.30
ssis-vs2022 1.5.0
ssms-tools-pack 6.3.0
sysinternals 2025.2.13
vcredist140 14.42.34438.20250221
vcredist2005 8.0.50727.619501
vcredist2015 14.0.24215.20170201
visualstudio2022community 117.13.1
visualstudio2022-workload-data 1.0.0
visualstudio2022-workload-manageddesktop 1.0.2
visualstudio-installer 2.0.3
vmrc 12.0.5.22744839
wireshark 4.4.5
63 packages installed.

Output Log

Gist

Additional Context

Was referred here by gep13 on Twitter.

[pauby]

@mattcargile can you provide the link to the social media post? There is a lot of information missing here that may be in that post.

[mattcargile]

There isn't much to it. Here is my original message.

[pauby]

@mattcargile is the issue still happening, or was it transient?

@Windos can you have a look at this?

[mattcargile]

It was transient. Probably for an hour or less. I tried a few times and gave up. Then when I came back it eventually worked.

[gep13]

Just to chime in here, and explain why I asked @mattcargile to raise the issue in the first place...

This was happening just after the release of Chocolatey CLI 2.4.3, and I thought the log might provide information about what part of the process was causing the error, i.e. the searching/resolving of the package version, or the actual process of downloading the nupkg. This might further provide information in where to dedicate resources during a release of Chocolatey CLI.

[Windos]

This appears to line up with a period of high traffic and the resulting inability for the backend to service all of the flood of requests. It was also during the initial rush of people upgrading to Chocolatey CLI 2.4.3 which only exacerbates this situation.

[pauby]

@Windos is there anything more to be done here?

I've moved this as it is not a Chocolatey CLI issue.

[Windos]

@pauby - Apologies I lost track of this issue for a moment there. Not directly, no.

We are looking at optimizations to CCR to handle heavy load better, but just after a CLI release (which has many millions of upgrades come through in a reasonably small window) is potentially always going to be a struggle while it's still v2 only.