Thank you. The problem seems to be caused by Web.ConcurrentRequestLimit setting. If the server receives lots of requests and needs to query itself, these requests will be queued when the limit is reached. So they never finish in time and the original request throws the timeout exception.

Hi @cshipley_6136 , We recommend using the /health monitoring endpoint. As you can see, it makes a connection to the database by calling that stored procedure. We do not recommend calling other URLs; and there is no reason another page would work. Calling other pages will impact performance and likely yield incorrect results. You're right, it might have to do with a "connection pool" problem -- but that's all managed at the driver level. You can control connection pool settings by changing connection string values, but to be honest we have no idea what the impact will be. Your best bet is to open a case with Microsoft, who has the expertise to know how to troubleshoot these intermittent "error 40's". They may have specialized tools or "secret debugging commands" you can use. This is all happening at the operating-system or driver-level, and while we're doing our absolute best to help you troubleshoot, but we have never seen this happen before and our main resource is searching google. And this is not an easy error to search for,..as you've probably noticed. Please keep us in the loop. Best, Alana

Hi @c-schuette_7781 , This error is occurring on the remote server (i.e. nuget.devexpress.com). This error can happen when a server is overloaded... so you're basically doing a DoS on DevExpress's server. You'll need to try again or contact DevExpress for help,. I believe that DevExpress wrote their own, custom NuGet server. We've had several issues with it in the past. While talking to them, you should also suggest they switch to ProGet ISV Edition like some other component vendors Best, Steve

@rhessinger

@valeon @miles-waller_2091 @olivier @It-purchasing_9924 @entro_4370 Took a bit, but CRAN (R) feeds have arrived https://blog.inedo.com/inedo/introducing-cran-feeds-in-proget/

Hi Steve, Moving the API key to the header worked - thank you very much! Kind regards, Mark

Hi @pallavi-tarigonda_9617, Adding an entry to the hosts file should not cause a "blocked" connection, so it sounds like there's definitely something strange going with your machine's configuration. I'm not sure how to troubleshoot this further. Self-connectors work fine in testing Free edition, and other users don't have an issue. If it helps, here's the code that ProGet uses to determine if a connection is local: public bool IsLocal { get { var connection = this.NativeRequest.HttpContext.Connection; if (connection.RemoteIpAddress != null) { if (connection.LocalIpAddress != null) return connection.RemoteIpAddress.Equals(connection.LocalIpAddress); else return IPAddress.IsLoopback(connection.RemoteIpAddress); } if (connection.RemoteIpAddress == null && connection.LocalIpAddress == null) return true; return false; } } I would explore the hosts file issue; the fact that a loopback (127.0.0.1) entry wouldn't work sounds like there was some kind of data entry error/typo in your hosts error, but hard to say. Best, Steve

Hi @ivan-magdolen_6846, An "Invalid credentials specified" basically translates to "invalid username/password". In this case, it doesn't matter that the user has permissions or not (authorization) -- they simply can't login (authentication). I would try this without chocolatey; you can simply visit the API urls in an "incognito" browser directly, and enter the username/password prompts from the browser. This should be a browser-prompt, and not the ProGet log-in page. Once you can access the API urls, that will give you an idea of whether the LDAP is workikng or not. Cheers, Alana

Hi @kigiwow570_6179, I don't have enough information/specifics to answer the questions; it really depends on the API queries being made, etc. Some API calls result in errors, others do not. In general, doing a NuGet restore will not result in errors being logged. Best, Dean

Hi @kigiwow570_6179 , These errors are being "forwarded" from NuGet.org, and if you're seeing them it means that "something" on your network is making requests to a ProGet feed that has a connector to nuget.org. This is typically an old, outdated tool or script. You'll need to track this down and update/disable it. It could also be a self-connector that is connecting to a feed that also has a connector to ProGet using the V2 APi - so double check your self-connectors. Best, Dean

@dean-houston About the missing files (FileNotFoundException), I made a mistake in my docker-compose file, so the packages volume wasn't persistent. Noob error , sorry about that. Best regards PhilippeC.

Hi @stevedennis I was just looking to configure Proget as good as possible. This part was a little bit fogus for me I thought this was a bug ... Thanks for your reply Best regards PhilippeC.

Hi @paul_6112 , Thanks for letting us know that this is still an issue. I created a ticket, BM-3914, to track this fix. Thanks, Rich

Hi @paul_6112 , Thanks for letting us know that this is still an issue. I created a ticket, BM-3913, to track this fix. Thanks, Rich

Hi @v-makkenze_6348, This fix has been released in pgscan 1.5.7. Please let us know if you have any questions! Thanks, Rich

@dean-houston

Hi Dean Thanks for your reply. It was just a question, finally useless. And Thanks you for your time Best regards Philippe

@rhessinger said in BuildMaster v2023 PSCall: Hi @paul_6112, What version of the Scripting extension do you have installed? This bug should be fixed in v2.4.0 of the Scripting extension. If it is not currently version 2.4.0, can you try updating that extension and see if that fixes the issue? Thanks, Rich Thanks Rich, This does appear to work okay on BuildMaster 2023.5 and Scripting 2.4.0 [image: 1700509354377-0e3636d2-4854-4025-9e3f-648f03cc46a1-image.png]

Hi @pallavi-tarigonda_9617, These errors are being "forwarded" from NuGet.org, and if you're seeing them it means that "something" on your network is making requests to a ProGet feed that has a connector to nuget.org. This is typically an old, outdated tool or script. You'll need to track this down and update/disable it. It could also be a self-connector that is connecting to a feed that also has a connector to ProGet using the V2 APi - so double check your self-connectors. Best, Dean