Hi @koksime-yap_5909 , I'm afraid we can't provide much clearer guidance than that, as there are so many factors involved that make predicting performance basically impossible. For example, the feed types you're using, your CI server configuration, how often developers are rebuilding, etc. The article you found is actually what we send users who experience symptoms of server overload, to help understand where it comes from and how to prevent it. As the article mentions, the biggest bottleneck is network traffic during peak traffic - there's only so much that a single network card can handle, and scaling CPU/RAM doesn't really help. This is where load-balancing comes in. The main downside is complexity/cost, which is why a most customers start with a single instance. It can take quite a while for a tool like ProGet to be fully onboarded across teams, so performance problems likely won't happen at first. Hope that helps, let us know if you have any other questions! Thanks, Steve

Hi @koksime-yap_5909, The command will recreate the user, restore administrative privileges, etc. It's safe to run - and you'll ultimately be left with a Admin/Admin user that you can log-in as. On ProGet 2025, the command is proget or proget.exe We should update the docs for sure Thanks, Steve

Hi @koksime-yap_5909 , I'm afraid this is a known limitation with Maven feeds; we made the assumption that package authors would follow the bare-minimum of Maven versioning: packages start with letters, versions start with numbers. The only examples we found that were counter to that were 20+ year old artifacts, however, we've since learned that authors still mistakenly use these incorrect versions. Unfortunately, supporting these types of versions require a complex/risky change. Maven is a file-based API and the client just GETs/PUTs files. However, ProGet is not a file server so we need to actually parse the URLs to figure out which artifact/package the files refer to. In this case, we parse package-alpha-0.1 as package-alpha (version 0.1), not package (version alpha-0.1). Hence, why it's not working. If these are your internal packages, the easiest solution is to follow the standard: https://docs.oracle.com/middleware/1212/core/MAVEN/maven_version.htm Thanks, Alana

Hi @koksime-yap_5909 , Not necessarily - it really depends on the API query. If the query is like "give me a list of all versions of MyPackage", then ProGet will need to aggregate local packages and connector packages to produce that list. If the query is "give me the metadata for MyPackage-1.3.1", then the first source that returns a result is used. In practice, NuGet asks for "all versions" a lot. So you'll get a lot of queries. Thanks, Alana

Hi @koksime-yap_5909 , Docker registry import from Sona, JFrog, and other ProGEt instances is coming soon via PG-3128 - we anticipate that in the next maintenance release. As for Assets, I'm afraid we don't have any support for that planned in the near future - it's relatively easy to write a script that "extracts" them - if you could extract it to a ProGet drop path, then they'll be imported that way. https://docs.inedo.com/docs/proget/feeds/feed-overview/proget-bulk-import-with-droppath -- Dean

Hi @koksime-yap_5909, No; when you use LDAP, then you need to manage the LDAP users' groups in your directory. Here is a recent discussion on the topic: https://forums.inedo.com/topic/5471/feature-suggestion-allow-ad-users-to-be-added-to-built-in-groups Thanks, Steve

Hi @koksime-yap_5909 , This is the "Feed Overview" page and the URL that you need: Thanks, Steve

Hi @koksime-yap_5909 , That's just a "suggestion box" in the UI - you can just type in whatever you'd like. But in general you shouldn't upload files via the UI, but using maven. Thanks, Steve

Hi @koksime-yap_5909 , This is a known issue and will be fixed via PG-3063 in teh next maintenance release, shipping later today. Thanks, Steve

@erich_1530 in the ProGet software, you will see a "License REquired" error message. if you click on the "Request License Key" you can get a Free or Trial key from within ProGet. Or you can go to my.inedo.com and request a key from there if your server does not have internet access

@dean-houston I just upgraded to the latest version and it worked perfectly now. I can update packages of more than 2 GBs without any problems. Thanks you so much!

Hi @pmsensi , Short of using the Native API, I'm afraid we don't have a first-class API to export/import package policies and their related information We may consider adding that after ProGet 2025 is released. Thanks, Steve

Hi @pmsensi , The pgutil builds audit command should show the same license information you see in the UI: https://docs.inedo.com/docs/proget/api/sca/builds/analyze The pgutil packages audit command should also provide similar information on a package level. Is that's what you're looking for? Thanks, Steve

Hello @atripp , Thank you for your help. We have an intermediate certificate (proxy), which I think, as you point out, can be the problem. I will clarify with our IT department. Anyway, after reading a little bit more, there is a variable to force Kaniko to use HTTP/1.1. variables: GODEBUG: "http2client=0" After adding that, everything works :) Thank you! Best Regards, Pedro

@rhessinger I added the requested info to the opened ticket. Best Regards, Pedro

@atripp Thanks for the fast reply and the bypass. Best regards PhilippeC.

Good news @m-karing_2439 , This works in ProGet 2024! More specifically, when rewriting/refactoring the PyPi feed, we added support for this "unconventional" repository - specifically, one that doesn't follow the /simple convention or use any of the JSON/warehouse api. Cheers, Alana

@emer-connelly_2117 very cool, thanks for sharing!!

Thanks for the update @mness_8576; based on this, it sounds like there's definitely a Gateway problem, and that the Gateway is misconfigured / misreporting some error condition from ProGet due to a quirky package request. That's a pretty common thing we've seen as well.