{"id":77063,"date":"2023-06-05T13:09:27","date_gmt":"2023-06-05T17:09:27","guid":{"rendered":"https:\/\/jumpcloud.com\/?post_type=support&p=77063"},"modified":"2024-02-23T10:58:07","modified_gmt":"2024-02-23T15:58:07","slug":"prevent-chocolatey-rate-limiting-in-jumpcloud","status":"publish","type":"support","link":"https:\/\/jumpcloud.com\/support\/prevent-chocolatey-rate-limiting-in-jumpcloud","title":{"rendered":"Prevent Chocolatey Rate Limiting in JumpCloud"},"content":{"rendered":"\n
JumpCloud uses Chocolatey to facilitate its Software Management features<\/a>. By default, packages will be pulled from the Chocolatey Community Package Repository. Chocolatey packages are rate limited at 20 packages per minute per IP address. If you exceed that limit, your IP will be temporarily banned for one hour. For more information, see Chocolatey\u2019s documentation on excessive use and rate limiting<\/a>. <\/p>\n\n\n\n When your org exceeds the rate limit for a certain software package, you will see an \u201cInstall Failed\u201d status for software packages in the Software Management section of the Admin Console. This status only appears for software packages that have not yet been installed and fail or packages that attempt to update and fail. It will not appear for previous installed software. In the event that you get an \u201cInstall Failed\u201d status, you must view the software details. If the install failed due to rate limiting, you will see the following message: \u201cSoftware failed to install or update because of Chocolatey rate limiting.\u201d<\/p>\n\n\n\n To view the status of your software package:<\/p>\n\n\n\n If Chocolatey\u2019s rate limiting is affecting your solution, the workaround is to create an Internal Software Repository to cache packages in the Chocolatey\u2019s community package repository. Then set the custom repository URL in each of your package configurations to install packages from your internal repository.<\/p>\n\n\n\n Internal Software Repositories are servers that your organization deploys and configures. They serve two major purposes:<\/p>\n\n\n\n If you\u2019re unsure if an internal software repository is right for your org, see Chocolatey\u2019s documentation for a breakdown of the pros and cons of the solution. <\/p>\n\n\n\n Using an internal repository can solve the rate limiting issue by acting as a proxy and cache. There many repositories that can be used, Chocolatey recommends these three repositories for organization use:<\/p>\n\n\n\n Of those three, JumpCloud recommends Nexus and ProGet. <\/p>\n\n\n\n ProGet is one of the repositories you can use for your internal software repository. For resources on configuring a ProGet repository, see the following:<\/p>\n\n\n\n Note<\/strong>: Enabling Allow Anonymous Access<\/strong> is necessary to use JumpCloud’s Software Management features.<\/p>\n\n\n\n Sonotype Nexus is one of the repositories you can use for your internal software repository. Note<\/strong>: Enabling Allow Anonymous Access<\/strong> is necessary to use JumpCloud’s Software Management features.<\/p>\n\n\n\n Artifactory is a paid repository software. For resources to configure an Artifactory repository, see:<\/p>\n\n\n\nHow to Determine if Your Software Downloads were Rate Limited<\/h2>\n\n\n\n
\n
Create an Internal Software Repository<\/h2>\n\n\n\n
\n
\n
ProGet<\/h3>\n\n\n\n
\n
Sonotype Nexus <\/h3>\n\n\n\n
For resources to configure a Sonotype Nexus repository, see the following: <\/p>\n\n\n\n\n
Artifactory<\/h3>\n\n\n\n