Hi @Nils-Nilsson, Thanks for bringing this to our attention. This looks to be a regression that happened right before release. I have created a ticket, PG-3289, to track the fix and we will release it this Friday in ProGet 2026.2. Thanks, Rich

Hi @jimbobmcgee , Very cool! We did not forget about this, just got a bit behind on feature requests (which this got classified on) with ProGet 2026 coming out. However, we've added this to our BuildMaster/Otter 2026 roadmap to review and incorporate. We plan to start on that relatively soon, and it may be something we can easily back-port to BuildMaster/Otter 2025. We'll update once we make progress on this :) Cheers, Alana

Hi @Nils-Nilsson , We've added this to our ProGet 2026 roadmap; there's an additive feature called "Build Pipelines" that just didn't make it in time for release, so this will fit nicely into that. FYI the main thing that this new pipeline offers is the ability to create multiple pipelines and assign them to different releases. Thanks, Alana

Thanks a lot @atripp for the quick fix. Problem solved Cheers -Fritz

Offline installers are available here which you can use to upgrade these older versions: https://my.inedo.com/downloads/installers

Hi @ybaskar-temp_3339 , Thanks for confirming that. I think it'd be worth exploring how to change those migration/environment constraints. While it's unfortunate to "lose history" and need to navigate to a separate instance, there's a moderate amount of risk in things simply not working the way it did before.... we're talking a decade of evolution, including platform, architectural, and even usage changes. That said, for an in-place upgrade, here's the approach that I would use. Use the Legacy (Traditional) installer to get to BuildMaster 6.1. Verify things work as expected on BuildMaster 6.1, agents updated, etc Upgrade to BuildMaster 6.2, again using the traditional installer Verify things work as expected in same manner Uninstall Ensure all components (iis site, service, program files.... except database, artifacts) have been removed Install BuildMaster 2025 as per normal, pointing to existing database Note that there's a decent change that you'll run into database or binding errors after #7, so make sure to run buildmaster.service.exe run from the commandline to better see messages and errors if things don't start up. Cheers, Steve

Hi @pg_user_8607 , Unfortunately, the only information we receive from the underlying library is LdapReferralException, so there's nothing else we can log. My understand is that the server is limiting the information and you ought to see more information from the LDAP/AD server's query logs (they are like HTTP access logs). That's the absolute best place to look. In our experience, a referral typically means the domain name is incorrect (e.g. user@domain.com instead of user@domain.local), but it could be any of the things you mentioned to. Unfortunately, LDAP/AD configuration can be a pain in rare cases (which it sounds like you are), and there's just no way around that. As for monitoring, here is what we recommend: periodic monitoring of the /health endpoint (every 5 minutes) (optional) HTTP access logs (retain for 7 days) There's nothing required beyond that. Those "container logs" (i.e. proget console output) that you see are primarily intended for us (product engineers) to troubleshoot problems and there's not much value in trying to use/storing them. For a tool like ProGet, trying to do extract/monitor detailed metrics is counter productive and leads to information overload. Many "errors" are not problems are a total waste of everyone's time to troubleshoot. For auditing, ProGet maintains internal audit logs (you can query them from the database if you really want to "export" them), or you can use webhooks if you want to publish events. But again, we don't think that's productive; they just become a "secondary log" that no one looks because it's harder to query than ProGet database. For authentication-related information, a combination of HTTP log monitoring (403 errors) and LDAP/AD server is the best thing to check. Cheers, Steve

Hi @stevedennis , using ?bypassIntegrated=false lets me download the package from the UI. Is this something you can fix? For now I can share this information with my colleagues. Offtopic (since we are already talking): We recieved your Inedo snackbox this week and we love it Thanks, Caterina

@dwilson_7533 that sounds about right! In modern versions of BuildMaster, it's possible to change Pipelines ("new" name for Workflows) a little easier, or even create builds without them. Speaking of, I'd recommend giving it a shot, we've got some pretty cool Git integration these days :)

Hi @certificatemanager_4002, I'm not sure I totally understand the question :) The ConnectionString property is marked as encrypted, which means that ProGet's Encryption Key will be used to store it to the database as encrypted, and obviously decrypt it. But this should happen automatic, when using the API or UI to save the settings. -- Dean

Hi @ybaskar-temp_3339, Going off of memory here (this was like 10 years ago), but I believe that BuildMaster v5 would hide legacy options unless there was already legacy data. Since there's no legacy plans there's no button. However, it still should be possible if you can find the url of the page to navigate to. I would check other apps for that option, inspect the url, and just replace it with your applications Id. Let us know if that works! -- Dean

@pg_user_8607 very cool, great practical use of the new ".cs scripts" type applications! I think this could make a nice blog post... I'll point this to our technical writers!

Hi @dean-houston, thank you for the explanation. I understand, that you don't want to risk the implementation for these special version numbers. On dealing with these false positives, it would be great to ignore a vulnerability just for a specific version, therefore fixing just the version mismatch, rather than deactivating the vulnerability globally. But I'll gladly wait for ProGet 2026 and check out the changes done to the CV management. Best regards

Hi @Ashley , It sounds like you're definitely looking in the right place / setting the right configuration. X-Forwarded-For should do the trick, but something as silly as a typo (which I've done several times) will make it not work. Here are the settings we recommend: proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Host $http_host; proxy_set_header X-Forwarded-Port $server_port; And as an FYI, here is the code we use to get the ClientIP adddress. public static string GetClientIPAddress(this AhHttpRequest request) { ArgumentNullException.ThrowIfNull(request); var forwardedFor = request.Headers["X-Forwarded-For"]; if (!string.IsNullOrWhiteSpace(forwardedFor)) { var ips = forwardedFor.Split(','); var clientIp = ips.FirstOrDefault(); if (!string.IsNullOrWhiteSpace(clientIp)) return stripIpv4OverIpv6(clientIp.Trim().Truncate(50)!); } return stripIpv4OverIpv6((request.NativeRequest?.HttpContext?.Connection?.RemoteIpAddress?.ToString() ?? request.UserHostAddress).Truncate(50)!); static string stripIpv4OverIpv6(string ip) { if (ip.StartsWith("::ffff:") && ip.Contains('.')) return ip["::ffff:".Length..]; return ip; } } Although I think the stripIpv4OverIpv6 bits may be relatively new. Thanks, Alana

Hi @ybaskar-temp_3339 , The "root cause" is relatively easy to answer. The error was occurring on the 10. Block 6.2 Upgrades.sql script, which is simply this: IF OBJECT_ID('ActionGroups') IS NOT NULL EXEC sp_executesql N' IF NOT EXISTS(SELECT * FROM [Configuration] WHERE [Key_Name] = ''Legacy.NoLegacyFeaturesDetected'' AND [Value_Text] = ''True'') RAISERROR(''Cannot upgrade to BuildMaster 6.2 unless "Legacy.NoLegacyFeaturesDetected" in Advanced Settings is "True". This can be done by running the legacy features checker.'', 16, 1) ' Basically it will simply crash unless Legacy.NoLegacyFeaturesDetected is not set to "True". The "Legacy Feature detector" should have set that to "True" if there were no legacy features detected... but perhaps it didn't? Since you were able to bypass it, I wouldn't worry about it. In the "worse case", legacy data would have been purged during the delete. Thanks, Alana

Thanks @atripp, that makes sense. I was having another issue with pgutil which turned out to be my fault, however I believe there is a follow on issue to do with the compliance analysis for project builds that have yet to have been pulled to ProGet. More detail on my original post here: https://forums.inedo.com/topic/5733/proget-unable-to-publish-sbom-from-pgutil/4. @Dan_Woolf suggested continuing the topic here as it's related to non-compliant packages and what I believe to be the recently published rule. Is this something you can take a look at? Thanks!

Hi @Ashley, Glad to hear that fixed the issue with the Project Name! You are partially right on the noncompliance. The publish date is definitely causing most of the packages to be noncompliant. Based on your logs, I'm also seeing at least one deprecated package as well. I see you already have another forums post about the recently published issue. I believe we can continue that issue there and close this one out. Thanks, Dan