Support

• K

  [ProGet] Unexpected redirect when accessing Maven package with non-standard version starting with a character
  proget maven • • koksime.yap_5909  

  5
  0
  Votes
  5
  Posts
  21
  Views

  

  Hi @koksime-yap_5909, Good news, it's available now for testing! We're considering merging to ProGet 2025, or maybe keeping for ProGet 2026? Anyway, I posted a lot more detail now: https://forums.inedo.com/topic/5696/proget-is-unable-to-download-maven-packages-that-use-a-nonstandard-versioning-scheme/2 Thanks, Alana FYI -- locked this, in case anyone has comments/questions on that change, I guess that post will be the "official" thread at this point :)
• I

  Symbol Server id issue
  • it_9582  

  15
  0
  Votes
  15
  Posts
  61
  Views

  

  Hi @it_9582 , Thanks for checking that! Well, I'm not sure then :) From here, how about sending us the package? Then I can upload it and see about debugging in ProGet to find out where it's coming from. If you can open a ticket and reference QA-3010 somewhere it'll link the issues right-up on our dashboard. Then you can attach the file to that ticket. We'll respond on there, and eventually update this thread once we figure out the issue. Thanks, Alana
• J

  Proget is unable to download Maven packages that use a nonstandard versioning scheme
  • joshua.mitchell_8090  

  2
  0
  Votes
  2
  Posts
  11
  Views

  

  Hi @joshua-mitchell_8090 , Thanks for the inquiry! The changes are available in the inedo/proget:25.0.24-ci.4 container image, and we'd love to get a second set of eyes. Are you using Docker? They're relatively simple, but we just avoid changing stuff like this in maintenance releases... so it's currently slated for ProGet 2026. But it should be okay for a maintenance release. Please let us know, we'll decide to release based on your or other user feedback. Here's what we changed. First, we added a "sixth" component called IncrementalVersion2 that will support versions like 1.2.3.4-mybuild-678 (where 4 is the second incrementing version), so that vulnerability identification can work better. Our implementation is based on the the Maven version specs, which in retrospect, seems to be followed only by ProGet. Pretty low risk here. Second, we changed our "path parsing" logic, which identifies the groupId, artifactId, version, artifactType from a string like /junit/junit/4.8.2/junit-4.8.2.jar into /mygroup/more-group/group-42/my-artifact/1.0-SNAPSHOT/maven-metadata.xml. It's a little hard to explain, so I'll just share the new and old logic: //OLD: if (urlPartsQ.TryPeek(out string? maybeVersion) && char.IsNumber(maybeVersion, 0)) if (urlPartsQ.TryPeek(out string? maybeVersion) && ( char.IsNumber(maybeVersion, 0) || maybeVersion.EndsWith("-SNAPSHOT", StringComparison.OrdinalIgnoreCase) || (this.FileName is not null && !this.FileName.Equals("maven-metadata.xml", StringComparison.OrdinalIgnoreCase)) )) { this.Version = maybeVersion; urlPartsQ.Pop(); } Long story short, this seems to work fine for v8.5.0 and shouldn't break unless someone is uploading improperly named artifact files (e.g. my-group/my-artifact/version-1000/maven-metadata.xml or e.g. my-photo/cool-snapshot/hello-kitty.jpg). Thanks, Alana
• M

  Debian mirror feed / connector doesn't work " Signature by xyz was created after the --not-after date."
  • matthias.schmitz_2037  

  4
  0
  Votes
  4
  Posts
  28
  Views

  S

  Hi @stevedennis , hi @geraldizo_0690 , sorry for the late reply, it was indeed a timesync issue. Thanks, Matthias
• G

  Unable to import packages from another Proget instance
  • gbeckett  

  9
  0
  Votes
  9
  Posts
  35
  Views

  

  Hi @gbeckett, I just pushed out a pre-release version of ProGet 2025.24-rc.3 and can be installed via InedoHub. Please see our our guide on installing pre-release verions for more information. Please let us know if you have nay problems. Thanks, Rich
• P

  Proget error when setting vulnerability expiry date
  proget postgresql • • phil.sutherland  

  3
  0
  Votes
  3
  Posts
  16
  Views

  P

  @rhessinger Thank you Rich - will install it once released and confirm it is fixed.
• P

  LDAP user name suffix removal
  proget ldap • • phil.sutherland  

  8
  0
  Votes
  8
  Posts
  27
  Views

  P

  To follow up, we ended up being able to get everything working using userPrincipalName for user identity by switching to the OpenLDAP/GenericLDAP connector. The remaining issue I was seeing - unexpected failed group lookup in the "Test User Directories/Load user by user name" test - appears to have been caused by a quirk in the connector. In this particular test for this particular connector, group names are case sensitive. In the other tests for this connector, and in all the tests in the AD connector, group name case is ignored. This does not seem to have any repercussions in actual use, but it led us a merry dance for a while.
• C

  Proget 25.x and Azure PostGres
  • certificatemanager_4002  

  4
  0
  Votes
  4
  Posts
  13
  Views

  

  Hi @certificatemanager_4002 , From the cybersecurity perspective, it's fine to leave it as root since the core process is run by the non-root user postgres inside of the container. You're never exposing a network service while the containerized process has root privileges. Here is more information on this if you're curious: https://stackoverflow.com/questions/73672857/how-to-run-postgres-in-docker-as-non-root-user As you can see in that link, it's technically possible to configure as non-root, but it requires more effort and doesn't really get you any benefit. As for load-testing and restarting, it really depends on the hardware and similar factors. Keep in mind that InedoDB is simply the postgresql container image with some minor configuration tweaks/changes. So any question you ask about InedoDB you can really ask about postgresql as well. As for using an external PostgreSQL server, the only information we have at this time is in the link I sent you before. You really need to be an expert on PostgreSQL if you wish to run your own server. Thanks, Alana
• P

  An error occurred in the web application: v3 index.json not found.
  • parthu.reddy  

  2
  0
  Votes
  2
  Posts
  7
  Views

  

  It looks like someone (at IP 10.2.12.133) has configured the wrong URL in Visual Studio or something. They are trying to access the NuGet API via the wrong URL (note the /feeds vs /nuget at the base url). Cheers, Alana
• S

  Update stats on MSSQL
  • sigurd.hansen_7559  

  3
  0
  Votes
  3
  Posts
  16
  Views

  S

  As I understand it, having a user with dbo-role is not sufficient(according to stackexchange). Since our user is role dbo, but not set as owner on the database, it does not work. Anyway, this is not a problem for us since we do run this manually :)
• J

  Download the cached packages to local machine
  • Johnpeter.Commons_1617  

  3
  0
  Votes
  3
  Posts
  12
  Views

  J

  Ay thank you so much. Yes. It's an air-gapped network. I found the files and have made a docker volume back to the machine.
• D

  Is it possible to run PostgreSQL using ProGet.exe without writing a file to disk?
  • dev_7037  

  3
  0
  Votes
  3
  Posts
  12
  Views

  D

  Ah, fantastic - thank you. I'll keep an eye out for it!
• C

  This topic is deleted!
  • certificatemanager_4002  

  1
  0
  Votes
  1
  Posts
  2
  Views

  No one has replied

• P

  Ticketing system in proget?
  proget • • paul.moors_5682  

  4
  0
  Votes
  4
  Posts
  38
  Views

  

  Hi @paul-moors_5682 , We'll definitely keep an eye on this after ProGet 2026; we're doing some big improvements for vulnerability management, which will probably push more folks out of the Approval Workflow. One thing I like about an in-built workflow is that it demos really well and makes it so much easier to see/understand how an approval workflow could work. While I personally love the idea of "approved packages only", it's so hard to recommend that workflow in practice. Anyway, let us know how your approval-only journey goes. We tried it internally here and it was a flop... just Microsoft's growing dotnet dependencies alone made it impractical. Cheers, Alex
• C

  ProGet License Enterprise
  • certificatemanager_4002  

  2
  0
  Votes
  2
  Posts
  19
  Views

  

  Hi @certificatemanager_4002 , Check out our Licenses for Non-production / Testing Environments for the full details. But if its a short-term migration testing scenario, then using an existing or trial key is fine. For a long-term environment, a separate license is required. -- Dean
• S

  Unverified/not approved chocolatey package categorized with Vulnerabilities:None
  • svc-4x9p2a_6341  

  3
  0
  Votes
  3
  Posts
  18
  Views

  

  Hi, Fashionably late here, but what @atripp said is accurate. Chocolatey's moderation process on the Chocolatey Community Repository is a completely separate process to the vulnerability management features available in ProGet. Our moderation process was put in place shortly after the Chocolatey Community Repository went live 15 years ago, and some packages were added to the feed and haven't received updates since then. While our moderation process is really good, and we've never seen malicious content make it to approved status, you should always detonate-test a package in your own environment before promoting it to a production repository.
• 

  No longer able to download package after update to 2025.21
  • Valentijn  

  5
  0
  Votes
  5
  Posts
  42
  Views

  

  Hi @Valentijn, We had a hiccup in one of our edge nodes that was preventing this version from showing up. If you check now, it should be available. Thanks, Rich
• A

  [ProGet] Debian connector for Jenkins
  • adoran_4131  

  5
  0
  Votes
  5
  Posts
  21
  Views

  A

  @dean-houston By way of follow up, unfortunately the verbose output of an apt update against the jenkins repo provided exactly 0 clarity. apt update -o Debug::Acquire::http=true Ign:1 https://pkg.jenkins.io/debian-stable binary/ InRelease Hit:2 https://pkg.jenkins.io/debian-stable binary/ Release Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. I appreciate the help in trying to make this work, but I am going to punt on this and just grant the specific server access directly to pkg.jenkins.io.
• S

  Using curl to either check or download a script file in Otter
  • scusson_9923  

  13
  0
  Votes
  13
  Posts
  67
  Views

  S

  Hello, Great news! Thanks, Scott
• G

  Debian Connectors Performance Issue
  • geraldizo_0690  

  6
  0
  Votes
  6
  Posts
  41
  Views

  G

  proget:25.0.22-ci.4 seems to work. The CPU consumption stays steady while ProGet is not under heavy load. The Debian connectors does not grow infitely. So for the third day this is the output: root@xxxxxxxxxxxxxx:/usr/share/ProGet/LocalStorage/Connectors# du -chs * | grep G 2.6G total I'll get back to you on this in a week. Thank you for the support.